Install the mod to the newly copied version of TC.
(This is so the main program file from steam is replaced with the DVD version.)Ĥ. () Install the patch to your newly copied version of TC.
Download the 3.2 patch from Egosoft's website. Copy the Terran Conflict folder to a new location. Make sure your steam copy of Terran Conflict is patched to the latest version.Ģ. However, a few people cannot get the mod to work with steam for some reason, so the recommended fail-safe way is as follows:ġ. Another advantage is allowing possible conflicts to be seen as if a script is changed it can be easy to find which other mods have changed it unfortunately with the currrent "script store", either xml or pck, the big advantage of git, seeing diffs between the different versions of scripts is wasted.Īssuming you have TC on the PC version of steam, you can just install the mod to your steam copy of Terran Conflict and it should work fine. So when a new steam version arrives, just setup a branch at your current base steam install, check it out (which will rewind any installed mods/scripts), allow steam to update this base then either cherry-pick each script/mod from the old to the new branch, or rebase the old branch on the new one (I think this works, personally haven't tried this yet). It can require a lot more storage depending upon how you install scipts/mods, oh, and of course discipline making each new script/mod a separate checkin, but it allows easier testing of changes (assuming you also take copies of your save directory at important points), by "rolling back" or branching and testing one set of scripts without one or more others. An alternative to a separate directory is using a revision control system - I use git (under Linux but it will work under Windows).
0 kommentar(er)
