Skip to content

Releases: Barinzaya/twitch-rcon

v0.2.3 - Configurable Retry and RCON Shutdown

06 Jan 21:16
Compare
Choose a tag to compare

Added an option for whether to automatically retry an RCON command if a connection error occurs after sending it. If a command causes the server to crash without a response, this can cause Twitch-RCON to get in a loop of connecting to the server and sending a command that crashes it.

This also reworks the logic for the RCON client so that it will more consistently exit after Ctrl+C is pressed.

v0.2.2 - All-Redeems Config

06 Jan 13:19
Compare
Choose a tag to compare

Added an all-redeems section to the config, which allows the default format to be set for all redeems, as well as specifying extra values that will get sent along with all other redeems. As an example:

[all-redeems]
format = 'space-key-value'
name = 'Barinzaya'

[[redeems]]
reward = 'Attack (Factorio)'
command = '/Attack'
limit = 12

will result in the following command being sent:

/Attack name=Barinzaya limit=12

Note that extra values defined in all-redeems come before values defined in redeems. As an additional note, if there are duplicate values (e.g. name is defined in [[redeems]] in the example above), both values will be included.

v0.2.1 - More Formats

05 Jan 19:01
Compare
Choose a tag to compare

This release adds additional formats that may be specified for redeems. These are:

  • space-key-value: Adds keys and values directly to the command as key=value pairs, where each pair is separated by a space. This does nothing to prevent issues with keys or values that contain spaces. Example: /Attack limit=12 name=Barinzaya
  • space-value: Adds values directly to the command, separated with spaces. This does nothing to prevent issues with values that contain spaces. Example: /Attack 12 Barinzaya

v0.2.0 - Extra Options

05 Jan 18:27
Compare
Choose a tag to compare

This adds the ability to define additional options for a redeem, and they will automatically be formatted into the command prior to it being sent. The format may be specified via the format key.

Thus, a redeem like this:

[[redeems]]
reward = '...'
command = '/Attack'
format = 'json-map'
limit = 12
name = 'Barinzaya'

will result in the following command being sent:

/Attack {"limit":12,"name":"Barinzaya"}

The following formats are currently available:

  • json-map: The default if format is not specified. A JSON map containing the keys and values. An example is shown above.
  • json-array: A JSON array containing only the values specified, in order. For the above example, this format would send: /Attack [12,"Barinzaya"]

If no extra keys are specified, nothing will be added. Thus, existing configurations (containing complete commands) will function as before.

v0.1.2 - Multiple Commands per Redeem

05 Jan 15:55
Compare
Choose a tag to compare

This release changes the way redeems are processed from the configuration file. Before, if there were multiple redeems with the same name, one would be chosen arbitrarily. This probably should have been an error, but wasn't validated. Now, all redeems whose names match will be applied.

In addition, this also adds an optional channel key to the redeem configuration, which may be used to specify which channel the redeem must have occurred on. This may be useful if for some reason you switch between channels frequently, but otherwise isn't particularly useful... yet.

v0.1.1 - Pause on Error

05 Jan 14:14
Compare
Choose a tag to compare

Added a "press any key to exit" prompt when the program exits due to an error.

This allows the error to be seen without having to open the log file.

v0.1.0 - First Release

04 Jan 20:46
Compare
Choose a tag to compare

Initial release, with minimal but complete functionality for its intended use.