raystuttgart
Civ4Col Modder
Done.
Solution: RTFM
"install instructions.txt" after unzip
Done.
Solution: RTFM
"install instructions.txt" after unzip
Does this necessity to change the version being used on Colonization to Original version still apply?Hi guys,
today we noticed again, that some players have not yet heard about the issues in latest Steam version of Civ4Col.
(It is common knowledge in the modding scene but we understand that new players might not know that.)
To explain:
In the latest Steam version (released years ago) GameSpy was removed for Multiplayer.
They also changed something considering mods. - We have no idea why since 2K / Firaxis never answered to that.
To summarize it:
We the People Mod - especially next release version - WILL FOR SURE BE BUGGED if you use that latest Steam version.
Especially in Multiplayer - and even more so with Mods - that latest Steam version causes issues.
In previous releases those bugs with that Steam version may have been minor or rare. (Unless you played MP games.)
Due to the fundamental changes in new release those bugs will be major and certain. (Also in Single Player.)
-----------
In other words:
If you want to play We the People Mod withoug bugs follow the instructions below.
If you want to play Civ4Col Multiplayer games without bugs follow the instructions below.
Revert your Steam installation of Civ4Col to "Original Release version" - which is easily possible.
Simple solution:
Go to your Steam client, and switch back to "Original Release Version" - even if Steam says it is "unsupported".
(Simply ignore that "unsupported", it has absolutely no implication. It is in fact the best version available on Steam.)
View attachment 617101
-----------
If you want to help us prevent bugs, please tell everybody you know playing Civ4Col Steam version.
Best regards
WTP team
-----------
@Birdjaguar
Can you please make this thread sticky?
This has really caused us many issues and we would like to prevent this from now on.
Thanks in advance.
Yes, please do it if you have the Steam version and want to use our mod.Does this necessity to change the version being used on Colonization to Original version still apply?
The only thing, which has changed since this guide was written is that I have written code to detect which version of Colonization is being used. It should now display an error at startup if the "wrong" steam version is used.Does this necessity to change the version being used on Colonization to Original version still apply?
Colopedia (and discussions in the forum).Where can I find the manual for the mod, please?
Gotcha.Colopedia (and discussions in the forum).
Otherwise there is no manual.
It is a free mod, no professional game. Also the mod is still being developed.
Nobody is motivated to write a manual that could be outdated next release.
Somebody mentioned writing a wiki at some point, but that idea quickly died once it became apparent how much work it would be to maintain and enter all the changes with each release. Colopedia has the benefit of reading the values from the same location as the game itself, meaning it self update with each change.Where can I find the manual for the mod, please?
There is a nice button for it on the top left. It's also in the main menu, but if you open it while you are in a game, a few values will change to adapt to your current player as it takes leader discords and similar into account.The question still remains that 'where do I find the Colopedia, please?'
Have you never started the game until now ?The question still remains that 'where do I find the Colopedia, please?'
Well, that is how it is at the moment.It's a heck of a faff using built-in manuals
Well, it is all XML files that can be read by an editor ... but it would not be very comfortable honestly ...If it's in-game only can it be copied to a different machine at all?
You mean crash as in it just closes? That's a new one and I can't really say what could cause that. If there is any error message, then it would help.Team, I'm a long time WTP fan, and have just downloaded it onto my new laptop. Used the Steam version, includiing the 'original unsupported' beta version in Steam. Sadly, whenever I open it up it crashes before the game even opens.
It gets this far (see image) before crashing.
I'm not sure this is a WTP issue, per se, but seeing as the gurus of CivCol live here, I wondered if anyone has any ideas about what I can do? I have tried reloading it, reinstalling it, flicking between versions and using it with, and without, WTP. Help please!
The first thing I would definitely do is get up to version 4.1.Team, I'm a long time WTP fan, and have just downloaded it onto my new laptop. Used the Steam version, includiing the 'original unsupported' beta version in Steam. Sadly, whenever I open it up it crashes before the game even opens.
It gets this far (see image) before crashing.
I'm not sure this is a WTP issue, per se, but seeing as the gurus of CivCol live here, I wondered if anyone has any ideas about what I can do? I have tried reloading it, reinstalling it, flicking between versions and using it with, and without, WTP. Help please!
It's an annoying issue because it seems to work and then suddenly people report super weird issues. One issue is some people experience multiplayer insists on being vanilla only, but there are other issues were it's a mystery why those weird issues are fixed by switching the steam version.4 - Discover that there are issues unless I switch to 'unsupported version' in Steam (although what the bugs are, who knows - certainly not me although I can say the mod seemed to be working)
I decided to hijack the ini file and let the mod write itself to the default mod. This would be awful in a setup with many mods (unless they all do it), but realistically speaking, most WTP players only use one mod.That said, if I do this the next time I launch, I get WTP automatically loading, which is really cool.
It's an annoying issue because it seems to work and then suddenly people report super weird issues. One issue is some people experience multiplayer insists on being vanilla only, but there are other issues were it's a mystery why those weird issues are fixed by switching the steam version.
I decided to hijack the ini file and let the mod write itself to the default mod. This would be awful in a setup with many mods (unless they all do it), but realistically speaking, most WTP players only use one mod.