No worries and I’m glad it’s working! Pretty sure I’ve forgotten to do that before too. I’ll check to see if I can auto create and wire a parent tick node on new state machine creation.
Local variables per state is currently in development and may do what you want. If your data is constant it could be set as a default value. But if it’s constant already, can you just include it in the blueprint node you use to send text to the UI (or another text creation node) rather than redefine it as a variable? Or include it in a data table somewhere and reference that? The individual states weren’t really designed for data storage. Blueprint member variables work of course but are state machine wide.
Another option would be to create a separate state machine for each state and create blueprint variables for the sentence, and reference each state machine in master state machines (basically treat multiple state machines as single states), but that’s probably far less convenient.
If there are other use cases you can share regarding this I can see if they can be met or added with local variable development.