Uncomment next statement if you want to make this script same channel open on their listen handle Change ONLY when speaking to an object with the Set key to UID of object or avatar you wish to direct the chat to uncomment the following statements and change to suit Function to control how information is output Change these command strings in case of conflict link number containing the script you wish to control. and then chatting "/link_number ON/OFF/DONE" where link_number is the integer of the by uncommenting the line within default > state_entry > "listenChannel = llGetLinkNumber() " For multiple prims, each script can be individually addressed with chat commands Chat "DONE" to end debugging session and script(s) will remove themselves. Chat "OFF" to silence and "ON" again for chat reports. and the script(s) will begin repeating link messages on chat to the owner. to monitor the link message traffic within. USAGE: Place a copy of script in each prim of a linkset that you wish (Credited to suggestion made by Sassy Romano) VERSION: 0.5 1/4/04 - Added uSpeak function to control output mode
This header must remain intact when copied, modified or used A debugging script for chatting of intercepted Link Messages
#LSL SCRIPT DEBUGGER FOR FREE#
The script itself use, modify, pass on for free as you wish. Calendar: LinkMessage Monitor in Link #1 is DONE! Calendar: LinkMessage Monitor in Link #1 is Now OFF Calendar: LinkMessage Monitor in Link #1 is Now ON The message protocol is: COMMAND string: "T", DATA integer: current_time, MODIFIER key: an alarm key when necessary: LepreKhaun: ON
#LSL SCRIPT DEBUGGER UPDATE#
To : link number of prim message is arriving atĪ sample debugging session, checking on a timing "heartbeat" from a (brain) script in link 2 to a (user interface) script in link 1, which uses it to update a clock/calendar every 60 seconds.The format of the chatted reports (which also might be easily changed to suit one's needs) is: This allows you to "tune in" as needed to specific parts of the interactions in complex arrangements.Īlso, the commands ("ON", "OFF" and "DONE") can be changed if they conflict with your existing application chat commands. As in (addressing a monitor in link #3) "/3 OFF", "/3 ON", "/3 DONE". Say "OFF" to quiet them and, when you're finished with the debugging session, chat the word "DONE" and they'll remove themselves.įor advanced usage within multiple prims, one can uncomment the line within default > state_entry > "listenChannel = llGetLinkNumber() " This will make each monitor separately addressable, simply proceed a command with the link number as a channel. One simply places a monitor script in each prim of the linkset one wishes to eavesdrop on and chat "ON" to have them begin monitoring the traffic.
I made the usage of LinkMessage Monitor as simple and straightforward as possible. That way one can check that the messages are:
So a monitor script only has to be placed within the prim(s) you wish to listen in on and then communicate to you what traffic they overhear.
In other words, all scripts within a link node receive a link_message addressed to that link. Link messages aren't so much script to script as they are link node to link node. This is the program I wrote for this and I'm sharing it with the community for others that may have a need for such. I asked ChatGPT to write some LSL script for secondlife to teleport an avatar, it delivered a script and explanation, I asked it to amend the script to show some hovertext and it invented 2 new LSL events.While working on a calendar/scheduling application that has (at the moment) three scripts messaging each other, I found a need to monitor the messages to debug the interactions.
0 kommentar(er)
