War weariness? What's that? ;D Seriously, WW means nothing to me now with Mausoleums. Plus there's the fact that we've had so few battles up until now that war weariness is basically back at zero for me anyway.
The fact that the city was on a hill wouldn't have made a difference. With the absurd technological lead I have over you, the units I throw at yours make yours look like matchsticks by comparison regardless of where they are. Nothing your fault in that, of course - just that it so happened in this game that we've proved just how unbalancing early contact on these kind of maps can potentially be. Something to keep in mind for all future games, I guess.
My sincere apologies Necrominious, however I did not actually realise that I had done anything wrong. Originally we had had a set turn order when I was actually attacking you, but then that sort of faded away after the initial invasions while I was waiting on some more advanced technologies and wasn't really doing anything except patrolling your shores. This turn I was finally ready to strike again, so wanted to get back to my nation playing first in the turn as we had originally done. I had no idea that you hadn't moved your Galleon on the previous turn, all that I knew was that I saw it on one of my patrols and naturally wanted to eliminate it.
Also, I would like to point out that in any event this was not a 'double move' as such, since I had not been sitting on the turn timer waiting to make my two moves at once. My previous move was played about half a day previously (in the early morning for me), and the last one was played in the late evening before I went to bed, since I wasn't sure if I'd have time in the next morning to play. There were no malicious intentions.
In any event, I agree that you might have had a chance of taking one of your minor size 2 island cities back, but is there really much of a difference made? Had you captured the city then I would have merely taken it back or razed it a turn or two later, and we'd be back in exactly the same situation as before. I don't really believe that this in any way affected the inevitable outcome of the war. If it had been one of my major cities that you were about to capture then I could understand the justification, but being just an insignificant size 2 island city I don't really understand.
What I also don't understand is why if it was so important to you, and you knew that you couldn't log in and would miss your turn, you still did not notify me in any way. If you had sent me a message letting me know of the situation (that you were blocked from logging in) and requesting me to let you move first because of something that was important, then I would of course have had no problems with obliging you.
Finally, I would be fairly strongly against the option of a reload at this point because I just initiated a rather major amphibious combat assault on one of Necrominious's cities this turn, and reloading would change the outcomes of those combat results. Units that had previously won their battles might now lose. Thus a reload would likely be heavily in Necrominious's favour, since the combat results from last turn happened to be favourable to me last time (winning about a half dozen medium-odds battles in a row). Reloading gives him a second chance to defeat my units which had already been victorious when they attacked previously, which I don't believe is fair. Just because my nation happens to be in the stronger position, doesn't give the right for another nation to get second chances in the combats between us.
An email should be sent out to all players when this happens. How are we suppose to know what's going on after we play our turn? I have missed a few turns due to all this, thoughout the game, but probably could have logged back in and played the turn if only I knew what happened.
I do absolutely agree with this though. We all do need to know when the game's down, it causes too many problems when it's down at inconvenient times and thus causes otherwise avoidable arguments. But we also all need to communicate more amongst ourselves too. (Case in point right here, of course. If Necrominious hadn't been blocked from logging in then he could have made his moves, then I could have made mine and we'd both be happy. Necrominious was blocked from logging in, but I did not know this and he did not let me know to do anything differently to usual. Thus I made my moves and got my combat results, and Necrominious missed out on his. If we reload though, that gives Necrominious a second chance on his previous defeats against my units, which I don't believe is fair.)
Last Edit: May 27, 2007 17:35:38 GMT -5 by emperor
Actually, checking Civstats he hasn't logged into the game in the past 11 days. Since the game's often waiting on just him to end the turn (case in point right now, 9 hours left on the clock and only him holding us up from turning over), I suggest booting him to AI as soon as possible, just as a courtesy to the rest of the players. He's of course welcome to reclaim his civ when/if he gets back here, but until then it's really not fair to keep his civ just sitting there while the rest of the world moves on. (Also, the computer will at least attempt to fight back against the multiple invaders, whereas right now he's just a sitting duck for those aggressive nations to target.)
Last Edit: May 15, 2007 22:44:37 GMT -5 by emperor
Great news. Looks like Civstats still needs to be put up though? (Perhaps you'll have to re-enter the game under the new IP, I think that's what we had to do with one of our other games when we changed IP's.)
Yes, for me it would be sufficient to reload from the start of the turn that we are currently on, with Necrominious allowing me to log in first before he logs in, to retain the turn order that we have had the previous few turns.
Yes, I must also request a reload. I took two of Necrominious's cities at the start of this turn last time around, but now thanks to the reload he has double moved me and I can no longer take those cities. I believe that a reload is in order, especially with Plattfuss having problems as well.