Zugg Software :: Search

I've had numerous problems with the auto update not actually installing!
Sits there downloading the new files but never installs, just closes, and the next time i load cmud its the same version, alwa ...

Sometimes when you alt tab back to the program the scrolling is all messed up so that you can't see the most recent stuff, it just keeps repeating the old content, you can tell new posts are arriving ...

perhaps for future releases this should be set automatically?

Just noticed this strange issue...

if i chat bob@bob.com and jim@jim.com

it will come out on the mud as bob@bob.com and bob@bob.com

Now i know this isnt the MUD because as soon as i connect v ...

afaik i havent ever used zmapper...

I have sent a report but thought id post here also

IconTbl: Type mismatch for field 'Bitmap', expecting : Blob actual: String.

Happens when i connect to any mud apart from the first one! so ...

sometimes you have to double click on the correct icon on the sessions list otherwise it will open the last session used.... Been like this since cmud was released

i had an issue with cmud losing focus to the command line after swtching to other sessions, appears to have sorted its self since i removed cmud and reinstalled....

well i removed cmud totally and reinstalled it and the command line focus issue is no longer there, so im guessing its something to do with a bad version of cmud at some version.....

When you click on a session the command line doesnt become active, you have to click on the actual command line to enter any text, this happens when you have more than one session open. Hadn't really ...

Didnt see the message about the release of 2.24, just downloaded and tried it, and all seems fine. Dunno HOW i missed that sticky on the new version :)

Following on from the post here: http://forums.zuggsoft.com/forums/viewtopic.php?t=30610

I have doubled checked all my sessions and none of them are sharing the same package file.

Basicly all i ...

Still getting crashes with closing of sessions that has been happening since 2.20

See the following

Date/time : 2008-05-07, 12:03:50, 211ms
computer name :
user ...

Well i explained the issues to them with the way mccp was set up.. and fixed it for them.. mccp should now be fine on dark skies - Problem was MCCP1, Jobo used that on the early versions of Dystopia, ...

this will probably be an issue with all muds based upon dystopia 1.2.7 (yes i know im a dystopia hater but the imms of ds are changing stuff)

Must be something to do with the change to mccp detection that 2.21 has, as this never happened in previous versions of cmud

well it could well be how it handles mccp :P

do a search for "dark skies" on mudconnector and lemme know if its only me that has the issues :)

Well i meant to say it didnt have a reconnect trigger.. and i get to enter my name, but then the cMUD crashes, tried to make a new session and the same still happens.. changed the login into for a ses ...

Just updated to 2.21 pro beta, trying to connect to any session results in a lockup of cmud... session does have an autoconnect trigger, maybe that has something to do with it?

following on from that if you make the connection box larger the full text shows..

i didnt mean default sessions i meant each session... and i wasnt moaning about the labels in each text box just pointing out...

Upgraded to cmud pro 2.20 from cmud pro 2.18, and my session corruption issues resurfaced, now i read in the version history that 2.20 tries to fix bad sessions, it didnt.
So i decided to delete the ...

we had green on black vt100 terminals and orange on black terminals when i went to uni in 1995 still, so i understand the green on black starting color all to well... :)

again this has happened, uninstalled cmud removed all trace of it from this computer, reinstalled recreated the sessions, they worked, went away turned computer off, came back and only 1 session allow ...

i changed the name of the package file that the mud that refused to open ran using, and it actually allowed me to connect to the mud, so i guess the package had somehow got corrupted, from what i thin ...