Re:
Ok, maybe not the place to suggest it, but here's one thing I think would be great, and could make life easier for both the developers and the folks to who do the work to figure out the 'delta' in all the new patches. It's kind of a self-documenting patch feature also.
The developers could write some build targets to automatically generate "null" mods for all the defined game spells, items, creatures, nations, spells, etc, from the original source code base at the time they build the patches. Then deliver these full-content and authoritative null mod files as part of the patch. Once setup, it's easy for the developers since they never have to do more extra work per release to detail what has changed and what is current. And it's super easy for us users, since we always have the ability to check these 'database' parts of the content directly, and nobody needs to do has extra work to create big (and error prone) null mods every time a patch is out (no string searching executables, finding new unit numbers, weapon slots, and trying to decompose *trs files, etc.) As a bonus, it becomes a great modding tutorial in itself, so you can see exactly how the modding commands correspond to the creatures, items, etc, that already exist and use them.
It would also make it easier for us to do larger scale or longer-term projects like a total conversion mod. If I start a lot of work to mod changes into 3.14, and it takes a year to finish, I want it to be easy to propagate those changes into the current 3.xx without having to research the changes in each version between .14 and .xx and manually update things.
Sill
|
Threaded Mode