As mentioned, more in-depth descriptions / documentation in text files need to be included in order to act as both general and specific guides.
EDU (export_descr_unit) in RTW is a good example of this - specific unit stats are documented at the top of the file, which unlocks many doors all at once and saves hours of painstaking testing and research by the TW community.
I'm currently modding the campaign map resources in DR (descr_regions) and DS (desc_strat), with a few other files as reference. Since there is no supporting documentation present for these resources, the coding is completely trial and error - the resources are unsorted in a list, with no comments whatsoever. To date, this has been extremely time consuming - repetition is an understatement.
There is a way around the trial and error approach - actually going into the campaign map and taking note of the exact tiles where the resources are to be added / relocated / deleted (using settlements / landmarks etc as origins). Then its the case of using map_regions.tga to mirror the exact tile location (which has already been written down) to position resources accurately.
This indirect approach could've been completely avoided if the resource list was broken into specific regions using semicolons (;) etc to document region / settlement names. This, as a result, would save many hours of taking specific notes on resource locations on the campaign map. This example can be extended to many other text files present in RTW.
Basically, more in-depth developers notes / comments in the text files are a necessity for future products in the TW series.
Bookmarks