Switching versions

[gchristie]

Is it possible or advisable to use Clovis' mod when playing against the AI, but then using the 1.13b version when playing by email? Or would it be best to use different computers for this? How cumbersome is it to switch between versions if using the same computer?

Many thanks.

[Gray_Lensman]

deleted

[gchristie]

Very helpful, thank you!

[Evren]

NO.

But... You can actually install the game multiple times on your PC. So, what you do is install a vanilla installation of the latest version that Clovis Mod is compatible with. Next, you install Clovis SVF Mod over that installation and I suggest renaming the "Main" game folder (after you install Clovis Mod). Once you have done that, go into the renamed folder and create a shortcut to the AACW.exe file in that newly named folder. Name it something like "Clovis' SVF"

after you get that done... install the second installation of AACW using the normal default name that you normally use and patch up to v1.13b or whatever. You should have a shortcut already, if not create one for this installation's AACW.exe and bingo, you should end up with 2 AACW shortcuts on your desktop, 1 pointing to Clovis' SVF mod and the other to the normal game installation for PBEM or whatever.

I thought it was a yes? That's his quote from the mod thread:

"TO REVERT TO NORMAL PLAY, just move the modpath.ini out from the AGEod's American Civil War folder."

[Gray_Lensman]

deleted

[Franciscus]

This should be stickied. Very, very helpful and concise explanation by Gray.

Thanks

[Clovis]

ONCE AGAIN, SVF doesn't modify anything in the normal game. It's so just IMPOSSIBLE to cause troubles in official version after being installed.


SVF doesn't modify any normal game file. It just install itself in a new folder and places in the Ageod American Civil War folder a file named modpath.ini which foces AACW to load the game.

If you remove this file from the folder, you will revert to normal version. As simple as that. I place mine in the doc subfolder when I need to switch to the normal version.

Uncompatibilities: as SVF doesn't modify anything, there's none I can remember when switching for the normal version.

On the contrary, having placed another mod in the normal folder will create troubles in SVF gameplay (and only it it)if you install SVF from this modified verson, as SVF folder copies to it all the normal file I let unmodded. So files modified by other mods would be copied in SVF folder and create bugs in SVF.

The pain is then just to manually switch the modpath.ini file. If I had more programming skill, I would create a batch file. I can't.

So there is the solution consisting to create 2 folders. BUT that implies to apply the official patches to both folders as some contents of the official patches aren't integrated in SVF install files because the SVF install process will create them in the SVF folder.

So in the end, keeping SVF in the same folder is certainly better to avoid any troubles when playing SVF.

[Franciscus]

OK, Clovis, but as implied by Gray in post 5, in order to have a clean install of AACW that get's easily recognized by the patch instalation routine in order to try beta patches etc, it is better to follow these explanations.
This does not mean that your mod does anything bad to the original files, it is just for convenience
(and I have a 1Tb HDD, BTW )

[Clovis]

OK, Clovis, but as implied by Gray in post 5, in order to have a clean install of AACW that get's easily recognized by the patch instalation routine in order to try beta patches etc, it is better to follow these explanations.
This does not mean that your mod does anything bad to the original files, it is just for convenience
(and I have a 1Tb HDD, BTW )

If you know my mod better than me, fine

But since 2 years, I'm using one unique folder without any trouble. the 2 folders solution is much more triky for update. The official patch installation isn't deceived by mine own routines which are based on winrar, not on the innosetup etch used by AGEOD and don't change Windows registering entries for AACW. Period.

To put it bluntly, what have been said about update paths preceding my post is wrong.

[Franciscus]

Man, are we touchy, or what ??

I think that Gray's explanations are very useful, at least to me. I speak from experience, because once I had installed your mod and then forgot to remove the modpath.ini file (yes, I am human ) before applying a beta patch for AACW and then I had to install everything again. Now, I do not have to worry.
And yes, mod implementation in AGEOD's games could be better.

And finally, I end here this discussion. If you do not mind, I would do as I please, OK ?

Peace

Regards

[Clovis]

Man, are we touchy, or what ??

I think that Gray's explanations are very useful, at least to me. I speak from experience, because once I had installed your mod and then forgot to remove the modpath.ini file (yes, I am human ) before applying a beta patch for AACW and then I had to install everything again. Now, I do not have to worry.
And yes, mod implementation in AGEOD's games could be better.

And finally, I end here this discussion. If you do not mind, I would do as I please, OK ?

Peace

Regards

I really just don't see how the modpath.ini file which is used only by the AACW.exe to play and not by the patch installer could have messed up your install. I'm maybe vouchy but I would prefer have a detailed explanation on this, just because if you're right, there's maybe something I may do. But for now, I'm sorry to say it seems your messed install came certainly from other cause than SVF.

Back to work, in peace.

Regards

[Nikel]

Franciscus, Clovis. Relax, please.


No more quarrels between regulars here, please

[Franciscus]

I really just don't see how the modpath.ini file which is used only by the AACW.exe to play and not by the patch installer could have messed up your install. I'm maybe vouchy but I would prefer have a detailed explanation on this, just because if you're right, there's maybe something I may do. But for now, I'm sorry to say it seems your messed install came certainly from other cause than SVF.

Back to work, in peace.

Regards

I will explain better. I prefer to have one instalation with 1.13b and your mod (which I have not been playing due to lack of time, BTW, and now waiting for the final 1.00 version :coeurs , and another one for applying beta patches. Once I applied a beta, and later decided to go back to the latest official, and had to go the hassle of installing again AACW, patch and your mod. I just prefer the convenience of knowing that the beta patches go the vanilla version.

regards

[Clovis]

Franciscus, Clovis. Relax, please.


No more quarrels between regulars here, please

Don't wory Nikel. That's just I know how my mod is working and Why GL explanations are wrong on this. I explained it softly in my first post. That's just I've been forced to say it more forcefully. But i will repeat it if needed.Not in this thread howewer, there's no need to keep it alive more.

[Clovis]

I will explain better. I prefer to have one instalation with 1.13b and your mod (which I have not been playing due to lack of time, BTW, and now waiting for the final 1.00 version :coeurs , and another one for applying beta patches. Once I applied a beta, and later decided to go back to the latest official, and had to go the hassle of installing again AACW, patch and your mod. I just prefer the convenience of knowing that the beta patches go the vanilla version.

regards

OK. SVF is fully independant of the official to the exception of the AACW.exe file. Ie you can revert back from a beta version to the official one and let SVF untouched and play it ( It suffices to move the SVF folder and the modpath.ini before deleting AACW and replace it in the AACW after the new install). No need to reinstall SVF .

AACW.exe is the unique exception as there's alomost the only official file SVF doesn't copy when installed.

That's why I update SVF with each new bta or official AGEOD patch because I need to implement some of the new data changes in the files I modded too. .

Interesting point I will integrate in the install note.

Thanks

Clovis

[Gray_Lensman]

deleted

[Gray_Lensman]

deleted