I just wanted to point out something from the point of view of someone who writes tutorials for UE4.
I can understand that it is frustrating that the tutorials don’t work out of the box, but it really isn’t practical for a tutorial writer to keep things up to date quite so closely with a product that is fast changing like UE4. That said, I would like to point out that when I post a tutorial, I’m hoping what people take away from them isn’t just a “step by step” that they can follow and have it work, because if I were doing that I could just give out the end product and have the same effect. When I write a tutorial I’m trying to do my best to show the “why” as well as the “how” of it all. If you can understand the why, then the how becomes easier to figure out for yourself. In the cases you mention, there are likely alternative nodes or events you can use if you take the time to understand what the existing tutorial showed and then think through the logic of what it is trying to do.
I’m not trying to bash you or anything, I’m trying to get across that programming as a skill is as much about learning the patterns of problem solving as it is about specific knowledge of a particular programming language semantics. I’m an experienced C++ programmer, so when I go to do things with blueprint it is relatively simple for me because I simply type the name of what I assume the blueprint node would be for the thing I want. Most of the time that works, but if it doesn’t I then check the reference material and see if I can find an alternative name for the same thing.
I noticed a student of mine having the same problem recently. I’ve been constantly helping him in class to solve what are relatively trivial things in blueprint. What struck me was that he was seeing the same errors again and again, because he wasn’t learning the underlying pattern of his particular problem and therefore didn’t really understand the solutions I was showing him.
What I’m suggesting is that you treat any issues with specifics in tutorials as a learning experience. If there’s a node not showing up, try and think of ways to find out what the alternatives might be. First off, try and think of other names for the same functionality. Next you might look at the reference material online. Then you might come onto the forums and ask what the new way of calling the old changed node is.
I’ve seen several examples in the comments of my videos on youtube where someone has had a problem with a particular BP node due to a change in engine versions and posted a question about it. Then someone else who has had similar problems has posted a reply to them.
So instead of saying “unable to continue” you should be thinking “how best do I learn how to overcome this issue”. See what I mean? Use it as an opportunity to learn, rather than as a point where you give up. Trust me if you keep at it, you’ll be rewarded with a great feeling of accomplishment afterwards.
Just my small observation from recent life.