So did you get a screenshot of your orders, as discussed previously?

Do you play with multiple browsers/windows open? I know that has fooled me before.

No and no.

There should be a disclaimer somewhere stating that "when orders are messed up, look at the mirror" :)

It's human error, happens to everyone.

Just happened to me, would have sworn I entered the order correctly, but apparently only thought I did, and didn't.... Fortunately for me, it's not game changing (it would have been a very useful move though...). Oh well. It should happen once to everyone so they're extra careful from then on, haha. Note to self: When you come up with a hilariously brilliant move, actually put in the order for it.

Sorry to state the obvious but did you click update after entering the move. If you click finalize first then I don't think works. Same if you enter the order but then navigate away from the screen.
This is also easy to do if you have quite a few orders to enter.
I stuffed up my moves last night. I swore I ordered a fleet to the Irish Sea from MAO and it went to Nwg. But even though I don't remember making this move I can see how I could make such a mistake. Mistake are inevitable, even if rarely.

I mean MAO to NAO.

Sorry, Ninj, but if you don't have proof, and with Kestas adamant that such a bug is impossible, the conclusion is likely to be that it was probably your mistake.

To clarify, if you have gotten to the screen where you have both a Finalize and Update button, you're moves will execute at the end of the phase, regardless of if you hit finalize. However, if you much around with the drop down boxes and don't hit update again, you will NOT get your updated moves.

I think these threads are silly. Take the screen shot of your finalized orders and then see how often those are messed up.

It's not hard to double check your orders people...

NPRZ - nothing against you personally here - I just think that it's always human error. I've had mistakes plenty of times, but they are ALWAYS my fault...

I didn't post this for discussion or sympathy, but only to bring it to k's attention.

I had three moves to make in order to win. This was the most important one, so it was the first one I entered. There were two other convoy moves, plus one support order. That means I saw that same order sitting there through something like 8 or 9 form-submit sequences.

There is no question the move was in, it was the first move I entered.

And one little click on a drop down box can inadvertently change things.

@NPRZ: "I didn't post this for discussion or sympathy, but only to bring it to k's attention."

Yes, but Kestas has already said he does not believe that this kind of system error is possible, unless someone can prove otherwise. So he's unlikely to respond positively to yet another post about this kind of "bug" unless you offer some evidence.

I do sympathise, but I'm just saying that this thread is unlikely to achieve anything as it's just repeating things that have been said several times before.

NPRZ: Unless you have a screen shot, or can show how it could go wrong in the code, there is no option but to accept that it is human error.

"Since this was a game-ending move, and a mini-backstab against a fairly powerful ally, there is no doubt I entered and finalized the order correctly" is a massive non-sequitur. "The safety of the space shuttle is absolutely vital, being a matter of life or death. Therefore it is impossible that the Challenger suffered a design flaw that caused its accident." is pretty much analogous.

As Kestas has said, if this was a bug, it is incredible that it hasn't caused an illegal move or a game crash or similar.

Folks, I've been writing code for 30 years. I've seen much weirder stuff than this. In any case, it's reported if anybody cares, and I'm done.

Yes, but in the previous post about this issue, Kestas explained, in programmer-speak, why this bug could not be happening in the way desribed - unless by human error.

So the only proof which can be used in this case is the screenshot of FINALIZED moves? Shot of screen with both "Update" and "Finalize" buttons wouldn't be such a proof, I guess?

should get some interesting responses to this one. lets just throw this out there, is it possible someone is hacking accounts to be an ass or something?

if this is a problem that's probably caused by disfunctionality of drop down menus then why don't we change the menus?

That's not the drop down menus are coded. The drop downs don't send info back to the server until you hit update. While you CAN code the drop downs to go back to the server every time they are touched, when you have 17 armies, it gets to be a hassle.

The problem happened more than once to you ninja? and it is not that frequent in other users...
There must be something wrong; or you don't pay attention and make the same mistakes frequently or someone is messing with your acc, as your password or something...

If it was a random error it would happen more frequently... and the more times you play more probability there would be to get an error... so, I don't see exprienced players of this site complaining...

@NPRZ - I'm with ya man. I've been programming longer than Kestas has been alive. He may swear it is impossible, but I know better. NOTHING is impossible when it comes to software bugs.

There is no such thing as a bug. There is poor programming. I'm surprised any programmer will use the word 'bug'.

(I am a computer programmer)

@Draugnar - there are some pretty nasty ans subtle bugs that can do weird things. But kestas has done his due diligence and writes the information about moves twice - once to the database and once to a log. If it was database corruption, or not checking return codes, then I can see stuff like this happening, and being maddeningly difficult to find. But in every case so far, the database has agreed with the text log. The system received the order as it was executed. Note that I did NOT say that you entered the orders as they were executed.

I don't think it's a bug in the database. Maybe we should be looking carefully at the hairy javascript that handles the menus?

@Dingle, to a degree, you are correct. sometimes, however, it is n't the programming that is poor but the specifications and guidance from above. Team efforts required detailed specs for interfacing, but when one team is told to add an option and another team doesn't know jack about it, you get problems within the system.

also, the environment in which you develop can make a difference. I once did a project in turbo Pascal (long time ago) where the TP4 key handler kept dropping keystrokes. I finally hand wrote and assembled a key handler and put it in as inline code because there was an issue with the runtime. In my program, it was a bug. My code was perfect, but the runtime libraries were farked. However, it was still my problem to fix.

Dingleberry, I fail to see the distinction. Your statement reminds me of when I was referred to a neurologist about a pinched nerve. After a bunch of tests, he informed me that I was suffering from "neuralgia myeloparestheisa" which sounded very grim, and probably expensive. I asked what it was. It's Latin for "pinched nerve."

In any case, I've decided to start taking screen shots, as I've seen this often enough and it's either that or go look for another Dip implementation, and I rather like this one.

I don't know anything about programming, but why don't I see such mistakes happening? I have played over 100 games here & as said before, when mistakes happened, they were my mistakes (scrolling too much with my mouse when selecting destinations etc.).

What I want to say, is that if these kind of mistakes exist, then there should be some pattern (of how often and where those mistakes occur). As long as this game doesn't have artificial intelligence to harass some players, then these mistakes should take place much often & to anyone. So, I'm not the man to evaluate the programming work, but I do say that it's unlikely that it's a programming mistake.

@Dingleberry-Jones - "There is no such thing as a bug. There is poor programming. I'm surprised any programmer will use the word 'bug'."

That's a little arrogant, even for a programmer. Granted, there is poor programming in the world, there is also poor testing and poor design and poorly designed tests and there are even poor requirements, which influence everything that follows from them. B ut it isn't always down to the programmer.

There is also the unexpected; and before you reach for you keyboard to tell me you have to think of the unexpected and program around it, read on: Who'd have thought software written for a PC 11 years ago would now have to run (and fail) on a multi-core processor? It fails because the thread priorities used to schedule the program's different threads are no longer be enough to keep the different threads (with their shared variables) from running simultaneously. It falls over its own feet. That wasn't bad programming, it wasn't bad design, it wasn't even bad testing. You can't call anyones work for the original team "poor" because the software that's worked fine for 11 years doesn't work now on a shiny new multi-core PC. Even if the team had thought that somewhere in the future, somebody might come up with a multi-core processor and they'd programmed around it, they couldn't have tested/proven their multi-core code because there were no multi-cores to test it on (and the project manager would have thrown a fit if they'd wasted time writing code they couldn't test to fix bugs they couldn't even reproduce). But its still a bug.