Sounds like you're trying to determine which player/users are currently running the scenario? Just to let you know the content in the beta is not meant for multiplayer interaction (but I hope is a possibility in the future). Its purpose/goal is to save/rank scores among users, and save data for individual use for a user.

With some crafty programming, it's possible to do multiplayer (At least it seems to be, and without even hammering the gallery to hard!). But yes, I am trying to determine which users are currently in the scenario. It's not a problem to set a string when they're running it, but when they stop it without executing the stopped() method, it's a problem. I don't believe the stopped method is run unless the stop button is hit, but that's a good idea.

Yes I gave some thought to it as well. But the problem is, the only communication you can use is by changing the states of the data members of a user but that takes too much time saving to be doing it constantly (doing it just once doesn't go without notice). I would imagine only a turn-based game/program would come out alright. And for determining which users are currently in the scenario I thought something like having a data integer to be periodically incremented, which can be observed as being active, but again, updating the data costs too much time.

Bourne has worked out the implications correctly, I think. Doing cross-user interaction with our design is difficult. That's not because we're mean, it's just that the current system is quite a nice, small design for doing high scores, and adding player interaction would add a whole load of other challenges. It's a possibility for future expansion, but pretty much for 2.2.0, the storage design that's in the beta is what will be in the final release (perhaps plus/minus a method or two). As for knowing who is online, we do actually have that information (more by coincidence than design), but I don't think we want to go to the trouble of exposing it. Again, we have our current design and who's-playing doesn't really add much to the design (since it's intended for long-term storage, not short-term interaction).