Not Real - Convert Stateful Events Review

@eric79 Hey Eric - I've got broader changes in another branch but I wanted to validate the methodology I'm using for switching over these stateful events. It feels like I'm doing something wrong below/I'm breaking more than it should. I guess I'm also a bit unclear about how VWF replicates the chain of property settings... should we expect the 'history' of "setProperty" to get called on all properties on initialization or are the properties just set without a check when a new user joins? I'd imagine that the proper way to check/set for state would be to use getProperty and then setup the view appropriately depending on the current scenario/other things. Is this correct?
This is going to be a problem when my changes go in, because I've switched to relying on this event to control the flow of the scenarios (instead of having the scene call into the scenario).

In general, I'd like to remove all dependencies of the scene on the scenario.  The scene shouldn't have to know anything about how scenarios work.  It's reasonable for it to store the scenario - though ultimately it would be better to move that into a scenario manager of some sort (especially once it becomes more complex).