Reflex 3 comes with a special script that I recommend every scene owner install: the Reflex console. The primary purpose is to enable "live programming" of all the other Reflex scripts. But this console also comes with extra goodies, like surveying and offering teleports to other visitors.

Once installed and with the default settings, try typing "/reflex" into public chat. You should see output like this:
/reflex (for this brief help)
/reflex About
/reflex Where [ <position vector> ]
/reflex Invite <name> (must be in this scene)
/reflex ShowBangs <On or Off>
/reflex ShowAllMessages <On or Off>
/reflex QuietSetSettings <On or Off>
/reflex FindScripts [ <script ID or Reflex name> ]
/reflex Settings <script ID or reflex name> [ <settings> ]
/reflex Validate [ <script ID or reflex name> ]
/reflex Bang <Reflex name>

See below for details.


In addition to the live programming you can do with the console, there are a bunch of nice utilities for making your job as a creator or even just a visitor a little nicer.

About command

Get some handy details about the experience/scene you are in right now:

/reflex about

- Script: Reflex console 3.1
- Experience: metaverse-machines-showroom
- Instance: 2460f8a3-f3bd-412f-bd18-cb2c2fe8636c
- Owner: galen
- Atlas URL:


Where command

This will report your current position or let you teleport yourself to a specific location. Examples invocations include:

/reflex where
/reflex where 10,0,1

Invite command

Until Linden Lab introduces a way to invite someone to teleport to your current location, this will do as an alternative. The person will need to already be in the scene with you. You can refer to them by a partial or full name, like so:

/reflex invite gal
/reflex invite galen

Try it on yourself to see what the other user will see. You won't go anywhere different, of course.

Live programming

The console enables you to find Reflex scripts and get and set almost all their settings while visiting. Moreover, this enables you to collaborate with other users who can help you with this sort of "live programming". Of course, settings you change will not be saved long term. You still need to write down your changes and enter them into your scripts' settings in the scene editor, but it is often much faster to experiment in a live scene than to repeatedly make small changes and then rebuild and test.

FindScripts command

Let's say you entered an existing scene to help a friend with Reflex script settings. One of your first steps might be to identify what scripts are out there. In the chat window, you could enter the following:

/reflex findscripts

The resulting list will return one line per script, with the script's unique internal ID, Name setting value, and script name listed, like so:

74.) [9] Sd4Left (Reflex door sliding 3.0)

This is one key reason you want to name most of your Reflex scripts (e.g., "Sd4Left" for "sliding door #4, left side"). You will use these names not only for identifying outgoing bang messages, but also so you can interact with them via this console.

You can also filter your search by entering some key words or phrases that represent the Reflex name or the script name. Some examples that would match the above:

/reflex findscripts sd
/reflex findscripts left
/reflex findscripts door sliding

If you know the ID of the script, you can search for it by that using:

/reflex findscripts [9]

Validate command

Ten seconds after a scene starts up, the console sends out a validation request to all Reflex scripts. Only those scripts that consider their settings to be invalid will respond in public chat. You can invoke this same general validation at any time using the following:

/reflex validate

If you wish to validate a specific script, you can refer to it by Reflex name or by ID like so:

/reflex validate sd4left
/reflex validate [9]

- Reflex script Sd4Left [9]: Valid

In this case, you will get a positive indication that the script's settings are valid, too. So if you don't get a response, check the name or ID. Or it may be that the script has somehow crashed.

Settings command

You can get or change settings using this command. To see all the settings, try one of the following:

/reflex settings sd4left
/reflex settings [9]

- Reflex script Sd4Left [9]: Valid

Settings for [9]:
- Name: Sd4Left
- OpenNamesCsv: AllDoorsTv:On, Sd4Tv:On
- CloseNamesCsv: AllDoorsTv:Off, Sd4Tv:Off
- ClosedPosition: 3.78,12.5,0.01
- ClosedOrientation: 0,0,-90
- SlideTrack: -1,-1,0
- OpenSeconds: 1.5
- CloseSeconds: 2
- AllowZeroTimings: 0
- UpdateMilliseconds: 30

To change settings, you use the same command, but add the changes you want to make after the name or ID, like so:

/reflex settings sd4left slidetrack: -2, 2, 0 | openseconds: 1.6|AllowZeroTimings:1

Put a pipe-separator between the settings you are updating at once. Don't bother including things you don't intend to change. And, as you can see, you are free to add extra white-space for readability.

The script should respond with an indication of whether the settings are valid and a report of what the new settings are for you to check. If you messed up the format for the settings, you'll see an error message hinting at what you might have done wrong. Just try again.

Bang command

Used to send out a "bang" message, simulating a Reflex sensor or other bang-emitting script. The message will pass along your own identity. If, for example, you sent out a bang targeted at a teleporter, it would send you off.

ShowBangs command

Use this to see the current console setting or change it, like so:

/reflex showbangs
/reflex showbangs on

With this enabled, you'll see all the bang messages that float around among scripts as they trigger behaviors.

ShowAllMessages command

Use this to see the current console setting or change it, like so:

/reflex showallmessages
/reflex showallmessages on

With this enabled, you'll see all the Reflex messages that float around among scripts. These include not only the bangs, but all others as well. This is not very useful to most users, but can be handy for the scripter who wants to get a better understanding of how to integrate custom scripts with Reflex.


Normally, when you set settings via the Settings command, you'll see validation results and a list of all settings values for review. If you don't want to see this feedback, you can turn this setting on like so:

/reflex quietsetsettings on