I may be somewhat of an oddity, but I've been playing Civ III in it's 'virgin' form for 3 months now - that's right, I have yet to install any kind of patch. I've read time and time again how great the patches (and how bad the bugs) are, but my question is this - if I don't think the game is broken, should I bother fixing it? My fear is that I won't like the patched game. I already know there are little things (horsemen no longer retreat, science max is upped to 40 turns) that I don't like about the patches. So, with 2.0 supposedly coming out - should I bother with it if I'm already happy?
Announcement
Collapse
No announcement yet.
To Patch or Not to Patch
Collapse
X
-
I'm going to be completely and honestly blunt with you right now. You are a complete idiot for not patching up to 1.21. Please rectify your mistake at your earliest convinence. I can understand not using the previous patch due to AI tech trading, but not for 1.21. All the things you do not like, such as science max/min, can be changed in the editor.
-
Frantz - Don't worry bro, EVEN though you called me a complete idiot I can roll with the blow - we'll just call it constructive criticism. I only play Civ 3 once a week (Saturday) and I have a thoroughly good time when I do. Nevertheless, improving on some of the tediousness (like having stackable movement) would be nice. I'll have to give it a shot.
Comment
-
Hmm, maybe I was a bit to judgemental to call you an idiot. If you started playing three months ago, the patch at the time was v1.17f. I could understand if that turned you off from patching by virtue of the posts here and at CivFanatics.
Thus, I hearby rescind my claim of idiocy if you go forth and patch hencforth.
Comment
-
One thing I really hate about the 1.21 patch is that you can't make changes to the civ3mod.bic file and have them affect current games!
Grrrrr!
They save the bic information in every save game file now. Why did they do that? It makes it almost impossible to test out changes!
Comment
Comment