Instead of saying the current name or disguised name of the person you were following if they give you the slip -- it will now say 'Looks like someone gave you the slip'. This reduces the meta info that it is possible to glean.
|-||AdamBlue9000||1m||Rolling 526d6 damage against both of us.|
|-||Nemisis||1h||@invis is the biz! whoops.|
|-||Bruhlicious||4h||Deine Mutter stinkt nach Erbrochenem und Bier.|
|j||Johnny||39s||New Code Written Nightly. Not a GM.|
|a||Mench||1h||Doing a bit of everything.|
|And 33 more hiding and/or disguised|
I've updated some sever code to hopefully avoid a loop condition where a limb doesn't get severed and the player doing the severing automatically continues trying.
SEVER & KNOCKOUT
If you try to sever a limb from someone KO'd who is not restrained, but the person is going to wake up before you would finish the sever, it won't let you sever. This is due to the inability for the code to detect if someone wakes up during the sever and automatically stop it, since presumably, the person wouldn't just lie there waiting for their leg to be severed.
We have neon signs and holo signs that can contain ASCII or interesting stuff like NEW ROSE HOTEL, except some of the letters are missing. In these cases, we have an accessibility_text prop that will show the signs true meaning if someone has @ACCESS STRIP_ASCII is enabled.
However, not all signs /holos -need- this as some are just text, so setting it actually reduces the quality of the experience, and often hasn't been done at all leading to a warning on the admin every time someone see's these signs without accessibiltiy_text.
To combat this, I've updated the warning to be more specific about what needs to be done to resolve it, and added a new property called .ignore_accessibility_text which can be turned on for signs/holos that do not contain ASCII -- thus providing the same messages (minus the [ and ]).