1  |   Order by index

Mar 31, 2003, 8:05pm

I wish there was a way to mark an object as having a persistant state or to save values to variables, so that you would be able to have a door that's been opened stay open even if it gets out of visibility range. I would preffer to have the default behavior like it is now, but the addition of a "persist" command that would cause the object to act as if it had never left visibility range, and a "reset" or "reload" (or recreate?) command that could be used when you want to reset the object as if it were non-persistant and had gotten out of range and back, would be very useful.

For example, I was just playing my Fireflies game in NewAW, and got up to a score of 111101101101 so far, and when I stopped to look in the beta newsgroup I found that to check on something reported there I'll have to change worlds... which means my score will be reset to 0 when I return. Now, I know this can be done with bots, but I like built-in features... so I'm posting this one to the wishlist. :)

TechnoZeus

Mar 31, 2003, 8:14pm

What if each object was:

Create name OBJX

(i.e. all in the world) and somebody put: create persist name=objx


LOL

[View Quote]

Mar 31, 2003, 9:04pm

Then I guess a lot would have to be remembered by the browser if you left that world. This is no more of a potential problem than the risk of someone doing the same thing with almost any other command, although in combination with other commands it could get to add up quite a bit.

By the way, I only meant persistant within a single session. Closing and restarting Active Worlds would release all persistant values. Also, I hadn't really meant for the command to me able to be issued with a name= parameter, both because of that potential complication and also the fact that having to put the command on the object itself could give the Active Worlds browser a heads up on which objects might be made persistant, so that it could make preperations if needed. On the other hand, a "time=" parameter might make sense, so if the object is out of range for longer than that time (or perhaps if the persist command was not re-issued within that period of time and then the object got out of range) it's persistance would expire. A default time of 1440 minutes would make sense if no time parameter is specified, so that the object would persist for a full day before expiring and going back to being treated like a non-persistant object until the persist command is again used on it.

TechnoZeus

[View Quote]

1  |   Order by index