well that is because i guess u made the events on release button or once pressed on one of them, is a basic mismatch that most people dont see as how things work in c2... C2 takes every line of code as you lay it down in the event sheet. so if u tell it play animation left for example when A is down its going to do so... as for playing an animation when was pressed... thats a totally different logic... and has a different meaning if u try to understand it a bit more then a quick glance... try swapping from pressed.... to IS PRESSED or IS DOWN that will fix it however... the last key u press is going to be the last that will be triggered so if u press AD and the delay between them is by 000000000. pico something the very next one pressed down will be the one animating ur character.
for better ease of understanding...
Was pressed condition triggers one time if the button was sometime pressed and the events or actions are not in play - sometimes they might even overwrite each other but wont be a big glitch or something visible
IS PRESSED condition triggers if u keep pressed the button down ... once u released it it stops... this is what i suggest u to use to avoid any other future coding problems in C2 same logic can be applied to on mouse button or touch... they all have same conditions
on release condition well obviously ... when the button was pressed and is released the animation or events will trigger one time unless its a looping animation
thats how far i can remember for the keyboard customization's and as being relative correct to ur problem.
dont beat yourself to fast... its usually a pretty easy solution 99% of the time , and also 99% of the C2 coding problems are made by programmers or because we get hyped by the easy system of getting things done fast and so smooth with it that we dont double check it.. or we dont try understand it a bit further, since its a no programming required software we expect things to happen by themselves which most of time do... but we need to understand how to make those things make sense to the machine we are communicating with... i get it .. been there done that..
hope it helped you out.... also try reading the manual its pretty easy to understand and a complex lecture also covers a lot more then keyboard using... will really help you out on some cool stuff that will ease ur work in future.. if u got time for it.
extra tip if u dont have different conditions that has to happen on the same key... dont use nothing else but IS PRESSED DOWN same for mouse/touch relative to movement other conditions relative to pressing are a dud and will only confuse u (for clicking u can easy use TAP touch object applies to browsers and mobiles directly i never used mouse rarely when i really need some extra thing from ti that touch doesn't had it before... but now there is no need for mouse object anymore)
C2 basic friends conditions that i prefer and recommend because they never let me down - touched - on TAP /for objects clicking simulations /is in touch - is down - for dragging motions or movements with keyboard or any other thing... i strongly dont suggest using on release... 80% of the time will not trigger and if it does will trigger wrong cause u might release and click again to soon
there is one maybe exception for the -release- condition one where u dont use it for fast interaction cause - on release- condition will have a tactile delay triggered by human response which means the delay between touching and releasing the button... most people want stuff to happen when they click it not when they release... it makes perfect logic.. we dont want to wait... we need that speed lol ......... monkey brain i guess not developed.
remember.. is pressed down.. usually is used for moving objects... for playing animation to work with it u have to get more specifics in sub events if needed