I understand that RMMV and it's predecessors are designed to be standalone but many people use external programs to enrich the content being developed and I feel it is encouraged for more than basic output. Creating easier pathways for users to accomplish this may benefit both the platform and empower users in ways that set RPGM at greater distance from similar programs and make it equally or more approachable at the same time.
I dont make a secret about my non-developer status, at least in context to games. I develop things in Excel and Access but that's an entirely different structure and mindset than what we do here - mostly.
Workflow and good practice is typically universal across any development platform. With that, there are things I hope RMMV dev teams incorporate especially now they've move from Ruby to JS.
1.) create a template database in XML and CSV for use in external editors (like Excel, Numbers, Sheets, or Open Office) with the ability to import directly to RMMV. This would offer users better control and broad access to a straightforward development of game mechanics.
For example, the template would have pre-defined table headers and the user would fill in the content directly. If I wanted to have my characters multiclass, it's just a matter of flipping a switch in RMMV so the XML or CSV header was read, otherwise ignored. Then if the primary class was FIGHTER, any subclass of FIGHTER would become part of the FIGHTER class tree. Likewise, if a developer wanted to incorporate TRAITS / SKILLS / SPELLS to classes or subclasses they could assign them in the same fashion in one direct approach rather than one at a time. I can write things like this in VBA quickly and easily, but because I dont know the platform of RMMV anywhere close to what I know Excel, AND it would require tampering with the core script I would be more comfortable leaving it to the official Devs.
2.) Direct exportation of assets to popular external applications. Rather than hunting down the different folders for tilesets, character faces, etc - do a 'lump and dump" to a folder for quick and easier access with PS, GIMP, TileD, or any other editing program and add an import switch to pull back to RMMV. I just requires a strict naming structure for files but that's actually a very minor and simple thing in any program.
What are other things you'd like to see?
I dont make a secret about my non-developer status, at least in context to games. I develop things in Excel and Access but that's an entirely different structure and mindset than what we do here - mostly.
Workflow and good practice is typically universal across any development platform. With that, there are things I hope RMMV dev teams incorporate especially now they've move from Ruby to JS.
1.) create a template database in XML and CSV for use in external editors (like Excel, Numbers, Sheets, or Open Office) with the ability to import directly to RMMV. This would offer users better control and broad access to a straightforward development of game mechanics.
For example, the template would have pre-defined table headers and the user would fill in the content directly. If I wanted to have my characters multiclass, it's just a matter of flipping a switch in RMMV so the XML or CSV header was read, otherwise ignored. Then if the primary class was FIGHTER, any subclass of FIGHTER would become part of the FIGHTER class tree. Likewise, if a developer wanted to incorporate TRAITS / SKILLS / SPELLS to classes or subclasses they could assign them in the same fashion in one direct approach rather than one at a time. I can write things like this in VBA quickly and easily, but because I dont know the platform of RMMV anywhere close to what I know Excel, AND it would require tampering with the core script I would be more comfortable leaving it to the official Devs.
2.) Direct exportation of assets to popular external applications. Rather than hunting down the different folders for tilesets, character faces, etc - do a 'lump and dump" to a folder for quick and easier access with PS, GIMP, TileD, or any other editing program and add an import switch to pull back to RMMV. I just requires a strict naming structure for files but that's actually a very minor and simple thing in any program.
What are other things you'd like to see?