I’m trying to do a simple access of a public variable in a child object. These are the amount of different ways I’ve tried so far:
I mean, the Epic answer seems to be “the engine wasn’t designed in that way, just work around it”, but this is meant more as “I’m new and this feels like the logical way of doing things, why wasn’t it designed to be this simple?”
I mean, more people than me are confused by this, because for example, here’s the first Google result on this topic:
Hopefully there’s an equally easy way other than the three examples posted here to accomplish this but also, it would be great if these three examples actually worked, instead.
Right now, it seems that the Blueprints follow exactly the same archaic syntax rules as programming languages, and are not at all easier, because it just makes it more difficult to search for the answers, since the answers are graphical nodes instead of text you can copy and paste. And it seems you need to know exactly what to search for in the blueprint editor and type it in in order to make it work, which again I don’t really see much of a difference between scripting (that white connecting line is perhaps easier to spot than a missing comma, but still). A toolbar with common functions that you could drag and drop, like the modes bar in the main editor, would have gone a long way to mitigate this.
As of writing this, I still don’t know the answer! First impressions from me are a big thumbs down, unfortunately.