Perhaps if everyone print screens before their moves...

so i guess that there is no evidence of my moves being entered then?

The moves entered are recorded, but they're displayed via the map. So if the map doesn't correlate with the moves someone say they've entered then they're saying that their moves were changed from the time they were entered to the time they were processed

I've had a few 'mysterious mismovements' before. Like Berlin attacking Munich when I'm certain I inputted Silesia. I'll start taking screenshots like Ghosty proposed.

Not to put too fine a point on it, but that's silly. Place yourself in a situation where you have a 50/50 shot at a center. You finalize one set of moves and take a screenshot. The un-finalize and try the other set. now if you guessed wrong you can blame it on the system and produce your screenshot as proof.

It's ludicrous. How could that be fair?

At issue here is most likely an error in entering orders. Just as in the table-top version of the game, a miss-written order has to stand. Its in the rules.

I was referring to the possibility that sometimes the orders that are finalized are miss processed by some bug.

I understand that. But the potential for abuse is too high. If there is a bug, it can be tracked down and fixed. Given that the situation is not common, a bug seems unlikely.

Here's another suggestion. Change your password, and make it strong. It is a possibility that your account was accessed by another player and your orders deliberately changed.

somebody must have cracked the database and he now has access to all the players' passwords. he's changing orders and making fun of us as we speak

That bastard :P

i *think* that i had that happen to me once. I had ordered port -> spain and mers to support, but the support wasn't entered, and mers wasn't attacked. I may have mistyped, but i'm not sure.

this could very well be the system attempting to add random elements to the game, such as mutiny. Maybe the army didn't want to follow the orders.

clearly I screwed up somehow...I must have forgotten to update...thanks for looking anyhow K, sorry to waste time
Oh well....next!

I've experienced the same problem before. I put it down to human error on my part but if other players have had the same problem I guess it's something else.

You don't have a monopoly on human error. With something like this, nine times out of ten, it's human error.

So what is it the other 1 out of 10?

Ok, you got me. the other 1 out of 10 is a programming error, which is also a human error.

Except 1 out of 32715892340579 the server is sentient, and is laughing at us.

this has never happened to me. anyone else who has been lucky?

The bug could be subtle. Perhaps the database does not set/release a record lock in a timely manner and the conflict results in an order not being processed completely. As Kestas says, the map displays the stored moves. If you had keyed one set of moves and keyed a second set, it is remotely possible that the second set were not written to the data storage. This is not a usual 'bug'. By that I mean that the code is correct as far as processing goes, but it may not be able to handle situations where lag times/disconnects may be a factor.

I've looked at the open source, and though I am not a php guy it does look like it is robust enough to handle these situations. That's where my intuition puts the problem at either the end-user, or a malicious third party monkeying with the moves.

And yes, something like this has happened to me. But I can safely blame it on the very small screen of the Blackberry I borrowed and my fat fingers.

> The bug could be subtle. Perhaps the database does not
> set/release a record lock in a timely manner and the conflict results
> in an order not being processed completely
Unfortunately the problem is some people claim that their orders were changed, not just left unprocessed :-( This really is hard to explain with a bug

Someone having access to the database is actually something I had considered, and it isn't totally unreasonable. I'll upload the bugfix&extra-comments version tomorrow and change some database passwords while I'm doing it, just in case.

Well, this hasn't happened to me yet. I'm pretty sure it's simply human error, which happens a lot more than people think. I've made my share of mistakes.

Happened to me - but I have another explanation - my mouse has a wheel(?) instead of a 3rd button. And I use it for up-down navigation along the page (scrolling).
However, in some cases I had the 'order menu dropdown' selected with teh mouse - so instead of scrolling I was changing my order. The worst part of it is that the 'scrolling' kicks in within a second (if you move your mouse slightly, or when the dropdown menu selection runs out of options :). So, if you don't see this (get distracted, don't double-check your orders before finilizing, etc.) you are submitting the wrong orders.
Not that I'm an expert - but I would assume if an error occurs less than 0.1% of the time (?) - the reason to be human - and not software :)

On a second note - there was an idea somewhere to be able to 'log' and even 'execute' unfinilized moves. May I say that this is a really bad idea. I have players who, as a rule, wait until the last moment (and I believe statistics will prove they do it with intent). This should not be encouraged.

In fact, if it is possible, I would kindly suggest that the 'deadline' is not a fixed time, but a range (period) - let's say anywhere between 24 and 26 hours (to retain the 24-hour minimum). This way there will be noone waiting until the very last moment - to see if accidentially someone else will miss their move :)