We had an issue where someone was spamming movement due to something on their keyboard and this caused issues across the MOO. I have added a cap to the number of movement commands that the MOO will respond to from a single player over a short period of time.
I've also instructed the admin on how to handle it when they see it happening (kick the person offline, speak with them when they get back online, if it happens again, suspend them).
This should hopefully prevent further disruptions.
This will now tell you to use g feed instead. As this is the main 'feed' topic and viewing it was showing all the feed content which was like 7k+ lines.
Fixed a messaging boo boo in the Cortex Bomb's exploding message, showing the name of the person detonating the remote, rather than the person whose mind is being blown.
Updated admin tool to make it easier to manage apartment doors for adding and removing rent time, changing renters from one person to another.
Updated admin tool to show typos in a more structured way to help make it easier to read the @typo submitted and then fix it.
(Thank you for submitting typos!)
The drive and drive out messages were missing the origin and dest directions from their props. Fixed.
There are a bunch of different kind of barriers that can block exits / manholes. Two of these are not really barriers at all but crime scene tape and WCS cleaning barriers, which are really just denoting that something is happening in the area. Previously these had the same fatigue cost as a manhole cover or pile of debris. I've made it so each type of barrier can have its own fatigue cost and made the cleaning/crime scene ones cost very little comparatively.
This was showing 'a creepy bunny-masked' instead of a creepy bunny-masked average dude'. Or whatever the shortdesc modifier would be. Fixed.
Holo progias were not registering in the missed call app when a call came in to a progia with the app. I've fixed this.
I've updated the code used for login/reset password/account creation for the grid from within the MOO. It was previously relying on the Grid 3 node app to generate the IC password and hash, but as some of you have seen, if that application was unavailable for some reason (network, restarting, bug, etc) it would lag the MOO.
Now it will handle this all within the MOO and via SQL, making it more resilient. If anyone notices any issues, please @bug and xhelp.
When a tailor takes an action that causes the clothing to be unfinalized, you will now see a yellow text warning that the item was unfinalized.
You can no longer set @see-thru on items that a currently being worn.
By default items get layer 1 when created. We check if they contain certain names and update the layer based on that.
tailcoat has been added to layer 4
vest has been added to layer 2
waistcoat has been added to layer 3
I've updated the default layer to 1 for some materials that it was not 1 for. I don't think this should impact anything, but if you encounter issues, please @bug it.
Synthetic Leather Material was 2 now 1
Waterproof Vinyl Material was -1 now 1
Cultured Wool Material was 2 now 1
This should mean they are wearable below things they were not wearable below before, in cases where the name would have normally caused the layer to not be explicitly set to something else (see help tailoring for the list of names that cause different layers).
I've updated all the player made vests, tailcoats, and waistcoats to use the layers I outlined above.
If a post gets 5 upvotes it will get a green border highlight.
If a post gets 10 upvotes it will get a blue border highlight.
If a post gets 20 upvotes it will get a pink border highlight.
This should make visually identifying important posts more intuitive.
I've implemented the ability for BGBB moderators to rename threads. This should help when people create threads that do not have useful titles.
I've added a feed notification for Grid 4 posts to the feed and standardized how the feed notifications come in so they are clear, and don't have the topic id.
There was a bug where someone could type 'open here' in a locker room and it would generate a TB. I've fixed it.
Searching in the library catalog expected a capitalized letter but didn't enforce it, leading to a traceback when a lowercase was provided. Fixed.
(Edited by Slither at 8:29 am on 11/29/2025)
