ScreenEffects

• Fixes the success message for registering a screen effect group ignoring the .disable_reload_message flag.

• Fixes #1
• ‼️ Replaced the public function scrfx:add_screen_effect with two new API functions.
• Added API function scrfx:api/register_screen_effect/register_group which accepts two macro arguments storage, and path like the old function.
  • This registers all screen effect definitions in the list provided.
  • Throws an error message if the provided screen effect group does not exist.
• Added API function scrfx:api/register_screen_effect/register_definition which accepts two macro arguments storage, and path.
  • This registers the screen effect definition provided.
  • Throws an error message if the provided screen effect group does not exist.
  • Note: In the future, I might add data validation for easier debugging :).
• Changed screen effect definition and group schema, see the README for more info.

• Support for 1.21.6-1.21.8
• Removed redundant .dev_mode flag from scoreboard scrfx.zinternals.globals
• Added a better reload message.
  • You can disable this by setting the .disable_reload_message flag from scoreboard scrfx.zinternals.globals to 1.
  • There's also clickable text in the reload message that does this for you.

• Changed how datapacks register screen effects.
  • You will now define your own storage containing the screen effect definitions.
  • Once you have done that you can run the scrfx:add_screen_effects function which take in a storage and a path argument.
• Changed callbacks.
  • Instead of having only two options on where to run commands, You can now run commands on any frame you like.
  • The middle and end fields have been replaced with one callbacks field because of this.
  • It is a compound which contains key value pairs, the key being the frame number and the value being the command.

You can read more about this inside README.md#registering-the-screen-effects.

• Backwards compatibility now works for 1.21.1.
  • ⚠️ 1.21.2 - 1.21.4 compatibility has not been tested yet. Please report bugs on the issues tab.