well this is really silly , I clicked on the screen and now it works, the cube moves. I guess you have to click on the play screen to make any blueprint work?
1 Like
Yes, the window does not have focus automatically. If you ever want to fiddle with how this behaviour works in the final product:
Ok I’ll try this again from scratch and see if it works. I didn’t try to print the pawn but don’t worry I will do it if I find the same problem again. Thank you for your time though. I’ve been trying all morning to get this to work
1 Like
You should absolutely watch me try to move a cube in Unity. 
1 Like
Sorry I have one more question. Since the event tick only has one connection, how do you connect the rest of the keys?
Ideally, you would not use WASD like this at all. I mean you could but the system is being phased out of the engine. At this point, it is considered deprecated legacy. At the very absolute minimum, consider creating axis mappings for movement:
These execute every frame.
Ideally you would hook it all up to the Enhanced Input. But it’s a bit involved.
I mean, you could mess around with stuff while the blueprint police is asleep:
And you can always split an execution wire like so:
Ok I have too many questions and I feel that I shouldn’t make this thread too long with multiple questions.
If the current input system is going to be deprecated I think it is a better idea to learn the enhanced system already, so I think I am going to watch some videos about it.
I don’t want to take up all your time since you’ve been really helpful.