This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
client_side_scripting:client_scripting_interface-basic_howto [2020/01/10 14:19] boingman |
client_side_scripting:client_scripting_interface-basic_howto [2020/02/02 09:35] boingman |
||
---|---|---|---|
Line 5: | Line 5: | ||
The script is started from the client and communicates by reading information from standard input and writing commands to standard output. A full list of commands can be found below. | The script is started from the client and communicates by reading information from standard input and writing commands to standard output. A full list of commands can be found below. | ||
+ | |||
+ | ===== Before we start ===== | ||
+ | |||
+ | Various and sundry clients are available for this game. For JXClient, the snapshot build as of 27-Jan-2020 is current. | ||
===== Getting Started ===== | ===== Getting Started ===== | ||
Line 59: | Line 63: | ||
| | ||
monitor -1 1 run_stop | monitor -1 1 run_stop | ||
- | |||
- | If you are using an older JXClient release than currently available, monitor commands sent to the script may 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. | ||
- | |||
- | This behavior was eliminated in JXClient by the 15-Nov-2019 snapshot release. Other scripting bugs were also corrected by this release of JXClient. | ||
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.\\ |