Zugg Software :: View topic

Wizard Joined: 17 Jun 2006 Posts: 1201

This has nothing to do with ansi but it does have to do with color issues... Has anyone noticed that when a command is sent, the very next line is not in the right color? It doesn't matter what command but any command that is sent from a script using #send the next line ends up not being colored correctly. For instance, the health in my prompt turns gray.

Example:

Some random line of text is received.
-command shows here-
1234h, 1234m, 1234e, 1234w cexdb-

The 1234h part shows as gray when normally it would be green, but only happens where there is a command. It happens every single time as well.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I had color issues before 2.18, but 2.18 fixed my problems with the bleeding color changes. Are you using 2.18 now? And, is it a clean installation with brand new packages, layouts, and all that?

Wizard Joined: 17 Jun 2006 Posts: 1201

Yes, yes, and yes. I am using 2.18 and this isn't bleeding. I'm not coloring anything. It's a command being sent. The prompt is changing from the normal color to gray for some reason. I know before on the old beta versions if I substituted something with color or used any sort of %ansi it would bleed over, but I really can't see why this is happening.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

I've seen this. Somehow after sending a command the next line or two are the wrong colors. It has been around for a several versions but with all the other ansi problems I didn't feel it was worth reporting.

I THINK it was introduced when Zugg put the %ansi(reset) automatically at the end of a #say and #echo. Any further ansi code sent by the mud changes the display back to the proper colors.

For example the '1234h, 1234m 1234e, 1234w' are all supposed to be green but the 'cexdb-' are supposed to be gray and as such an ansi code is sent by the mud fixes anything following.

It almost looks like Zugg cached the last color that the mud sent but failed to cache the mud sending %ansi(reset). So when the next line is sent from the mud he concats the cached color onto the beginning of the line.

Wizard Joined: 17 Jun 2006 Posts: 1201

Well except now it has gotten worse. A couple of random times it blacked out like the next ten lines after a command. I can see the command of course going through but all the rest of the text becomes black, except for things that I have personally colored. In other words all the text being received suddenly turns black, which on my black screen means it vanishes. This is not fun! It only reappears when I get a line that I have something colored in it.

This problem only happens out of the blue though. Not like the other one described above. However, it is still related because it is any time a command is sent. I don't have ATCP or MCCP on either.

Wanderer Joined: 30 Jan 2006 Posts: 66

Yep I have this as well... sometimes lines are blacked out for a while.