GrognardsFromHell
Parse protos and description sub folders feature
In zmod I already have 198 protos, including combined files for scrolls, wands and potions. Most of them are generalized, but some are related to specific module.
As a game designer I want to separate files into folders to have structure and order. Thus sub-folders are needed.
Also I want to unparse essentially all protos from proto.tab to understand which protos I can remove, as I most likely will have to reuse proto ids.
Why limit it to protos though? It sounds to me like the more general demand is for modularity - i.e. to have several modules load on top of each other, with specific content modules built on top of infrastructure modules (spells, items, crafting rules etc).
Not sure I understand your second request, is it a separate issue?
Not sure I understand your second request, is it a separate issue?
This is just additional argumentation why this feature is usful :) (these are tasks for myself)
Off course I agree with general approach. Although it would be nice to specify exactly what it will affect.
- protos
- description
- scr?
Now expanding scr would be grand. I would love to separate spells, traps, common proto script events, module script events etc.
Another requirement is order - sub folder probably would need to be found first, and then root.
Just to be clear, the idea is to have sthg similar to the new overrides folder setup. I.e. the subfolders aren't at the data-type level (e.g. subfolders within protos), but at the module level.
Mine idea is simple.
But to be honest I do not understand yours. It's obviously different, perhaps evn potentially could handle mine's as well.
Can you elaborate more please?
Your idea is simple, but not general enough, and would generate lots of work to apply the same for every type of data - i.e. I'd have to add sub folder support to scr, and then maybe descriptions/long descriptions, and who knows what else - I foresee that I'll keep getting requests to add this or that.
So instead, let's have the subfolders as packages that can contain whatever you want (protos, mesfiles etc), and load them similar to how the overrides folder is handled now. Basically the overrides folder does this already, except I guess you'd probably want to load it at a lower priority than overrides (but possibly, higher than data folder), and also include support for dat files.