1  |   Order by index

Sep 28, 2002, 9:17am

I think there should be a noSync argument for move commands so that the computer makes sure they start at RANDOM times and not all together with the universe / system clock.

- Mark

Nov 29, 2002, 4:07am

There is. It's been there since the command was first added. It's also the default though, so just don't use the Sync parameter when you want that behavior. Also, if you would like to make a delay timer to start several objects at distinctly different times, you can use the animate command as follows...

create animate me tag=99 wow 1 1 9000, astart; adone move 30 0 -20 loop

This example gives a 9 second delay and will work properly on the current version of Active Worlds in any world that has a wow1 texture, when used on an object that does not have a surface with a tag value of 99.

Back in early 1998 I suggested adding Trigger Delay support, which would make this much sort of thing simpler. Here is an example of a command using the (as yet unsupported) trigger delay concept to accomplish the same thing, but without being restricted to working properly only if a certain texture exists in that waorl or only if a certain tag value is not in the object being used...

create(9) move 30 0 -20 loop

In my original version of the trigger delay idea I used milliseconds, to coenside with the animate command's syntax, but since seconds are widly in use now, I have used seconds as the delay units in this example. There would have to be no spaces in the "create(9)" because that way it would be read in as a trigger, and the first thing after the space would be interpreted as a command. The unmber in parentheses (or braces, or what ever the developers decide to support) would be interpreted as a delay time in seconds, and a timer would be started that would cause the command following that trigger to happen when the timer runs out. There could be any number of such timers, and multiple triggers could be combined by placing a "/" between them, again with no spaces. For example...

create sign "start with this text"; create(3600) sign "You've been here an hour?"; activate(60) sign "clicked over a minute ago"; activate sign "just clicked"

or another example...

create sign "not clicked or bumped yet"; activate sign "clicked"; bump sign "bumped"; activate(60)/bump(60) sign "bumped or clicked over a minute ago"; activate(350)/bump(350) sign "clicked or bumped ofer 5 minutes ago"

Anyway, my point is that if these trigger delays were implemented, you could "easily" set up very specific delays on your move commands to keep them noticeably out of sync, but even without such and easy way to do it, the animate command makes it "possible" to accomplish the same effect.

TechnoZeus


[View Quote]

1  |   Order by index