User Tools

Site Tools


client_side_scripting:client_scripting_interface-basic_howto

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
client_side_scripting:client_scripting_interface-basic_howto [2021/04/11 16:58]
partmedia Reorganize top
client_side_scripting:client_scripting_interface-basic_howto [2021/06/19 08:12] (current)
boingman [Using Scripts in the Client] Add further information about JXClient script management.
Line 11: Line 11:
   * ''​scripttell <id> <​string>'':​ send text to currently running script <id>   * ''​scripttell <id> <​string>'':​ send text to currently running script <id>
   * ''​scriptkill <​id>'':​ stop currently running script <id>   * ''​scriptkill <​id>'':​ stop currently running script <id>
-  * ''​scriptkillall''​ (JXClient only): stop all currently running scripts 
  
 +  * JXClient only:
 +    * ''​scriptkillall'':​ stop all currently running scripts
 +    * Unique alphanumeric substrings of <​path>​ may be used as <id> so that script names may be used in lieu of numbers
 ===== Writing Scripts ===== ===== Writing Scripts =====
 The script must be executable (e.g. ''​chmod +x''​ with an appropriate shebang). For some languages, it may be necessary to write a wrapper script to start the program. Additionally,​ on Windows systems where the shebang is not supported, the player must provide a means of running such a script. For example ''​script python <​path-to-script>''​ if you are using python. The script must be executable (e.g. ''​chmod +x''​ with an appropriate shebang). For some languages, it may be necessary to write a wrapper script to start the program. Additionally,​ on Windows systems where the shebang is not supported, the player must provide a means of running such a script. For example ''​script python <​path-to-script>''​ if you are using python.
client_side_scripting/client_scripting_interface-basic_howto.txt ยท Last modified: 2021/06/19 08:12 by boingman