Regarding readme item 2.2.c - Units will complete an attack b4 move

[igmo]

from my experience the gameplay change listed as "2.2.C" in your readme is way too biased to a unit completing an action before taking a new order.

in my play, a ghol sent to pick up pus refused a command to move elsewhere (he was very close to the pus, but i was rather surprised he refused.) in another instance a ghol running up to throw a ground attack (but at least 1 sec from a throw stance) refused an order to attack a specific unit (damn dorf lived too!)

what you are setting up with "2.2.C" is units thinking for themselves, which is bad bad bad. if i'm dumb enough to stop an attack in progress, thats my fault. i may just have a good reason to do so, though, and dont need some dumb monky-dog creature making that decision.

[iron]

no Igmo, you've read that wrong. On occasion in Myth 2, if a unit was in the act of swing its sword, kicking or whatever and you told it to move somewhere, it could ignore you and keep attacking.

2.2.c is a fix for that. It addresses a minor but annoying issue and does not have the effects that you're assuming. It doesn't give units any means of choosing for themselves but provides better responsiveness to player commands.

I'm not saying what you say happened in-game didn't occur, but if it did I'd like to see films of it before jumping to conclusions.

[igmo]

yup, i did missread it... sorry.

what i said happened did happen, and so i read that item to match my experience. asside from the fact that i have not lied (even socially) in 10+ years i cannot prove what i posted

even if i had film, i'd have to tell you that i clicked at ground then dorf (or pus then moved) - not sure how you'd be able to track when i clicked what. is there a keystroke log synched to game time?

so, either the attack continued, or my click was lost. i don't normally notice click losses, so i assume the former.

[iron]

yes its possible to tell - the film records player commands as & when they happen, so I'd be able to tell exactly what the ghol or whatever did in response to what you told it to do, and thus tell you whether or not there's a bug and why.

All you'd need to do is tell me when in the film it happens and where to look

Btw please don't think I'll sell you short on this or deny there's a problem just for the sake of it. I've spent many many hours recently analyzing films, and am happy to keep doing so if it will either identify a problem with the beta that we can fix or set your mind at rest about it. I can also (using magick tools available to developers) make Myth switch to 1.3 gameplay, as it if were a 1.3 film, immediately at the moment when the problem occurs so I can see very clearly if the behaviour is different.



Edited By iron on 1082691891