I started out with creating a project in a game genre that I was passionate about playing myself. I started by looking up tutorials step by step, finishing the tutorial so it works, then examining the blueprints. Then moving on to the next part of my game, finding a tutorial on it, examining the code, then linking the 2 tutorials together with the knowledge that I acquired.
i.e. I started by looking for a tutorial “Ue4 basic AI” so i found tutorials on making enemies follow me around, with line of sight etc.
then I looked for a tutorial “UE4 health and damage” and made it so the player character has health. And I now understood a basic way of how to deal/take damage. I also gave the enemies some health this way by looking at the code how I did it and then coming up with my own solution for enemy’s health.
then I looked for a tutorial “UE4 melee attacking”. So I implemented basic attacks, which substracted health from the enemy.
then I looked for a tutorial “UE4 AI attacking”. So i made the monsters attack me
then “UE4 UMG HUD basics” to make a interface for health bars
then “UE4 death and respawn tutorial”
then “ue4 experience and leveling system tutorial”
etc etc…
After a time doing this you will understand blueprints better and better and after 2-3 months doing these basic tutorials you can understand blueprints so good that you can create your own stuff.
So my advice is to just start a project your passionate about and take it step by step, looking up the tutorials you need for the next step in your project. No need to find documentation or step by step explanations of blueprints, just start a project and look up the tutorials you need.
I’m 1 year later now since I started learning blueprints this way, and I’ve got a very solid project going by now.
check the action RPG toolkit and the Emberheart game threads in my signature 