Well, this guy is adding his actions ON the actual button and since I have a button that survives throughout the entire game session, I don't want to add a behavior on to it which only has a use in one of the 100 scenes. I want this behavior of the button to be specific for this scene. This is what I mean with "This FSM can not be placed on the object that is disappearing". I am saying here that I can not place any FSM on the actual button. So, my problem which is about finding a GameObject that starts as inactive still persists. I need to ether call the "ShowStory" and "Find Game Object" in a truly synchronous way or wait for my clickable button to be active and then
after it is certain that the button is active, use the "Find Game Object" in combination with the "U Gui Button On Click Event".
Another way to do it would be to actually be able to call a
non-static method and store it's returned value somewhere since I do have methods for finding this inactive GameObject but neither can I find an action which will call a
non-static method and store it's value.
PlayMaker is starting to make me think of JavaScript web development but without any control at all
Also, the link you posted is just one of those tutorials extremely hard to follow due to strong accent, mumbling and with such low image quality that it's just barely readable. That along with the fact that he's just rushing through it explaining basically nothing, as far as I know. I have watched it 3 times and I haven't learned anything.