Suggestion: Ability Groups - More organized power JSONs #206
Labels
No labels
documentation
duplicate
help wanted
invalid
Palladium 4 / 1.20.1
Palladium 5 / 1.21+
question
Review requested
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ThreeTAG/Palladium#206
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Right now the
abilitiessection in a power JSON is just a huge lump of different abilities. While the current system of just writing down every ability on its own makes sense, it also doesn't take into account how there're abilities, that even though are different, are used together for achieving some goal and are not just separate abilities (conceptually).Hence I suggest "Ablity Groups". It's the idea of letting addon-makers the option for grouping multiple abilities in a couple of curly brackets, with a
group_namekey at the top of the brackets. These Ability Groups would help manage and design clearer and better readable power JSONs.From a technical view point, these additional grouping brackets should be completely optional and only visual. They shouldn't have any impact on how the power works, and the addon-maker should be capable of nesting the Ability Groups.
(Since they would be optional, backwards compatibility is promised).
I have seen really messy, long power JSONs, and I think this could make them much easier to navigate. And also, reverse-engineer for anyone learning from existing power JSONs.
Ability Groups: More organized power JSONsto Suggestion: Ability Groups - More organized power JSONs