Description of the Feature:
A lot of people have been asking for the option to sort the database and change the IDs of anything there.
However, because the entire engine is ID-Based, that is NOT easy to implement - not even with the suggestion of refactoring the ID-count, because there are too many direct ID-assignements in the corescript or in plugins (starting with the fact that the attack skill is always the skill with ID=1, that prevents easy refactoring the skill-IDs as an example).
So I suggest an alternative approach that should bypass those implementation problems:
Add a new string to each database list that is completely ignored by the engine, but allows filtering or sorting in the editor.
Besides a new field for it on every list tab it would need a button to change the list itself from ID-Based to the new string and back, and buttons for sorting on the new values/strings
Why is this feature good?
Possible issues with this feature?
A lot of people have been asking for the option to sort the database and change the IDs of anything there.
However, because the entire engine is ID-Based, that is NOT easy to implement - not even with the suggestion of refactoring the ID-count, because there are too many direct ID-assignements in the corescript or in plugins (starting with the fact that the attack skill is always the skill with ID=1, that prevents easy refactoring the skill-IDs as an example).
So I suggest an alternative approach that should bypass those implementation problems:
Add a new string to each database list that is completely ignored by the engine, but allows filtering or sorting in the editor.
Besides a new field for it on every list tab it would need a button to change the list itself from ID-Based to the new string and back, and buttons for sorting on the new values/strings
Why is this feature good?
- allows for custom sorting on the new string in whatever way the user wants
- does not mess with the IDs like the other suggestions
Possible issues with this feature?
- Still a lot work and a change to the json files required, just not as much problems as trying to do the same with the IDs
