What I'm doing is copying over rules and profiles into the GST file, the main game file for 40k. The catalogs, the .CAT files, can then reference it instead of them each having to have their own copy of the rules/profiles.
I'm still trying to understand the point you're trying to convey with matching id codes in that
No, they're not. I just did a random spot check on a few, and the ID codes for rules are not matching.
Good thing is, no files will break on day of release. It's up to the person making the file if they want to use the shared versions or not, this will just help reduce file size for almost every file that gets synced
Besides, if we set up the shared ones with the same IDs as existing data files, that would actually break something
so if I go in and spot check three random ones, they will all three have the same ID in shared rules, is that what you're saying?
The fact remains though, if we set it up with the exact same ID for them, it would break the files. When somebody tried to create a roster using those books, it would find duplicate IDs for the rules and cause it to crash
This will accomplish roughly the same thing, only instead of each rule being in each file, they will be in the GST. If the IDs are doubled up, one in the GST and one in the data file, it will very likely cause issues
let me do it right now
For this I set the ID for the Bulky special rule in the KDK file to the same ID as the one in the GST.
We don't want the IDs to be the same in the GST file as they are in the CAT files.
To all other data authors: This is how the Shared Rules section for KDK looks now that I started switching rules over to the GST. I'll put it up in a repo soon so you can all start converting over also if you wish. This will not be necessary if you choose not to.
out of interest, and sorry if this has been covered (i've not really kept up with the alphas) but does mean we could in theory have a file for the Space Marine Forgeworld units & link to them from the seperate army datafiles
If you scroll up you can see some screenshots of what I've done so far. it is really easy to work with this way, and is less reliant on updating multiple files if they change something major like the wording of a rule in 8E (if and when it comes out years down the road)
Wait a sec, I had an idea... if we reset the data files and GST to version 1, it will prevent it from auto updating on anybody's system that has a higher version number than that. But, anybody who is doing a fresh install of it will get the newest data. This way nothing of the old stuff will break, but we'll still be able to continue on BAU
I know there was discussion a while back about fortifications... should we use this as an opportunity to roll the fortifications from Stronghold Assault into the main data file? This way we can actually use that part of the FOC vs taking an entirely separate detachment just for fortifications. Thoughts?