Communicating between scripts and/or prims

From SLIS Second Life Wiki

Jump to: navigation, search

Scripts can communicate with each other using commands with the following syntax: 

actiontype:action|value1|value2|value3...

eg. 

set:sloodleserverroot|http://moodle.edochan.com

...or... 

do:rez|Sloodle Classroom|<1.0,1.0,1.5>

[TO DISCUSS: Would we be better prefixing these with "sloodle" or something to make sure they don't conflict with messages sent by non-Sloodle scripts? Is there an LSL standard for this kind of thing?]

These commands may be sent using any communication method - linked messages, chat or, potentially, e-mail or xmlrpc relayed through the server.

Commands used so far are as follows:

  • set:sloodleserverroot|<Sloodle server root>
  • set:sloodle_courseid|<Course ID>
  • set:sloodlecontrollerid|<controller ID>
  • set:pwd|<Prim pwd or object-specific session key> (deprecated)
  • set:sloodlepwd|<uuid>|<pwd>
  • set:sloodlepwd|<prim_pwd>
  • set:toucheruuid|<UUID of avatar>
  • set:controllercode|
  • set:pwduuid|<UUID of object whose session key has been passed as pwd>
  • set:controlleruuid|<UUID of object that will be controlling child object>
  • do:reset
  • do:rez|<Object>|<position>
  • do:cleanup_all
  • do:permitentry|<UUID of avatar>
  • list:inventory

TODO: remove old codes once Sloodle 0.3 is released.

See the Sloodle channels page for details on how to decide which channel to use for your message.


This page is part of the Sloodle documentation
SloodleDocs Home | User Documentation | Administrator Documentation | Developer Documentation | Sloodle Wiki Home
Retrieved from "http://slisweb.sjsu.edu/sl/index.php/Communicating_between_scripts_and/or_prims"
Personal tools