If a trigger is active and another trigger is called the plugin will now switch correctly to the new trigger.
The trigger.yml file is now only ignored if it is the default file. Before it was always ignored causing some people to think the triggers were broken.
Triggers with a -1 stay time will now stay until another trigger is called or till the player switches worlds.
Added a reset-on-trigger option in the trigger files. This option is useful when you want to change how the scoreboard interacts when a trigger scoreboard is active and the SAME trigger is called again. Setting it to true will reset the entire scoreboard (starting from 'frame 1') while setting it to false will simply reset the timer.
Triggers now support asynchronous events.
Example of what is possible with the new trigger system:
New default trigger scoreboard:
Code (YAML):
#The event that will trigger this scoreboard with full package name and classname event: org.bukkit.event.player.PlayerJoinEvent
#It will look for this method when getting the player to target, so if the player method is getPlayer() you put getPlayer #You are able to find the method in the javadoc of that plugin, most of them will just use getPlayer as method target-player: getPlayer
#This is the scoreboard that will be displayed when the trigger is called trigger-scoreboard: joinscoreboard
#For how long will the triggered scoreboard be displayed in ticks. 20 being 1 second stay-time: 200
#If the event is trigger more than once during the stay time should it reset the entire scoreboard: # true will reset the entire scoreboard (starting from frame 0 again) # false will just reset the timer reset-on-trigger: false
Ideas you would like to see and feedback are always welcome!