[BUG 80.0] City stolen, I stole it back, game broken

from Elemental Forums

Not sure if it's already been reported before, or if this is the appropriate forum to post this for a noob such as myself.

 

Basically Kraxis used his city steal spell, I conquered it back and it won't let me end turn.

 

I've reloaded and tried waiting a few turns, instantly going back for it, waiting about 10 turns to no avail. Anyways, love the game keep up the great work and just thought I'd post this.

3,007 views 6 replies
Reply #1 from Elemental Forums Top

Have you tried razing the city to see if you can continue after?

Reply #2 from Elemental Forums Top

Silly me.... I loaded the save that I made after the bug happened and I can progress turns just fine now. After for attempting to Raze, I didn't try that and now that I loaded the previous saves before this happened he refuses to spell steal my city. :(

Multiplicity - Control multiple PCs using one keyboard and mouse
Reply #3 from Elemental Forums Top

I've often thought that Kraxis is a big uncooperative jerk.

 

I've also found that with some oddities that exiting the game and reloading can fix things. I hadn't thought of that in this case, but glad you worked it out. Still, a bug and should be fixed if possible.

Reply #4 from Elemental Forums Top
Yes, exiting, closing steam, and restarting the game often 'fixes' many oddities, bugs, etc. One bug that has hit me in several games is that I cannot move any units on the big map. Ending my turn does not free the units in the next turn. But saving, closing the game, and restarting, all is happy.
Reply #5 from Elemental Forums Top

A lot of bugs are hard to reproduce because the game doesn't use a consistent random seed.  They really should, though, at least for the beta.  While I do think the regular game would benefit, it would also make reproducing bugs a LOT easier.

Reply #6 from Elemental Forums Top


I still very often find myself able to move units around but can't end the turn, restarting always fixes this one too. I had thought this problem was fixed in an earlier version.