JPG-BOOT-EVENT

If you need to create a bunch of arrays, strings, or objects it is usually much faster to create them inside the boot event and then just reuse them from the other behaviors. For example:

rb room javascript enterroom .
actions = new Array( 'bow', 'wave', 'curtsey' );
act( actions.random(), actor );
/s

is insanely slower than (it creates a new array everytime someone enters the room! very bad!):

rb room javascript boot .
actions = new Array( 'bow', 'wave', 'curtsey' );
/s
rb room javascript enterroom .
act( actions.random(), actor );
/s

Try to do all your setup and preprocessing work in the boot event.

While working with your code, you can use the "rspawn boot" command to trigger a boot event. This allows you to test your boot code without having to wait for the mud to reboot. You can also define multiple boot events if all your code won't fit into one.

To help encourage people to do as much of their processing as possible in the boot event the mud uses a 10,000 execution limit on the boot event rather than the usual 1,000 execution limit on other events.