RBP7 is still up, it's just Civstats that is down.
Just Sunrise and Team FFH left to play.
Just Sunrise and Team FFH left to play.
|
RBP7 IT and Tech Issues Thread
|
|
I logged in shortly after the turn rolled and one of our units had already been moved in a bizarre and harmful way. I wouldn't bring it up but this is a significant problem for us, and I would appreciate a reload if possible.
Anyone know of how this could have happened?
A Goto order (set intentionally or accidentally) executing? That or your partner logged in before you did and made some moves.
If it was actually something malicious (someone hacking the game for an obscure reason?), then I wouldn't have a problem with a reload. But I highly doubt that... it sounds more like a mistake or misunderstanding. And I don't think those warrant reloads. To put things in perspective, surely it can't be a bigger mistake than leaving your capital undefended with an enemy waiting to attack.  We didn't reload for that, and indeed we shouldn't have... if you screw up, you roll with it. So not to sound mean - and I have no idea of the circumstances in your case - but I'm not convinced a reload is appropriate.
You should just roll with it unless something out of the ordinary did happen, Seven. Otherwise everyone should get a freebie.
In Soviet Russia, Civilization Micros You!
"Right, as the world goes, is only in question between equals in power, while the strong do what they can and the weak suffer what they must." “I have never understood why it is "greed" to want to keep the money you have earned but not greed to want to take somebody else's money.”
March 5th, 2012, 23:35
(This post was last modified: March 6th, 2012, 00:14 by SevenSpirits.)
I guarantee it wasn't a mistake. (I've made quite a few misclicks already and I wouldn't dream of asking for a reload there.) I was the last on my team to login last turn and the first this turn. The only thing I did on last turn's login was check that the unit in question was still there and had no queued orders. After the turn rolled I connected, entered my password, hit enter, and when the screen came up my unit was selected and had been moved without any other keyboard or mouse input after hitting enter for the password.
I stared at it for a bit, but then I got a few failed attempts by other players to connect (which has happened in the past but doesn't usually) so I logged out and then logged back in. It pretty obviously wasn't someone hacking in as you can't make units move immediately at the start of the following turn anyway (right? ), and I was the first to log in this turn. But it's definitely not my error, which makes it difficult to roll with it.
I am aware that this game does not emphasize fairness, and while having a bug lose me almost a whole turn is not fair, maybe that's just part of the experience.
But please give me some credit. If it was a mistake I made I wouldn't be here asking if I could please get a reload, and it's annoying to be treated like it's my fault. LP, buggy behavior when opening MP saves (which is what happens when you log into a pitboss) is not uncommon. Not everything needs to be attributed to a person. ASM, I already posted in my original post that something out of the ordinary happened.
Sigh.
Sunrise, can I please get autosaves from Team FFH's last login before turn flipped and MackSeven's first login after turn flip? Seven, Mack, I need your password. Someone else, please pause the game for now. I'll see into this once I'm back from work and the saves reach me.
If you press any of the movement keys or left/right click the mouse while the save is loading (depending on which options you have selected), I think that can sometimes cause movement of the first selected unit immediately when the save loads. At least, I've seen it happen once or twice before.
Mist, you won't be able to get the save from MackSeven's first login after the flip, because it's only the most recent login that's kept (i.e. the second one). You could alternatively get the save at the turn flip, I suppose. Though all of this seems more trouble than it's worth... we only just started again and now we're halting once more. 
|
