http://www.wargear.net/games/log/415458
The game started, was somehow declined, every originally placed unit neutralized, and the whole map re-rolled. Not to mention, much to my opponent's benefit.
How does this happen? Can I get this annulled somehow?
Happens all the time. The final set-up is the game you get though.
That's crazy. That happens all the time? What triggers it?
I wasn't aware that it "happened all the time" but I know a somewhat frequent corrupter of the history is when a game initializes twice. Wasn't sure what that meant until now (I think) -
asm wrote:That's crazy. That happens all the time? What triggers it?
Most of the time players aren't even aware it happened until they watch the history at the end of the game and realize it's all screwed up. Since the game launches properly with the reloaded board, it's not really a problem, though, sometimes if you need to view the history in-game, it can be a bit annoying because it usually causes other history errors as well like excess/incorrect troop counts.
Oh, THAT'S where that comes from? Wow, it DOES happen all the time then.
so maybe I didn't restart that Invention dev game twice! - maybe it was this bug?
Ozyman wrote:so maybe I didn't restart that Invention dev game twice! - maybe it was this bug?
No, because I saw the board set up and displayed in the player. The bug is a history/log thing and happens before the game is set, as far as I am aware. From my experience, I still think that that was human error... or just zealousness to get that game restarted!
asm wrote:Oh, THAT'S where that comes from? Wow, it DOES happen all the time then.
I wasn't aware that it "happened all the time"...
Maybe when I said "all the time", I was overstating it a bit? It didn't use to be as frequent, so I guess now that I see a board repopulate or another history related bug in about 1 in 20 games, it feels frequent compared to its previous near non-existence. Since it doesn't affect game play I don't know how much of a priority it should be though?
Hmm it does seem to be happening more frequently recently, I'm not sure why. I'm looking into it.
I've added a patch to fix this bug. Let me know if you see it again!