PlanetImprovements.xml -- extra unused lines.

Proper Editing

from GalCiv2 Forums
Help me, please... ;)

While fixing_editing this file with some new Icons/Queries gfx references, i noticed a few extra-lines which seems to have been carried over from DL and aren't exactly active or valid (Pain Amplifiers, etc). Is it safe to simply delete these altogether?
Some have the rem (!--) tags applied & others are still there for no apparent reasons.

And a second question;

What is the proper location for a modded version of this file that intends to **Replace** (or overwrite, in fact) the default?
Cuz, if i place it into the named sub-directory (PlanetImprovements) of the Data folder instead of straight into the root itself... all values are doubled up in game! Strange.

- Zyxpsilon.
modding
2,223 views 4 replies
Reply #1 from GalCiv2 Forums Top
About the subfolders as opposed to the root: if the file goes in the subfolder, it is added on to the core file, but if it is in the root, it overrides it.

For the unused lines, the ones commented out (with the
Reply #2 from GalCiv2 Forums Top
Thanks!
Pending or replacing type of effects on data... gotcha.
Secondly, XML files structuring is easier to parse through when ONLY valid stuff gets written in.

- Zyxpsilon.
Curtains - Customize Windows with additional styles
Reply #3 from GalCiv2 Forums Top
!-- and --> or whatever they are (dont remember exactly) just mean that the section of XML within the two strings is unused by the engine. by deleting them, the code within that section is then used by the game. stuff like pain amplifiers are improvements that were created and then the devs decided not to use them for one reason or another. So you can enable them or delete them, it's your call.

-Dave
Reply #4 from GalCiv2 Forums Top
I was more after sizing some file bytes which aren't necessary to make room for mines... but if (REMs!) were inserted by staff, it sometimes means the issue isn't exactly resolved code-wise (well, this reasoning is based on my own design experiences and how a code gets properly developped though).

After deleting these, everything looks smooth anyway.
I only kept the "future" group just for kicks... as a reminder of structural definitions by SD.

Knowing how any of these files will grow exponentially (since, i need to add a LOT of new stuff) later, it only makes sense to find a comfortable editing process and a way to maintain compatibility through and up until TotA is officially released. Which would also get its fair share of editing as far as i can predict, btw.

Thanks all.