The Steam platform doesn't offer services for low costs, it takes away a good slice which would be otherwise invested in piracy countermeasures, such as copy protection, and manufacturing and shipping boxes to local stores. The first issue to resolve for ES is the financial effects of future DLCs for games in development. This is a more or less logical step considering the amount of negative response on the forums so far. Why do I have a feeling this game is "Rebirth" on the old engine before they ran into the wall of."this isn't going to work for what we want to do".
With that said some of the current X3: tc mods WILL work with albionP, although a ton wont work, all counts what they mod, xtc being one that will def NOT work without changes.ĮDIT oh also make sure you save different "profiles" for each different mod inside X3, or you will keep messing up your hotkeys when switching mods. As for the XTC dev's they will of course have to answer if they wish to port it over to albions new stuff, they may very well wish to after they see the new modding/script commands, or they may just find the new commands not worth a port. Also from what the article said, it would not REQ x3:TC but its basically x3:TC with a mod on top of it. They will be changing some of the "hardcoded" stuff and allowing a few more modding options/commands.
Its not save game compatible because they change OBJ files, which ALWAYS destroy save games. Now about albion prelude, from everything i read and understood its really just X3:TC modded. Then to play a new mod i just create a new empty "save" dir, OR to play one of the other 2 mods on my system, id rename SaveXTC12a BACK to just SAVE, and you have your XTC saves ready to go. Now from here i manage my save games by just renaming the current save DIR to things like.SaveToTTYakistart.
I have 4 installs right now(ToTT, XTC, DDTC, and a "clean" install that i use as my backup(i never put mods on it, just copy over to a new dir when i need a new x3).Īs far as save games go in windows 7, just go to users/computernameherer/my documents/egosoft/x3 tc/ So all you need to do is copy the folder (as a new name), and you have 2 working x3s. X3 is not a game that needs registry changes and all that jazz. Consider Terran Conflict as the starting point, and XTC being one branch and Prelude being another :) Be warned that from Egosoft's point of view, the Expansion Region and so on are not necessarily 'accurate'. It's very likely that Egosoft will overwrite some of what we did in XTC in terms of lore and setting - they have a different view on Aldrin and the universe as we had when we created our version of the lore. But basically, 'Albion Prelude' and 'X3: Terran Conflict + XTC' are two completely different things. The downside might be that, well, you probably won't be able to play the 'Prelude' plot in XTC. This also means we won't need any extra time or anything, as we won't have to port anything over. We still are making our mod for X3:Terran Conflict - as was always intended -, and you certainly won't need 'Prelude' to play XTC or vice-versa. To clarify - XTC will not require 'albion prelude', and we won't move our development either. One thing for sure: this is not going to have anything to share with XTC - neither development nor compatibility (meaning, it's a totally different thing).