CONFIG FORMAT CHANGED!!!! As well as code optimization
Config has changed, please read below:
I'm still slowly prepping for 1.8 - 1.14.4 support which should happen in 2.5.0 release. The latest thing I did was remove the custom enchant and add an unsafe enchant for the glow effect.
The code has generally been optimization a slight bit. You shouldn't notice any significant difference in performance however, since it was just slight.
OnDisable trigger (reloading plugins for example) now closes all RPS inventories, not that it was a problem in the first place but it makes it so that it doesn't produce NPE errors.
Please back up and then delete the existing config.yml file and allow a new one to be generated, if not the plugin will not load.
After that you can modify the new config and change up what you need to. This config is more neater and is getting ready for a few new abilities in 2.5.0, including the INDIVIDUAL_MOB. I noticed that if I keep adding new triggers I didn't want to keep making new config nodes for the default on state, and so any time a new trigger is created even via the API the flag for that trigger will be automatically added in the config. The idea in 2.5.0 is that there will be a disabled_triggers section where sysops can add which triggers they do not want to show up in the RPS menu, let alone just disable the button.
Note: 2.5.0 will modify the permission names for triggers, it will be rps.button.flag_name_lowercased. For now keep it the same