What i did when i began blueprints learning is
1 : Choosing one thing to do.
But not blueprints ! this is like saying : ok today i learn materials. Of course you can have fastly basics and the illusion to be skilled. But each new situation will be an issue because you don’t look at it in the right angle. and sadly, fastly will come the moment were you’ll be too much disappointed and leave.
Choose one small thing to learn in thewhole blueprints possibilities : communication : how to do a switch /light
2 : Find the tutorial (in fact, you can set as 0 a list of tutorials video / forums examples or downloads and all the stuff gave by epic in which with a bit time you have most of all the things you will wonder (at least it is true for me)
3 : doing it. Not only looking, but doing. You didn’t understand ? Ok ! It is normal. Just try to learn and remember. As we did when we learned numbers before being able to calculate.
4 : If you really understood nothing. Do it a second time to remember more how things work.
5 : Choose another tutorial in your list and do it.
6 : come back to ever done tutorials (best way is to create a project : learn stuff and migrate in it all you need to learn from content examples blueprint examples and add stuff from other tutorial. It will grow but you’ll know where to find what you did and you’ll not pollute your main project with fails.
After 10 different tutorials, if you really did them with attention and remember what you did, the last ones will help you to understand the first ones. And the more you’ll learn new numbers and how they are basically use, the more you’ll understand how to use them in more situations, step by step.
Yes, this is boring, but if you don’t keep a time to learn arrays, you’ll never know what a powerfull they can be. If you don’t learn communications you’ll always wonder what is the best in your situation between cast or interface.
Learn all what you can even if you don’t understand and let the light come in by itself ^^