PROBLEM: Questnet treats players like objects while Quest assumes a player object but never actually creates one. This makes testing player properties a little awkward(without running a server and logging on with 1, 2, or 3 players). Why not model them similarly using the %userid% idea? A few forms of syntax might have to be changed to the ASL in general, like you would always have to define to what player messages are sent, but all ASL coding would then be compatible with Questnet with no changes(except for perhaps the necessary third person objective, which I'm still convinced can be done with some sort of room script).

NOTE: Player properties are SEVERELY funked up. Sometimes they read properly sometimes not. Even for single player games, there should have been player properties which would have made it possible to just give a player the property "OK TO PASS THE GATE" instead of having to give them a gate note or whatever. Perhaps this is why status variables were created, but in complex games, and especially multiplayer games, variables defined at the beginning of the game hardly allows for a large game unless you give every player a boolean for each door they need permission to enter and whatnot.

REQUEST: Whenever you have the time, work on that "questnet save state" feature. This will radically improve ASL's viability for online gaming. Not only in the small grouped type games, but even for massively multiplayer projects(well... not too massive).