HotTK Multiplayer

Agent327

Observer
Joined
Oct 28, 2006
Messages
16,102
Location
In orbit
Last weekend Zippadoodeedah and me tried a MP session on IP connection with the 68x64 map. We had some fun, but after 30+ turns we called it quits as an OOS error occurred.
 
well if anyone wants to try some MP games, I'm down. Send me a PM or something, or we could organize a game here in this thread.
 
I have to say for now it's not multiplayer compatible. I tried, and thought it would, but didn't test it.

If anyone has prior experience of working with OOS errors, I'm all ears.
 
stmartin,

This may not have anything to do with your mod at all. If I remember correctly, a lot of people had many Multiplayer OOS errors while upgrading to some of the latest versions of BTS. (Starting about just over one year ago.) The short story was that somehow BTS wasn't overwriting some files properly while upgrading, and it was using the wrong random number seed causing one person to get a barbarian uprising random event while everybody else didn't (just one example.)

JEELEN,

I think you can clear the files necessary by holding down the Ctrl button while loading up Civ. Please have everybody trying to play the multiplayer game try that. If that doesn't help, let me know and I'll see if I can't hunt down some old threads talking about the file locations and help narrow it down to if it is a Civ bug or a HotTK bug.
 
stmartin,

This may not have anything to do with your mod at all.

Quite true. A number of mods get OOS errors, it's not HoTK-specific.

JEELEN,

I think you can clear the files necessary by holding down the Ctrl button while loading up Civ. Please have everybody trying to play the multiplayer game try that. If that doesn't help, let me know and I'll see if I can't hunt down some old threads talking about the file locations and help narrow it down to if it is a Civ bug or a HotTK bug.

I didn't know that, thx! (Will try it next time.);)
 
well there is the notorious amphibious assault oos for 3.17, but someone already did make a fix. From what I've heard, this bug causes more oos than anything else.

here's the thread
 
Back
Top Bottom