when you put await joypad on an actor with any of the directions you still require the a button to be pressed to make the code run
i expected that the script would run when the player collided with the actor with the dpad inputs, i image this has to do with how the player moves? i dont think its designed to work this way, but this could be helpful in rpg games that have actors like cacti that deal damage to the player or spiky roaming actors, without the need for crazy background code
running
Windows
version 1.1 release
I feel like this is the same as Issue #167. (Or, at least, could be solved by it.)
Actor scripts only fire when interacted with, not a bug, but a feature request
Pause script until only <>^v are selected, still requires a pressed first even if a isn't selected as an option, doesn't seem intended to me that is why I put it as a bug
So on the actor you have to press a then <>^v to run the script does that mean that assigning b also won't work on an actor?
Most helpful comment
Actor scripts only fire when interacted with, not a bug, but a feature request