Made a change to a code block in a verb that I think was getting people stuck in the 'PERFORMING' state, preventing them from performing some more.
Hopefully, it should be fixed and will allow people to perform to their heart's content.
Please report any wonkiness that may have been introduced.
If you eval a robot now, you'll see partially covered robot parts right after fully visible ones. Partially covered ones will not give your a condition, as they are partially covered and thus you can't fully evaluate them. This should avoid confusion that players have reported with not seeing parts that are not fully covered.
The SIC cyberware had no emp resistance, meaning it could be damaged and disabled by an EMP. We actually don't want this. It's only happened once ever, that we know of. I've given it much better emp resistance (to damage).
This should not impact disabling it temporarily / deadzoning it with an EMP. Just permanent damage to it.
Don't wany immies getting their SICs damaged, or people using EMPs in lieu of going to the ripper doc when they need their SIC gone.
I've updated the fire escapes in game such that they are NOT targets you can typically jump to from a rooftop. This should prevent the roof that overlooks the Ashlin Crown building from having 15 rooftops you can jump to.
You can still attempt to jump FROM the fire escape to a nearby roof, and I've left the fire escape that is LEVEL with the garage as a valid jump location but excluded all the others to make this a more manageable jumping experience.
Ammo production kits had a bugged property that was causing them to trace back when trying to make certain types of ammo. This was then compounded by a bug in the error handling code for these kits.
Both have been fixed, and ammo kits should just work now for anything you know how to make. If you run into any issues, raise a new bug so we can investigate.
This had been broken for a while due to the changes to security networks several years ago and this camera not being ported over. I've moved it and it should be working as expected now, and showing what's going on in RiotGear on channel 777, with the view rotating between different view points once a minute while games are going.
If you uncontrol/exit the vehicle/dismount while driving a vehicle, the vehicle will continue forward for 1 room and then either roll to a stop or crash due to the lack of driver. It's a coin flip that decides which outcome.
I've tested this and the messages are mostly right, though there might be a tad bit of wonkiness about you continuing to drive smoothly or something even if you've uncontrol'd or dismounted.
I don't think this outcome will come up much so it may be a non issue.
I had to edit vehicle movement so if anyone see's any weirdness please @bug it.
Updated how we pull recipe masks so that ones without full configuration (like tacos) show up correctly when you craft [something] using chef.
Hopefully fills in the gaps people were seeing where they bought the groceries but didn't see available recipes for the items.
I've tracked down a lingering and super annoying dynamic room issue where we were calling a verb (match_exit) to see if we had any real exits pointing in a direction, but which had the side effect of creating a dynamic exit if one didn't exist. This side effect exit would then be used, but blocked because it did something silly like fly you through the dome walls into the badlands.
However, if you attempted to fly in that same direction again, in some situations, it would use the same exit that was just created, without all the checks for if it was valid and not doing something silly (which we only did on dynamic exits that were just created).
I've resolved this with a read only check. I've tested, and had a few players test, and flight and other stuff seems to be working fine and the bug is gone.
This likely fixed a bunch of random bugs that people have seen rarely over the years.
It might also have caused issues that I can't foresee, so if you notice something, please @bug it right away.
Typos no longer get submitted through a separate system. Typos are submitted via @bug (you can still use @typo, it's now aliased to @bug). I've updated @bug with a new category id (10) for 'Typo'. Please use this moving forward when submitting typos.
I've also removed all the admin facing typo specific triage tools as they are now unused.
This change will also let the automated scanner identify and triage typos for fixing.
I've implemented automated traceback triage (manually kicked off by me, while I monitor it for now) similar to the bug triage I've already implemented.
This takes a more offensive approach to identifying bugs. Yesterday I implemented code that enhances tracebacks that we detect (but that are not surfaced to the player) with extra data that is then stored in the SQL db, on top of logging them to a channel.
Now, I've implemented a series of MOO verbs that allow an LLM which is connected to our dev server to pull these TBs one by one, investigate them, decide if they still exist, mark them as resolved if they are already fixed, and automatically submit a bug with the issue + root cause + suggested fix.
This should surface tracebacks as bugs for us to fix, without a coder (me) having to manually review old TBs in the logs, and make it faster for us to resolve them because we have enhanced tb info that is not in the raw logs.
(Edited by Slither at 11:29 am on 5/8/2026)
(Edited by Slither at 9:34 pm on 5/8/2026)
Due to confusion I've updated the app help for the messaging app to clarify that when you send a text message via the 'input write [number]' command you should include your message in quotes:
input write 555-1234 "Sup? How's it going you a dumb baka laka this is a quotes string with prepositions and stuff" with prog
The quotes are needed because otherwise if you include 'is' or 'with' or another moo recognized preposition in your message, it will break the verb execution and not work.
I realized tonight that because using - doesn't echo the text back to you, that this text doesn't end up in logs! That's a shame. You miss out on capturing RP if it doesn't log.
Well, it does not. This doesn't change how others see you talking, it just now shows you what you're saying echoed back to you like this:
-Cool.
You speak quietly into your phone: "Cool."
(Edited by Slither at 9:07 pm on 5/11/2026)