Could be a bug, could be design.
Description
When you attempt to morosascharge someone a few odd things happen.
1) If the person can charge set, they charge set you before you even charge at them and you appear to still be unable to enter a command until the number of rounds you were morosascharging for have passed.
2) If a creature has a carapace for deflection then it does the same thing as above and it is deflected in round 0 but you cannot enter another command for however many rounds you would have charged for.
3) A similar thing happens with evasion. If you morsascharge for 3 rounds and the person evades it at the very start you are unable to enter a command until the 3 rounds of what would be your charging the polearm are over. Log below for this one.
Carrion Fields on 2013-09-01 21:17 UTC
Automatically imported from the legacy bug board forum.
Vilhazarog on 2013-09-13 17:45 UTC
Subject: Design
Typically for these kind of skills you still did the charge/bash whatever, it was just blocked, evaded, etc and you still have to pay the lag penalty.
Tac on 2013-09-16 23:38 UTC
Subject: By bad (lazy) design maybe
That makes sense for a bash or whatever, but for something like morosa charge or perhaps timed attack, where you are charging up the attempt in advance it makes little sense for them to be able to evade (or whatever) before you've actually made an attempt to strike.
Vilhazarog on 2013-09-19 06:30 UTC
Subject: RE: By bad (lazy) design maybe
The nature of the ability requires you to make the attack regardless of whether it would actually hit your opponent or not. From a game mechanic point of view it makes little difference where the echo is placed, but from a purely aesthetic view, yes, it would be nicer if the echo was placed closer to the part where the AP actually makes the charge, but its hardly worth the effort to make a set of exceptions for evade and then put a special evade check in morosa charge.
Tac on 2013-09-20 00:13 UTC
Subject: I accept your laziness
I wouldn't change it either (based on laziness) but it would look better if it came at the charge part. The lag doesn't change but it makes more sense in the setting and doesn't feel as jarring.
Marcus_ on 2013-09-23 14:46 UTC
Subject: RE: By bad (lazy) design maybe
It's actually quite important from a game mechanical/tactical POV. Since the victim gets warned much earlier that a failed charge is coming, he knows that the AP won't do anything for quite a while and can use that information to his advantage.
If the fail came when the charge happened, in the same scenario the victim's "safety period" would be much shorter.
Vilhazarog on 2013-09-24 21:31 UTC
Subject: RE: By bad (lazy) design maybe
Ok, this is a fair comment, I just noticed that someone commented out the TO_ROOM acts on this ability so it's not telegraphed on success like I thought it was.