RPG Maker Forums
One comment first:
This is a usability feature without any function on its own, as an option for later plugin writers.
Description of the Feature:
In that way, it would be similiar to the "meta" function of reading tags in the notebox, but without further crowding on the notebox, allowing a much more user-friendly way of storing data for plugin use.
Code for Implementation:
The core engine will not need any additional code as this would be for plugin writers to use (optional: provide a meta-function for ease of use)
The data structure will need a new custom type stored for use here, but this would be similiar to existing types
The editor will need a new entry option on the trait windows, but again that would be similiar to the already existing options like "Parameters"
Mockups:
Why is this feature good?
Possible issues with this feature?
This is a usability feature without any function on its own, as an option for later plugin writers.
Description of the Feature:
- Add a custom option to the trait windows, allowing to store a combination of a new custom type with a number
- Add a new list "custom types" to the types tab of the database, similiar to the existing type lists (like skill types) for the feature above
In that way, it would be similiar to the "meta" function of reading tags in the notebox, but without further crowding on the notebox, allowing a much more user-friendly way of storing data for plugin use.
Code for Implementation:
The core engine will not need any additional code as this would be for plugin writers to use (optional: provide a meta-function for ease of use)
The data structure will need a new custom type stored for use here, but this would be similiar to existing types
The editor will need a new entry option on the trait windows, but again that would be similiar to the already existing options like "Parameters"
Mockups:
Why is this feature good?
- The notebox is already overcrowded if you're doing a plugin-heavy project. This feature would give an additional option to store data for plugin use, but one that is a lot better visible and usable compared to adding another line to a notebox that already contains several dozen entries (especially if they're some of Yanfly's lunatic code tags or action sequences)
- The trait list allows multiple entries of the same trait, giving this options that don't exist with the default meta function (which only returns one value for a tag).
- The traits are automatically collected on the actor no matter if from equipment or class or actor itself. No need for a plugin writer to check different noteboxes on equipment or class etc
Possible issues with this feature?
- The required change in the data structure (especially the need for the custom types) will probably cause an effect similiar to when the child generator tab was added (need to edit existing json files for compatibility), only this time in the projects themselves. Might be prevented by storing the new data in a new file.
Latest Threads
-
-
-
Fixed GALV Projectiles or QABS | Your opinion | Evented ABS (4 Viewers)
- Started by KotoYama
- Replies: 0
-
Latest Posts
Latest Profile Posts
People3_5 and People3_8 added!
forums.rpgmakerweb.com
Tonbi's MZ material factory
That is ok. I know the rest of the Actor 3 Set...
so hopefully tomorrow i get to go home from the hospital i've been here for 5 days already and it's driving me mad. I miss my family like crazy but at least I get to use my own toiletries and my own clothes. My mom is coming to visit soon i can't wait to see her cause i miss her the most. 
Holy stink, where have I been? Well, I started my temporary job this week. So less time to spend on game design...
Cartoonier cloud cover that better fits the art style, as well as (slightly) improved blending/fading... fading clouds when there are larger patterns is still somewhat abrupt for some reason.
