Really weird behavior related to inputs. Bug or miss understanding?

Hi, guys. I'm here to share the experience I had recently trying to implement a dynamic input support for keyboard and gamepad. It's probably a stupidity of mine but I need to understand what happened here so I can learn and move on.

I basically did all the input events in a different event sheet and then I just exposed all the booleans. I'm not doing anything related to inputs outside this event sheet, this is to ensure that I could easily implement all the different inputs from a keyboard and a gamepad without redoing anything, specially outside the input event sheet. So now It's prepared to create, in the options menu, the key assignments by the player.

I said all that to make you see that It's not something that I'm doing wrong in the character's movement mechanics events. If I use my xbox controller, everything works fine and always did since I started to work from the ground up supporting gamepad and not keyboard. Now that I've implemented the keyboard, and again, nothing changed anywhere because I just expose all the booleans to all routines in the game, a specific movement stopped working.

Now that you are aware of it, here is the weird behavior:

This gif shows the weird behavior of the wall jump

and uses this code

This gif shows the wall jump working normally

and uses this code

or this one

Could you edit your post to make it more clear which gif corresponds to which code? Do I understand correctly that "Keyboard Is key code down+Trigger once" works fine, but "Keyboard On key code pressed" glitches?

I would start by checking if these two events are triggered in the same tick. Enable both events and add Browser Log "On key pressed" & tickCount and Browser Log "Is key down" & tickCount. Run the game and check browser console.

Also, because On Key pressed is a trigger, it may be executed at the beginning of the tick, before some other events in your game essential for wall climbing.