We recommend using the Thunderstore Mod Manager or an alternative for installing mods
Plugin for making trigger events cause other events (e.g. light switch turn on a light or level open a door).
This unofficial TaleSpire allows creation of triggers that cause effects to occur. For example, a level or chain can cause a light to go on or off or a level can open a door.
Video Demo: https://youtu.be/KOWhUP4i_yw
1.4.1: Buf fix for exposing instance 1.4.0: Expose Instance to allow relays to be set from other plugins 1.3.0: Added support for wildcard asset triggers 1.2.0: Migrated to Asset Data 1.1.0: Added relay supression to avoid relay reactions on top of relay reactions 1.0.0: Initial release
Use R2ModMan or similar installer to install this plugin.
Set the desired setting using the R2ModMan config for the plugin or keep the default settings.
Warning: This plugin does not work with Core TS props, you need to use a custom asset!
The time interval in which relay Plugin ignores reactions if configurable in the R2ModMan configuration for the Relay Plugin. The value is the number of second in which Relay Plugin will not process any reactions.
Create a file with the extension SUB in a File Access Plugin valid location. This files defines the triggers and effects that the realy plugin will implement. The format for the files is as follows:
The file contains one trigger condition per line with no blank lines. Each triggering condition can appear only once in the file but the effect can have more than one effect. To specify more than one effect (you can have as many as you want), just add more effects starting with the delay such as:
WatchKey is the StatMessaging key that is to be watched for the given asset and state. WatchAssetName is the name of the asset who needs to be changed to the specified state in order to trigger the effects. This can be * to trigger on all assets. WatchState is the state that the watched asset need to change to in order to trigger the effects. Delay is the amount of seconds (can be decimal) that the effect is delayed after the conditions are met. SetKey is the StatMessaging key that is set when the triggering conditions are met. SetAssetName is the name of the asset whose state is set when the triggering conditions are met. State is the value that is set when the triggering conditions are met.
If the State starts with a ~ character, it denotes a toggle. The ~ is followed by the maximum number of states in the toggle. For example, ~2 means toggling between state 1 and 2. Where as ~3 would mean toggling between state 1, 2 and 3. It should be noted that toggle is 1 indexed (so 1 and 2 and not 0 and 1).
The following example SUB file is included with the plugin:
When Lever10 is set to 1, Light01 is set to Torch (turns on a Light using the Light Plugin). When Lever10 is set to 2, Light01 is set to blank (turns off a Light using the Light Plugin).
Relay Plugin has been updated to use Asset Data instead of Stat Messaging. This allows trigger of plugins that use either Asset Data Plugins or Stat Messaging. The trigger can be either source without needing to tell the Relay plugin if it is a Asset Data Plugin source or a Legacy Stat Messaging Plugin source. However, the output needs to indicate if Asset Data Plugin should be used to trigger the output or if the output is a Legacy Stat Message key. By default, the plugin assumes a Asset Data output. To specify a Legacy Stat Messaging output preceed the key with an asteriks. For example:
Asset Data Plugin output:
Legacy Stat Messaging Output:
Please note that the install buttons only work if you have compatible client software installed, such as the Thunderstore Mod Manager. Otherwise use the zip download links instead.
|Upload date||Version number||Downloads||Download link|