This is now 1 week instead of 2.
I've fixed the long standing bug tailors would get when setting messages that happen to contain the words her or him or his in the middle of other words.
ABUSABLE TEASE MESSAGES
This was done as part of an upgrade to the message checking function that prevents tailors from writing tease messages that display values that shouldn't be displayable. A simple abuse case would be %[dname], allowing you to make a garment that would give you the undisguised name of an individual. This is no longer possible.
The example of dname is useful to understand what was fixed. But at the same time, it's an information leak and should probably be scrubbed.
The hacker in me, having not known about that variable a second go, kind of wants to go throw it at everything I can to see if it sticks. I won't, but it's just an example of how something innocuous and offered in good faith can be used maliciously.
Any logs taken in recent months via the web client, when you were using https, will potentially have issues in some browsers due to loading of insecure resources. This can be fixed by editing the log's HTML at the top to point to http for the moo.sindome.org portion.
This shouldn't effect too many people and we have fixed the issue so that new logs taken after the next web client restart should work properly.
Any logs taken in recent months via the web client, when you were using https, will potentially have issues in some browsers due to loading of insecure resources. This can be fixed by editing the log's HTML at the top to point to http for the moo.sindome.org portion.
This shouldn't effect too many people and we have fixed the issue so that new logs taken after the next web client restart should work properly.
I noticed that there were a bunch of clothes sitting in the recycling bin that weren't being processed by the clothing voter system. These items had previously been set to 'save' in the old system, which meant we would move them manually back into the market because someone thought they were worth keeping.
The new system doesn't use .save, it just ignores clothes that are .save'd and asks people to review ones that are not. This means that if an item goes through the clothing review process and get's kept, it's moved to the market and then if it's trashed again it gets reviewed again, thus we don't have things kept forever that have fallen out of fashion or utilize old code.
I've made the review system also take into account .save'd items and move them directly to the market so they don't hang out in the recycling system forever. Small improvement, but worth noting for the future.
Support GMs can now @stats again, but they will only see if a player has a clone or not, which is important info for all GMs.
@ANSI
@ansi has been updated to include options for normal ansi and xterm256 though xterm256 has not been implemented yet. Everyone who had ansi off, still has it off, everyone else has xterm256 enabled by default.