GRIDSIGHT(TM) FIXED
Fixed a bug with GridSight not working on some terms.
banner art by Michal Lisowski
There was an issue with the factions code that made it so if two people that were liked by a group, were in a room with group members, the victim would ALWAYS get the backup, if the two people fought in front of those NPCs.
Now, the backup goes to the person with the highest faction standing.
I've updated the results when you run a command to see what commands a device or location offers. The results when a command takes an argument have been updated to give a better idea of what is expected.
For example:
add_sic_guest => add a SIC ID to the guest list for X amount of seconds
– ARGUMENT 1: STRING with length between [12-12] (SIC ID)
– ARGUMENT 2: NUMBER between [1-2419200] (EXPIRY SECONDS)
Previously (SIC ID) and (EXPIRY SECONDS) were not present and you had to guess what the command wanted. Should be more clear now.
Mag lev entrances are now scannable and deckers can do stuff to them. Find out ICly what they can do.
(Edited by Slither at 1:36 pm on 8/1/2025)
If you are using Gridsight(TM) cyberware, you should no longer be seen typing into your terminal periodically the same way others would be that are not using a super cool cyberware.
If you had a node with a line of text that was partially colored, the default-color for your term wasn't being applied.
I believe I have resolved this, but I had to make some changes to the way colors were applied. It's possible this has broken something that I haven't noticed. So please @bug any color wonkiness with nodes or terms in general.
(Edited by Slither at 10:14 pm on 8/1/2025)
You can also get the progia number for the device, the last incoming call number, and last outgoing call number.
Grid 3.0 doesn't pass the topic id when a new topic is created, so I can't do the notification with the ID [34330] like I want. Instead, if the topic id doesn't exist it will just say [Grid 3.0] instead of the ID. You can still go look at the topics in the forum and read it no problem, but the notification won't have the topic ID for new topics.
This was causing people to be able to see in the dark after death. I think I've resolved the edge case that was causing this.
When you view a node there is a new top line item that shows the date the content on the node was updated.
Fixed a bug I introduced yesterday with a change for another bug fix. You should be able to toggle again.
You now need to hold things to trash them. This should also prevent cuffed people from trashing things that aren't already in their hands.
I've removed the ability to use wildcards (% and _) in these searches. It was not intended. Clever to those over you who figured it out, but sorry, not intended :)
Brlang nodes have been updated to call this out.
There was a running out of ticks TB on very large content nodes. I've fixed this.
This language was not selectable if you were able to select a second language. This is due to it being renamed way back but chargen not updated. I've fixed it.
There was an unlisted option for feed-color that wasn't showing up in g options. I have added it.
There was a bug in listing the commands for terms causing a TB. I missed a descriptor for the type of value that was able to be passed as an argument. Fixed.
Daemons have not been released yet, but I'm adding some stuff around them. You'll notice daemon options in 'g data' moving forward and a MAX KNOWN DAEMONS in your g specs.
More details on daemons and what they do when I am done coding them.
Fixed a bug in renaming known locations/devices where if there was an error it kept executing.
You can now view the node source code of nodes you own or are on the ACL for, even without programming skill. I realized this was important for people who want to update nodes and don't have a local copy of it.
Fixed a bug in resolving an alias to a SIC ID using a grid program, which was causing a TB.
I have identified and fixed the bug that was causing PCs to put weapons away during combat. It was not random. Here was the situation and the context:
Player A is in a room with Player B and NPC A.
NPC A likes Player B (and will join combat to fight anyone who attacks them)
NPC A is holding something that IS NOT their best weapon (a progia, instead of a machete, for instance)
Player A attacks Player B
– Combat is created
--Player A joins combat.
-- Player B joins combat.
-- NPC A is notified that combat is happening
-- NPC A checks and realizes they like Player B
-- NPC A joins combat, attacking Player A.
----- NPC A executes 'hold best weapon' as part of joining combat
--------- hold best weapon checks if the NPC is holding something and finds they are
-------------- NPC runs 'freehands' command
------------------- freehands command uses the 'player' variable to see what items are being held in their hand, getting the WRONG item because 'player' is the player that started the combat in this context, then sheaths that object
-------------------- Player A sheaths their weapon
This was a difficult bug to identify. For anyone that knows MOO code, the 'player' variable in a verb is set to the player who initiated the initial verb that triggered any additional verbs to be called. 'freehands' was not designed to be called programmatically and was using 'player' instead of 'this' where this is the object the verb is being called on.
I've resolved the issue, and it should not happen anymore. If anyone sees this happen again, please @bug right away so I can investigate.
Apologies to anyone who was impacted by this bug.
I've added the relevant daemon specs to this command, so you can see what your term supports.
Updated the documentation for daemon creation. Specifically removing the mention that daemons are destroyed when they reach 0 ice, as that is not the case, I went a different direction :)
Bars now have a new player accessible command: @submit-drink [bar]
Players who own the bar or are on the bar roster can use it to submit drinks
ADMIN CAN
@manage now has a new option (8) for admin to review player submitted drinks. They can edit the messages. It will automatically create the drink for the admin.
Admin will still need to add the drink to the bar after it is created.
Daemons were only intended to monitor one thing. Multiple monitor commands in a daemon should have been prevented but I missed that in both my code and the documentation. I have corrected this. I believe this will resolve some of the issues people were seeing with daemons not monitoring things properly.
You can now scan retinal doors if you are wearing contacts. The code considers you to have your eye uncovered in these situations.
I've added a new bit of code which can tell if a person is visibly disguised, and have begun using it in some places the code simply checked if someone WAS codedly disguised. This should make those with high disguise scores, walking around as other people with different names, work better.
This applies to:
- selling items at stores
- delivering crates
- scavenger npcs that want items
- NPCs that want items
It does not apply to the bank, and several other areas where it is problematic to deal with disguised people. The bank in particular is super annoying as it uses the literal character name in some places as it is super old code.
Hopefully this improves the experience for disguised folx.
I've added #anchorlink NodeName Description of link here#endanchorlink as a node tag. The NodeEditing node has been updated.
Devices, Locations, and Daemons were showing up in no particular order when you used 'g data view devices/daemons/etc'. I've updated these so they order by the timestamp, from oldest to newest.
There was an issue with the aliases used for paying a disguised person (who was not visibly disguised). I think I've resolved this. Mench is going to have it tested when the reporter is online again.
This was generating errors, and is now fixed to show a pretty error defining the issue (node is invalid).
There were 2 NPCs which were asking for 2 different drugs, but only accepting one. Fixed.
This no longer lets you set an all caps name. It will lowercase the whole name, then capitalize the first letter.
I've updated the g links / g link code to refactor it, and make it support types of links better. All links that were cached in your session have been cleared to make way for the update, but moving forward, topiclinks, anchorlinks, and gridmail links, along with regular #link tags should get logged to terms correctly.
I've updated the messaging daemons receive when things happen on devices they are monitoring to make it more clear in cases where a backtrace isn't happening, that the notification is simply a detection of activity on the device
DAEMON MONITORING DAEMON INSTALLS
Daemons will now receive a notification if they are monitoring a device and a new daemon is installed on that device.
Fixed what I hope is the final lingering bug with links. Links should be working for non anchortag links now.
The 'node name' across all Brlang commands should now accept 50 characters of input and not 20, making it match the maximum node length.
If anyone has issues (if I missed a command) let me know via an @bug and I'll fix it right away.
The BrlangNode documentation has been updated as well.
I previously made @voice show up on all messages on a progia, but only did this for the '-' command and didn't do it for 'to prog message'. I have updated that code as well and voice should be coming through all the time now.
The following node tags have been added:
#rotating-message
#ordered-list
#unordered-list
#blinking-text
You can view info on how to use them on the NodeEditing node.
For tags like #ad that define a length, I've updated them all to 150, to standardize them. This doesn't impact other tags that don't have a set length (like #table).
Added a few new node tags:
#header
#progress-bar
You can read about their usage on the NodeEditing node.
The NodeEditing node was getting too big so I broke it out into NodeEditing and NodeEditingAdvanced. I also updated the documentation in several places.
I've also added a new #weather tag which shows the current weather with a little ascii visual of the weather, and a screen reader readout of the weather for those with accessibility turned on.
If you have a connected grid term to your gridsight and the term leaves your body, it will automatically disconnect and you'll see a disconnect message. This will happen if it is wrested, dropped, stolen, etc. I think I got all the cases, but if I missed any, let me know in an @bug report.
The grid playtip has been fixed, and logging into Grid 4 will trigger it.
I've upgraded our GPT integration, broken the code out into its own small app, and updated us to a newer version of GPT (4.1 nano). It should be pretty fast, is running on Node 22, and the server has been updated so it dies less often (hopefully).
I have added an OOC tell message suggesting people add a note about their current mental state, during the clone update process.
If your gridsight is linked to a term in your inventory, you can 'use term' without holding the term in your hands. ONLY works if you are linked to the term already. Lets you switch to using a different term (like a street term or held term) then switch back, without it being visible to anyone but you.
I used my trusty friend GPT5 which is getting pretty darn good at MOO code to review all 16k lines of code + properties and flag issues for me to review. It actually found a bunch of stuff that I had missed in my original reviews. So many I won't list them all, but generally:
- Fixed a lot of node/program/daemon messaging
- Fixed a bunch of bugs that would have resulted in TBs in edge cases across all grid code
- Fixed the code comments for a bunch of verbs with copypasta issues
- g programs scheduled was showing the wrong time
- Fixed a bug with notifications not being cleaned up properly
- A bunch of other stuff
Mostly typos fixes and verb documentation, but I did fix a few bugs that hadn't been spotted by players or that might have caused some confusion down the line.
If you are fully (name change) disguised, people that ask for random items will now pay you. Thought I had fixed this before but missed an issue. Resolved now.
(Edited by Slither at 5:13 pm on 8/31/2025)
