Wearoff/Dispel color

When an affect wears off or is dispelled, it's always dark blue. I've looked through the world config and global settings, and nothing seems to change it.


And I missing a setting, and is there a way to change that?

Is that good or bad? Is that different from other things?

It's a bad thing because dark blue on black is hard to see, not to mention the color should be coinfigurable.

And while I'm here, why can't I post more then once a day? I tried to post a replay when I first saw it, but it said I had to wait a large number of minutes before replying.

I agree the color should be configurable! But it's not clear to me that this is somehow a problem with MUSHclient as opposed to some unknown plugin you have installed or just the normal state of text from your MUD. Maybe you want all dark blue things to not be dark blue anymore? That you can do by changing the display colors in the world settings for ansi 4 and 12.


Nick is experimenting with anti spam measures. Sounds like something went wrong. Hopefully he sees this and it gets fixed for you.

It's also entirely possible the setting is server side rather than client side as to why you can't find the client setting.

Ok, but aren't all colors sent by the server interpreted by the client and then are configuarble? Or does Mushclient have some coded in colors that are just passed through and can't be configured?

Well all of the basic ANSI 16 colors can be configured. Press Alt+6. Or go to the menu Game -> Configure -> ANSI Colours...

What was the message exactly? You should only have to wait a fairly short time, based on your profile. Certainly a lot less than a day.



Five minutes?

It's possible my anti-spam measures are faulty, but you should never have to wait more than 30 minutes, and even that scales down once you have made more posts.

The last one was 193 minutes, but it was longer before that. I asked Iyara to pass it along, but I'm not sure if it made it to you Nick.

And the chances are that I'll have to wait just as long before I can reply to anything you post.

Yes, and no, on both counts. Colors from the server are simply passed by the client without modification to plugins, scripts, triggers and any custom color settings you've configured. I can tell you for fact that if you haven't configured any custom ansi settings and don't have any plugins, triggers or scripts that are changing the text color on your messages, the color is being set dark blue by the server and MC is simply relaying the information from the server unchanged because there aren't any default color changes based on what text is received from the server. You can't find the default client setting you appear to be seeking because there simply isn't one of that nature. If the normal text color from the server isn't dark blue for affects being dispelled or wearing off, you have a plugin, script or trigger changing the text color that you're going to need to identify and change to do anything about the text color, or you can change the ansi color settings as described by Fiendish but that may have other unintended consequences.

Except that the server doesn't actually have the ability to send colors. It can only pass along color identifiers.

No MUD says "{R0,G0,B255}This text is blue".
It says something more like "{blue}This text is color 'blue'."

Note here I made up my own formatting, but this is the basics of ANSI coloring. MUSHclient then says "{blue}" means a particular shade of blue by convention.

ANSI 256 has much more strict of a guideline for color interpretation, because it actually follows a 6x6x6 color cube. So you probably shouldn't change only color 46, because colors 40 and 47 are supposed to correspond with adjacency and then they wouldn't.

Fiendish, while you and Nick and I are well aware of that distinction, I was trying not to confuse Gaowin who hasn't demonstrated that level of knowledge.

Don't worry Meerclar, I was a builder on the mud I was at before I switched to MM for over 15 years, so I have a pretty good grasp of things.

I have tried to change the ansii colors in the world configuration, and none have dark blue, but I didn't think of taking a look at the plugins I have.

I'll check my plugins and see if any of them are what's doing it.

I just checked out the other thread you listed all your plugins on, LOTS of places you could be seeing color manipulation that wouldn't be reflected in the client settings if you're still using the full MM package you had at that point.

Can you please copy and paste the exact message you see from the forum? Thank you.

Test post to check throttling time-out.

I found the problem, I think. It worked when I tested it on a test server, but on the real server the time difference between UTC and server time was adding an unexpected extra wait. Your wait time should be much shorter now.

Yep, I was able to reply instead of waiting 3 hours.

If you still have it enabled, take a look at the affects_by_name plugin for where you're most likely getting that text color from Gaowin.

There are two ways of configuring colours. The simple one is to use the ANSI colour configuration window in the client world configuration. This maps the ANSI code to some arbitrary RGB colour (the default is the standard ANSI mappings).

Changing that will change every instance of (say) blue to some other representation.

You can also use MapColour which will map an exact RGB code to something else. This can be used with MXP or 256-colour ANSI if there is a particular colour that the MUD sends that you don't like (and it isn't a standard ANSI colour sequence).

Another throttling test.

Thanks, I'll take a look at that after I see if affects by name is the one that's messing with me.

Hell, at least this isn't as annoying as figuring out that the Windows 10 auto update was blocking your xml files Nick:)

Bloody Windows 10.

Ah yes, those XML files can be dangerous in the wrong hands!

---

Fixed bug in throttling where if a new user had made no posts, they would be throttled until time had elapsed since their previous post, which would clearly be never. ;)

The affects by name plugin was the culprit, because dispelling affects now doesn't show what affects were removed, much less if dispelling was successful or not.

And yes Nick, we should always be careful so that evil xml coders don't take over the world. (Or at least take control from Microsoft or Comcast)