There were a number of things that I wasn’t aware of, such as the fact that the name you give your android release has to match whatever name you chose for you unreal project exactly. Initially I was attempting to launch the game directly to my device and there were some obscure errors so I opted to do what you suggested and just package it and manually install the apk and obb file. I’ve finished the actual blueprint for dashing and combat text, I just have to prepare them for public use ( arrange them, comment them etc.). But with more flexibility comes more complexity and it becomes less intuitive. I found myself frustrated with construct 2 because there were some things I couldn’t do, but with unreal blueprints that is mostly gone. I used construct 2 and stencyl as well and I agree they are more intuitive, but they are also more limited. I finished recording the videos on saturday night so I was a bit tired by then. It sounds like you have a lot more ideas to add to it. I’m looking forward to seeing how you progress. For some reason I find Epic’s version of visual programing very unintuitive compared to others (like Construct 2 and Stencyl admittedly those are 2D engines compared to UE4) so having your excellent platforming kit to refer to is proving very helpful. Even though I am using parts of your kit differently, it is really helping with my thought processes regarding how everything works together, especially the blueprints.

Thanks for the tutorials Axell (one of them you sounded really tired.

Stencyl enemy ai