Well, it turns out that I did have a variable that it could read so I was starting to work with that with my original plan and doing away with the event dispatchers since they didn’t seem to be what I needed. I’ve included the screen shot of the variable being set by the trigger (finish line) which would then pull up the main menu ui. The second screenshot shows where the variable is being received. Strangely, even if this variable is set by the trigger, the ui doesn’t get the message some how and the colour doesn’t change, however, if I set the default variable to true, it changes the colour. This is where I’m thinking something isn’t being passed between the two. (I didn’t set a false to the branch because if the check is failed, then nothing changes with the widget and it just constructs as usual, but I don’t think that’s the issue)
I also tested using custom events, which was how I originally made the trigger. It would run a custom event and in the widget, that event would set the variable and it would get called with the same branch. Still wouldn’t change the colour until I changed the default value. Am I missing something here or is there some kind of information not being passed through the two?
Here is the variable being set by the trigger.
And this is the variable being retrieved by the widget. By the way, “SmiteLevel” is the name of the text instead of “BaseLevel”. Haven’t cleaned that up just yet.
I also used make slate colour since that was the only node that would come up and was compatable. For some reason, it was saying that “only exactly matching structures are considered compatable” so I was forced to use slate colour. So far, that isn’t an issue, and it’s more the boolean value not being set or read.