[Feature Suggestion] An "Extension Packs" System

[pongo1231]

Add the ability to download extension packs inside the config utility. Extension packs are able to modify the mod by making use of the systems already in place in the mod and are (primarily) provided through Git repositories. For now the focus of extension packs are custom effects which make use of the Lua scripting capabilities of the mod, though this could be broadened at a later point to also provide other features (e.g. presets or translations). Users are able to easily view and install extensions and manage those through an user interface in the config utility.

• [x] Implement basic extension packs system (list extensions packs with their corresponding names, descriptions and icons, also allow users to install, update and uninstall extensions)
• [ ] Allow users to add their own sources for extension packs
• [ ] Allow extension packs to define their own options which can be viewed and managed in the config utility
• [ ] (Potentially?) Allow non-Git sources (through the use of an JSON file pointing to all extension packs instead)

[anto4440]

Alright, this is all a bit confusing to me since I'm not that technical. So what you're saying as that this will allow users to easily download mods for the mod in the form of extension packs.

[pongo1231]

Alright, this is all a bit confusing to me since I'm not that technical. So what you're saying as that this will allow users to easily download mods for the mod in the form of extension packs.

Essentially yes. While the functionality for adding custom effects is already there (that's what the custom_scripts folder is for) this will enable people to easily install those as extensions and to share their own ones.

[TheRealAyCe]

Shouldn't most effects that are one-time and not performance-heavy be converted to Lua then, to make learing to create effects easier for people?

[pongo1231]

Shouldn't most effects that are one-time and not performance-heavy be converted to Lua then, to make learing to create effects easier for people?

Currently that isn't feasible due to custom effects not being customizable in the config utility and requiring people to edit the script themselves. There's documentation in the wiki already and the plan is to release some sample extensions which will demonstrate the capabilities of the system.

[pongo1231]

Initial work started with 9f8049a80e77704bc1c1532c74e924a2a6a9ba1a.

Rather than using Git repositories to host them there will be a web portal through with developers can upload .zip files containing Lua scripts (and later on effect sound files as well).

[pongo1231]

Frontend is functional and has all the basic functionality intact.

[Rylxnd]

What if we could add like a change log (separately from the description) for when a submission is updated?

[pongo1231]

Any reason just using the description to mention changes doesn't suffice? The character limit of 600 could be increased if length is a concern.

[Rylxnd]

The description is limited to 5 lines. And when writing a change log you usually do it in a list like:

• fixed bug
• added this
• changed this
• removed this
• this now does this

With 5 newlines limit, you can't really list off changes. Unless not in a vertical list. But a vertical list is easier to follow.

[pongo1231]

Implemented now, you can describe the changes of a version and have it be visible through the webhook

[Rylxnd]

❤️