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 [2018/02/16 19:38]
karl [Commands to client] add missing request player, skills, spells
client_side_scripting:client_scripting_interface-basic_howto [2019/09/13 13:17] (current)
boingman Updated monitor section to include the ncom command in JXClient RC 1.20.0
Line 59: Line 59:
   ​   ​
   monitor -1 1 run_stop   monitor -1 1 run_stop
 +
 +If you are using JXClient Release Candidate 1.12.0 (or older), monitor commands sent to the script will look like:
 +
 +  ncom XXYYYYeast
 +
 +Where XX is a 16-bit packet ID and YYYY is a 32-bit repeat indicator. Binary data is transmitted in network byte order (big endian). NOTE: Newline characters regularly occur in the packet ID field so reading this line will have to contend with that, simply reading a line will invariably end in error. It is anticipated that this issue will be fixed at some point in the future.
  
 If you type the command __scripts__ in your client you will see our script is still running.\\ ​ If you type the command __scripts__ in your client you will see our script is still running.\\ ​
client_side_scripting/client_scripting_interface-basic_howto.txt ยท Last modified: 2019/09/13 13:17 by boingman