WorldsShaper Procedures

1. Getting Started

• Creating a New World
• Naming a World
• Saving a World File

2. Objects

• Naming an Object
• Deleting an Object
• Adding a Wall, Floor, or Ceiling
• Adding a Shape
• Moving Objects
• Scaling an Object
• Cutting and Pasting Objects
• Copying Objects
• Grouping Objects (WObjects)
• Infinite Backgrounds

3. Textures, Text and Colors

• Applying Textures to an Object
• Changing the Tile Size
• Changing the Color of an Object
• Adding Text to a Wall

4. New Rooms and Connecting Rooms

• Creating a New Room
• Creating Portals
• Connecting Portals
• Connecting Worlds

5. Libraries

• Adding an Item from a Library
  • Adding an Object
    • Objects Catalog
  • Adding an Action
    • Actions Catalog
  • Adding a Behavior (including Sensors)
    • Behaviors Catalog
  • Textures
  • Attributes

6. Miscellaneous

• Creating Mirrors
• Creating a Wear Wall
• Making Your World Multiuser
• How to Register Your World

Creating a New World

To create a new world, follow these steps:

1. From the File menu, choose New to open a new world.
2. A new world opens with a limited view of the yellow and red walls, plus a portion of the green floor and blue ceiling. Click Drive to move around in the room.
3. The world is called World1 until you save it with another name. Any subsequent new worlds you open will be numbered consecutively (World2, World3, etc).

Naming a World

World names must be unique to be correctly identified by the Server. To name a world, follow these steps:

1. Scroll up the Hierarchy Tree to the very top. The default world name is listed there (e.g. World1)
   IMPORTANT NOTE: If you change worlds while your working, the Hierarchy Tree does not automatically change to the current world you're in. You must right-click anywhere in the world and then click Edit Properties to make sure the Hierarchy Tree updates.
2. Click on the world name at the top of the Hierarchy Tree to bring up the World Properties in the Properties Box.
3. Double-click the Name property.
4. In the Edit Name box, enter a unique name to identify the world. You can use the same name here as for the .WORLD file you'll save, but this isn't required.
5. Click OK.
6. Save your world.

Saving a World File

NOTE: Before saving a world file to disk, you should name the world in its World Properties as detailed in the first section of this document. You will be prompted to save a world before quitting WorldsShaper, with a separate prompt for each world you've made changes in. As with all programs, save early and save often.

To save a World file, follow these steps:

1. From the File menu, choose Save. The Save World box opens.
2. World files should be saved in a project subdirectory within the InternalWorldsPlayer directory.
3. Enter a filename with the extension .WORLD.
4. World names must be unique to be correctly identified by the Server.
5. Click Save.

Naming an Object

To name an object, follow these steps:

1. Right-click an object in the 3D window to select it. The object's Properties list appears in the Properties Box.
2. Double-click the Name property. The Edit Name box opens.
3. Enter a descriptive name to identify the object.
4. Click OK.

The name you have entered appears in the object's Name property and will also appear in the Hierarchy Tree.

Deleting an Object

To delete an object, follow these steps:

1. Right-click an object in the 3D window to select it. The object's Properties list appears in the Properties Box. Make sure that the object is selected in the Hierarchy Tree (it should have a yellow rectangle around it. If it doesn't, click on the object's name in the Hierarchy Tree). Alternatively, if you want to delete an object like an Action that can't be selected by right-clicking, navigate the Hierarchy Tree and select the object you want to delete.
2. Click Delete (the Delete button is to the right of the Properties Box.

Adding a Wall, Floor, or Ceiling

To add a wall, floor, or ceiling, follow these steps:

1. Move up or down the Hierarchy Tree to reach the Contents list of the Room Environment properties.
2. Click on the Objects tab in the Libraries section.
3. Click on the object in the library you wish to add and drag it to the Room Environment Contents in the Hierarchy Tree. A new object will be listed under the Room Environment Contents.

Adding a Shape

You can import shapes built in a 3D modeling program into WorldsShaper. The shape must first be converted to the appropriate .RWX or .RWG file format.

IMPORTANT NOTE: The filenames of objects you import will become case sensitive when uploaded to a server. To keep things simple, make all object and texture filenames lowercase.

To add a shape, follow these steps:

1. Move up or down the Hierarchy Tree to reach the Contents list of the Room properties.
2. Click on the Objects tab in the Libraries section.
3. Click on Shape (empty) in the library and drag and drop it into the Room Contents in the Hierarchy Tree. A new shape will be listed under the Room Contents, and a semi-transparent cube will appear in your room at 0,0,0.
4. Click the new Shape item in the list. The Shape Properties appear in the Properties Box.
5. Double-click the File property listed under Shape Properties.
6. Enter the appropriate relative path and filenname (e.g. tex/table.rwg) and click OK. The filename is added to the File property in the Shape Properties list, and the cube changes into your object. Depending on the method used to convert the file, it may be too small (or too big) to see.

   Scaling and Moving a Shape

   To scale and move your object, follow these steps:

   1. In the Shape Properties list, double-click Transform. The Edit Transform box opens.
   2. Type a number in the [N]: field and click Scale by [N] (N=2 will double the objects size each time the Scale by [N] button is clicked). The 3D shape should now be visible in the room at 0,0,0. You can use the Transform box again, or the Scale and Move buttons above the Properties Box, to scale further or move the shape to a new location.

Moving Objects

WorldsShaper offers three different methods for moving objects in 3D space, each with different advantages:

• Use the Move buttons above the Properties Box for speed and intuitive visual movement.
• In the Rect Properties, edit the From and To properties to move a wall, floor, or ceiling with precision if you know the exact final location. These properties do not apply to 3D shapes.
• Edit the Transform property to move any type of object incrementally and precisely.

To move objects to a different level of the Hierarchy Tree, or a different room, use the cut and paste commands.

There is also a Snap Tool which will allow you to set a snap increment for objects. This feature will place objects such that their origins are at some multiple of that increment. For example, if you set an increment of 50 for x and y, you could place objects at (150, 250) but not at (229, 510). The tool will snap the object to the nearest point that matches the criteria. To activate or change the snap increments, go to the Edit Menu, Snap Tool Settings.

Using the Move Buttons

1. Right-click an object in the 3D window to select it.
2. Click one of the buttons above the Properties Box: hold the mouse button down and drag. As you drag, the selected object moves in the 3D window.

	The Move Horizontal button equates mouse movement with x=left/right and y=forward/back.
	The Move Vertical button equates mouse movement with x=left/right and z=forward/back.
	The Pitch button equates mouse movement with pitch=left/right and ignores forward/back input. Pitch revolves the object around the x axis.
	The Roll button equates mouse movement with roll=left/right and ignores forward/back input. Roll revolves the object around the y axis.
	The Yaw button equates mouse movement with yaw=left/right and ignores forward/back input. Yaw revolves the object around the z axis.
	The Scale button takes any mouse movement from the initial point and sizes the object smaller on left or back, larger on right or forward.

Editing the From and To Properties

This method is most useful when you need to fit an object into a specific position. The From property identifies the x,y,z coordinates of the bottom left corner of an object. The To property identifies the coordinates of its top right corner. Changing the positions moves an object.

(If you also change the relationship between the positions, the object will be resized as well as moved. Check the Extent property to see whether the width or height has changed as a result of changes to the From and To properties. Click the Undo button above the Properties Box if you have changed the object in ways you did not intend.)

To edit the From and To properties, follow these steps:

1. Right-click an object in the 3D window to select it and bring up the Rect Properties.
2. In the Rect Properties list, double-click the From property.
3. Enter new x,y,z coordinates in the Edit From box, and click OK. You can either place commas or single spaces between numbers for x, y and z.
4. In the Rect Properties list, double-click the To property.
5. Enter new x,y,z coordinates in the Edit To box, and click OK.

Editing the Transform Property

1. Right-click an object in the 3D window to select it and bring up the Rect Properties.
2. Double-click the Transform property on the right side of the Properties box. The Edit Transform box opens. This offers a matrix of possible transformations that WorldsShaper applies to the object, using the coordinates or amounts that you specify in the [X,Y,Z] and [N] fields at the top of the box.
3. Enter values for [N] and/or for [X,Y,Z]. The meaning of these values depends on the option you choose next.
4. Click one of the following options:

Moving to an exact location or moving in increments

In the following cases, N is the distance in units to move the object. A negative number is acceptable if you wish to move the object down the x, y, or z axis.

• Move x by [N] moves the object N units along the x axis.
• Move y by [N] moves the object N units along the y axis.
• Move z by [N] moves the object N units along the z axis.
• Move by [X,Y,Z] moves the object on all three axes simultaneously, with the values for x, y, and z representing distance in units to be moved from the object's current position.
• Move to [X,Y,Z] moves the object on all three axes simultaneously, with the values for x, y, and z representing the destination coordinates.

Pitch, roll and yaw: changing an object's orientation

In the following cases, N is the angle in degrees to revolve the object. A negative number revolves in the opposite direction.

• Pitch [N] revolves the object N degrees around the x axis.
• Roll [N] revolves the object N degrees around the y axis.
• Yaw [N] revolves the object N degrees around the z axis.

Mixed rotations

In the following cases, N is the angle in degrees to revolve the object, and x, y, and z indicate the axis of spin. For example, [0,0,1] spins on the vertical z axis. A negative number for either value, such as [0,0,-1] (for x, y, and z) or -1 (for N), revolves in the opposite direction.

• Spin by [X,Y,Z,N] revolves the object N degrees beyond its current position around the specified axes.
• Spin to [X,Y,Z,N] revolves the object N degrees beyond its original position around the specified axes.

Scaling to exact measurement

• Scale to [X,Y,Z] scales the object to those exact measurements along each of the axes.

Scaling by a factor

• Scale X by [N] takes the existing X measurement and multiplies it by N. If N is greater than one, the object will stretch on the x axis away from the object's registration point (where the red dot shows up when the object is selected). If N is less than one, the object will contract towards ther registration point.
• Scale Y by [N] takes the existing Y measurement and multiplies it by N. If N is greater than one, the object will stretch on the y axis away from the object's registration point (where the red dot shows up when the object is selected). If N is less than one, the object will contract towards the registration point.
• Scale Z by [N] takes the existing Z  measurement and multiplies it by N. If N is greater than one, the object will stretch on the z axis away from the object's registration point (where the red dot shows up when the object is selected). If N is less than one, the object will contract towards the registration point.
• Scale X, Y, Z by [N] applies an N proportional scaling to all axes of the object at once, again with N values larger than one making the object larger, values less than one making the object smaller.

When you're finished in the Edit Transform box, click OK.

Scaling an Object

WorldsShaper offers three different methods for scaling objects, each with different advantages:

• Use the Scale button above the Properties Box for speed and intuitive visual movement.
• Edit the From, To, or Extent properties to scale a wall, floor, or ceiling with precision if you know the exact final position or size. These properties do not apply to 3D shapes.
• Edit the Transform property to Scale any type of object incrementally and/or precisely.

Cutting and Pasting Objects

Use the Cut and Paste commands to move objects from one room to another, or to a different level of the hierarchy. For example, you can cut objects from the Room Contents and paste them into the Room Environment Contents. To cut and paste an object, follow these steps:

1. Right-click an object in the 3D window to select it. Make sure that the object is selected in the Hierarchy Tree (has a yellow rectangle around it). If not, click on the object listed in the Hierarchy Tree to select it.
2. Click the Cut button above the Properties Box. The object disappears from the 3D window.
3. Move up or down the Hierarchy Tree and select the Contents list where you want to insert the object.
4. Click the Paste button above the Properties Box.

The object is pasted at the same location in the 3D window, and appears at the new location in the Hierarchy Tree.

Copying Objects

To copy an object, follow these steps:

1. Right-click an object in the 3D window to select it. Make sure that the object is selected in the Hierarchy Tree (has a yellow rectangle around it). If not, click on the object listed in the Hierarchy Tree to select it.
2. Click the Copy button above the Properties Box.
3. Click the Paste button above the Properties Box.

The copy is pasted on top of the original at the same location in the 3D window. The copy is listed below the original in the Hierarchy Tree and is now selected. You can now move it to a new location using the Transform property or one of the Move buttons above the Properties Box. If you wanted the copy to be in a different position in the hierarchy, select the intended location in the Hierarchy Tree, then Paste there.

Grouping Objects (WObjects)

To group objects together (make a WObject), follow these steps:

1. In the Objects Library, you'll see Grouper. Click on the Grouper and drag and drop it to the level of the Hierarchy Tree where you want your grouped objects to be (e.g. Room Contents, Room Environment Contents or Infinite Background Contents). A WObject gets added to the Hierarchy list, and a red dot appears at 0,0,0 to mark the default position of the new WObject.
2. In the Hierarchy Tree, click on the triangle to the left of the new WObject to display its deeper properties.
3. Now you can click and drag objects from the Objects Library to add them to the Contents of the WObject.
4. Once all of the objects have been added to the WObject, any scale and/or move operations performed on the WObject will affect all the grouped objects together.
5. NOTE: Currently the Visible property of a WObject does not work. If you wanted the WObject invisible, you would have to set the Visible property of each individual object within the WObject.

Infinite Backgrounds

To add objects to the Infinite Background:

1. In the Hierarchy Tree, one of the deeper properties of your Room is Infinite Background. Scroll through the Hierarchy to locate your Room's Infinite Background.
2. From the Objects Library, drag and drop a Grouper to the Infinite Background listed in the Hierarchy. A new WObject is added to the contents of the Infinite Background.
3. Click the triangle to the left of the newly added WObject to reveal its deeper properties.
4. From the Objects Library, click and drag whatever objects you need (walls, floor, ceiling) to the Contents listed beneath the new WObject.

   Use only as many objects as you need in the Infinite Background for a particular room. For instance, if you have a room with only one window opening to the east, you may need only one west-facing wall in the Infinite Background to show a scene through that window. If you have a skylight, perhaps a single ceiling will suffice for an Infinite Background. For an outdoor scene, you may well need many walls and ceilings and perhaps even a floor. Drawing Infiinte Backgrounds will slow down the rendering speed of a room at least slightly.

5. In the Hierarchy Tree, click on the WObject to bring up the WObject Properties in the Properties Box.
6. Double-click Transform listed under WObject Properties.
7. Enter the numbers -500,-500,-120 in the [X, Y, Z] field.
8. Click the Move by [X, Y, Z] button, then click OK.
   
   These last three steps needed to be performed because the Infinite Background is viewed from a Camera at 0,0,0. As a result, the Infinite Background floor and some walls would not be visible if you hadn't moved the WObject so that 0,0,0 became the center of the Infinite Background room.
9. Texture or size the walls as you desire.

One reason to group your Infinite Background objects within a WObject is so that you can easily take this entire WObject, Copy it, and Paste it into any other rooms where you want an Infinite Background. You can build all of your walls individually in the Infinite Background's Contents, rather than embedding them in a WObject, but then all of the walls will have to be moved individually.

Applying Textures to an Object

A texture must be saved in an appropriate file format ( .bmp, .gif) before you can apply it to an object. Also, place all your textures in a subdirectory within your project folder (e.g. C:\InternalWorldsPlayer\MyWorld\textures). To apply a texture, follow these steps:

IMPORTANT NOTE: The filenames of textures you use will become case sensitive when uploaded to a server. To keep things simple, make all object and texture filenames lowercase.

1. Right-click the object in the 3D window to select it. The Rect Properties for the object appear in the Properties Box.
2. In the Hierarchy Tree, click on the triangle to the left of the selected rect to display the deeper properties like Material.
3. Click the triangle to the left of Material. The Material Properties list appears in the Properties Box.
4. Click on Texture listed beneath Material. The MaterialTexture Properties list appears in the Properties Box.
5. Double-click File. The Edit File box opens
6. Type in the relative texture path and a filename (e.g. textures/floor1.gif) and click OK.

The texture appears on the object in the 3D window, scaled to fit the object with a single image. You can change the tile size of the rect to repeat the image at a different scale.

Changing the Tile Size

To change the tile size, follow these steps:

NOTE: Tile Size is a property of the wall itself, rather than one of the material properties of the wall.

1. Right-click the textured rect in the 3D window to select it and bring up the Rect Properties in the Properties Box.
2. Double-click Tile Size listed under Rect Properties. The Edit Tile Size box opens.
3. Type in the desired width in units of a single tile, followed by the height in units. You can use 0 for either the x or y to indicate that you want the selected texture to stretch the full width or height of the object, or 0,0 to stretch the texture to fit on the object exactly once. Note that this may introduce distortion.
4. Click OK.

Changing the Color of an Object

To change the color of an object, follow these steps:

1. Right-click the object in the 3D window to select it. The Properties list for the object appears in the Properties Box.
2. In the Hierarchy Tree, click on the triangle to the left of the selected rect to display the deeper properties like Material. The Material Properties list appears in the Properties Box.
3. Double-click Color listed under Material Properties. The Edit Color box opens, showing current values for red, green, and blue.
4. Type in new values for each color in the mix, in the range 0- 255.
5. Click OK.

Adding Text to a Wall

To add text to a wall, follow these steps:

1. Right-click the wall in the 3D window to select it.
2. In the Hierarchy Tree, click on the triangle next to the selected wall to display the deeper properties like Material.
3. Click the triangle to the left of Material. The Material Properties list appears in the Properties Box.
4. Click on Texture listed beneath Material. The MaterialTexture Properties list appears in the Properties Box.
5. Double-click Texture Type listed in the MaterialTexture Properties.
6. In the Edit Texture Type box, select "Texture created from a text string" and click OK.
   Note: If you later decide to remove the text and use a texture file instead, this property must be reset first.
7. In the Material Texture Properties, double-click Text.
8. In the Edit Text box, type in the text that will appear on the wall, and click OK.

The text string appears on the wall. Click the Drive button and move around the room to check the appearance of the text. If necessary, you can adjust it by editing the following properties in the Material Texture Properties list:

• Font lets you enter the name of a font. You must check this against a list of the fonts present on your (or the end-user's) system.
• Size controls the font size of the text, and should be set to one of the available font sizes for your system, but not greater than 48. Because the text is scaled to 128x128 pixels, the font size will affect resolution rather than the actual text size. Choose the smallest size that is effective.
• Foreground Color sets the color of the text itself, based on values for red, green, and blue.
• Background Color sets the color of the wall behind the text, based on values for red, green, and blue.

Creating a New Room

To create a new room, follow these steps:

1. Scroll up in the Hierarchy Tree until you can see Rooms listed near the top.
2. From the Objects Library, click and drag a Default Room into the Rooms section of the Hierarchy Tree.
3. A new Room has been added to the Rooms list. You can now edit the properties of the new room (it is selected in the Hierarchy Tree), but the 3D window still displays the previous room. Until you have connected the two rooms with portals, the only way to view and navigate in the new room is to use the Change Location option under WorldsMarks (described in the next steps).
4. Click on the WorldsMarks button on the left side of the 3D viewer, and choose Change Location.
5. In the Change Location edit box, you'll see the current room listed within the URL. Change that to the room you would like to go to. For example, if you are in Room1 and you want to go to Room2, change the "Room1" part of the URL to "Room2" and click OK.

Creating Portals

The simplest way to open a portal in an existing wall is to delete the wall and replace it with another wall containing a portal.

1. Right-click a wall in the 3D window to select it. If the wall is not selected in the Hierarchy Tree (a yellow rectangle around it), click on its name listed in the Hierarchy Tree to select it.
2. Click Delete (to the right of the Properties Box). The selected wall disappears.
3. From the Objects Library, click and drag a wall/portal object to the Room Environment Contents of the Hierarchy Tree. For example, if you've deleted a Cyan wall, you'll want to drag and drop an East Wall/Portal object into the Room Environment Contents listed in the Hierarchy Tree.

Connecting Portals

Note: You must create both Portals first before trying to connect them, referring to each portal by name. Note that you can create the second room (and its corresponding portal) while still in the first room -- see Tutorial 1: Lesson2 for detailed instructions.

To connect one portal to another portal, follow these steps:

1. Right-click on a room's portal to bring up its Portal Properties in the Properties Box.
2. In the Portal Properties, double-click on Destination Portal Name.
3. Type in the name of the destination room's portal and click OK.
4. Double-click on Destination Room Name.
5. Enter the name of the room whose portal you're connecting to and click OK.

To connect the destination portal back to the current room, walk into the newly connected room through the portal you just connected, turn around and select the destination portal. Follow the steps above, connecting the destination portal and name to the current room.

NOTE:If you ever see this type of message:

Portal Portal331 specifies a connection to null#Room#SomePortal which isn't a portal!

you've most likely misspelled either the Destination Room Name or the Destination Portal Name. Make sure that you have typed in the names exactly - upper and lower case letters, blank spaces, etc.

Connecting Worlds

To connect two worlds, you will need to add a RemotePortal action to the portals that are going to be connecting the two worlds.

NOTE: Currently there are Remote Portals listed in the Objects Library. These are obsolete and will be removed in a future version of WorldsShaper.

To connect two worlds via portals, follow these steps:

1. Follow the instructions above for creating and connecting portals. You'll notice that in this case the portals don't automatically connect. In addition to entering the Destination Room Name and Destination Portal Name, you also need to enter the Destination World URL.
2. Under the Portal Properties, double-click on Destination World URL.
3. In the Edit box, either select the destination world from the list, or type in:
   rel:home:subdirectory/worldfile
   filling in "subdirectory" and "worldfile" with the relevant information for the destination world. For example:
   rel:home:Tutorial/MyWorld.world
   The portals will now appear to work, but don't walk through the portal yet. It's easier to finish the process on this portal first before walking through to the other world.
4. From the Actions Library, drag and drop a RemotePortal action to the portal you're working with listed in the Hierarchy Tree. An RPAction should now be listed under the portal's Actions list. (See Adding an Action for further information)
5. You now need a trigger for the RPAction. From the Behaviors Library, drag and drop a SameRoom sensor to the portal you're working with listed in the Hierarchy Tree. A SameRoomSensor should now be listed under the portal's Event Handlers list. (See Adding a Behavior for further information)
6. Click the triangle to the left of the new SameRoomSensor listed in the Hierarchy Tree.
7. Beneath SameRoom sensor, click on Targets.
8. To the right of the Properties Box, click on the Add button.
9. In the Add to Targets box that comes up, select the RPAction you just added to the portal and click OK. Now the next time you load this world and enter this room, the other world you have connected to will load.
10. Save your world.
11. Walk through the portal and repeat the above steps with the connecting portal in the other world.

If a world you are connecting to takes awhile to load, you will see a default solid color where the portal is until the world has finished loading. To avoid this, you must add a texture to the portal itself. You will only see the texture when the world on the other side is loading. To add a texture to a portal, follow these steps:

1. In the Hierarchy Tree, find the portal you want to add a texture to.
2. Click on the triangle to next to it to reveal further properties.
3. Click on the triangle next to Material listed beneath the portal.
4. Click on Texture to bring up the MaterialTexture Properties in the Properties Box.
5. Double-click File listed under the MaterialTexture Properties.
6. In the Edit File box, type the relative path of the texture. For example:
   tex/wall1.bmp
   and click OK.
7. You won't see the texture if the world on the other side has already loaded.

Adding an Item from a Library

The libraries can be viewed with icons or just with text. Under the Libraries menu at the top of WorldsShaper, click on Icons On/Off to toggle between the icons and text.

All of the libraries use the same "drag and drop" method to add a library item to the hierarchy or to another object. To add an item from a library, follow these steps:

1. Scroll up or down the Hierarchy Tree to find the object or property to which you want to add a library item.
2. Click on the appropriate Library tab (Objects, Actions, Behaviors) in WorldsShaper to view a library catalog.
3. In the library, click on the item you want, holding down the mouse button, then drag it to the Hierarchy Tree and drop it (release the mouse button) in the appropriate section of the Hierarchy. The following four sections will help you with the specifics for adding Objects, Textures, Actions and Behaviors.

Adding an Object

To add an item from the Objects Library, follow these steps:

1. Items in the Objects Library can be added to three places in the Hierarchy:
   • Room Contents
   • Room Environment Contents
   • Infinite Background
   Most objects can also be added to the contents of WObjects. Scroll through the Hierarchy Tree until you can see the place where you want to add the object.
2. Click the Objects tab in the libraries section of WorldsShaper to see the catalog of Objects.
3. In the library, click on the object you want, holding down the mouse button, and drag it to the spot in the Hierarchy where you want the object. Release the mouse button. The object you selected is added to the Hierarchy tree with a default name, and the object's properties appear in the Properties Box.
4. If you would like to give your object a distinctive name, double-click on Name in the Properties Box and enter a new name in the Edit Name box. Click OK.

   If you have chosen a Shape from the Object Library, the Shape is added at location 0,0,0. Edit its Transform property to move it to a new location and/or scale it to the correct size.

Objects Catalog

Adding an Action

To add an item from the Actions Library, follow these steps:

1. You can apply actions to the Actions property of objects within your 3D world. There are quite a few actions in the Actions Library - check the description of individual actions in the Actions Catalog to see what types of objects to apply them to.
2. Click the Actions tab in the libraries section of WorldsShaper to see the catalog of Actions.
3. In the library, click on the action you want, holding down the mouse button, and drag it to the Actions property listed under the object that you want to hold the action. Release the mouse button. The action you selected is now attached to the object.
4. If you would like to give your action a distinctive name (and this is a good idea if you intend to have several actions throughout your world), double-click on Name in the Properties Box and enter a new name in the Edit Name box. Click OK.
5. Check the description of individual actions in the Actions Catalog to see how to set a particular Action's properties.

Actions Catalog

• Parameters common to all actions
• Actions:

  Wait Stdout Sequence Animate Gravity Move Print Pickup RemotePortal Loading Parallel Sound SetVisibleBumpable Teleport URL Talk Dispenser PlaybackRecording StopRecording

  The SET Actions SetInteger SetFloat SetBoolean SetString SetColor Set2DPoint Set3DPoint SetURL SelectAvatar Wear Posable Trade MoveCamera OpenURL VideoControl NotifyScript CameraHeight

Parameters common to all actions

There are two parameters that all Actions share in common. These are:

• Name
  This is simply the name you choose to give the Action. Note that naming Actions with something distinctive is very important! When you have to target Sensors to Actions, you'll be presented with a long list of every Action present in that .WORLD file, potentially a very long list for a bigger project. This name also shows up in the Actions list when you double-click and edit the object.
• Trigger Now
  Trigger Now enables you to test an Action without having to go through the hassle of creating a dummy trigger and jumping back and forth between Action and Sensor, or having to move around in Properties at all. Just double-click on Trigger Now and set the Edit box to True. Your Action should fire off right then, and Trigger Now will revert to False again.

Wait

Wait is a pretty straightforward action. You set a WaitAction property that specifies how many seconds the action should wait. When triggered, all the action does is start, wait that number of seconds, and then it's done. Wait is generally used as part of a Sequence.

Specific properties of Wait

• Duration (s)
  Type any integer or decimal value of seconds. Note that duration values smaller than .2 might be impacted by frame rate considerations and won't reliably give the same length wait each time.

Stdout

This action writes text to the "standard output", which means that if the user has a log file going, the text will appear there. Useful for debugging.

Sequence

Sequence is an ordered list in which you can put other actions, actually "pointers" to actions located in any object.

• Properties of a sequence
• Adding a Sequence
• Adding actions
• Synchronization issues
• The Wait action
• Editing the actions inside a sequence
• Sequences within sequences

Specific properties of Sequence

• Components: Listed beneath a SequenceAction in the Hierarchy Tree, this is a container where you put the list of actions that will be part of this sequence.
• Loop count: how many times you want this sequence to run once it's triggered.
• Loop Infinite: set to true if you want the sequence to loop indefinitely.

Adding a Sequence

1. To make a sequence, right-click on the object you want to add a sequence to (or click it in the Hierarchy Tree). The sequence can be just about anywhere, because it will be calling actions that may or may not be contained in the same object, and the actions will be taking place in the objects they're owned by.
2. Click the triangle next to your selected object in the Hierarchy Tree to reveal the deeper properties.
3. From the Actions Library, click and drag a Sequence action over to Actions listed beneath your object. A new SequenceAction is now listed beneath the Actions of the selected object.
4. Double-click Name under SequenceAction Properties listed in the Properties Box. Change the name of your sequence so that you will remember what this particular sequence does.

Adding actions

To add actions to a sequence, find the sequence in the Hierarchy Tree and click on its Components. This List will initially be empty. Click the Add button and add previously created actions into your sequence, one at a time (when the Add to Components box comes up, click on the downward-pointing triangle to the right of the first listed action. This will reveal a list of all the actions you have previously created). Note that you should try to add items to the sequence in the exact order they will run. When you Add another action to the list, it will always add to the last position, there is no insertion point! However, you can Delete from any point in the List. You can overcome the no-insertion-point problem slightly by careful use of Cut and Undo, because you can Cut from anywhere in the list but Undo will always place the action last in the list.

Synchronization issues: Multithreading

Another problem you might run into with sequences is that each item in the sequence's Components needs to finish executing before the next item can begin. This has the following unfortunate consequences:

• You shouldn't put an infinitely looping action into a sequence, because that action will never complete itself. In theory you could put an infinitely looping action as the LAST thing that happens in a sequence, but then WorldsShaper has to deal with the overhead of two things running constantly: the looping action and a sequence that it can't close.
• You can't use a single sequence to synchronize two things to happen at exactly the same time. For instance, if your sequence had a Move action that made a door open and then a Sound action that played the sound of a door opening, the door would open all the way, stop, and only then would the sound be played. The way around this particular problem is to have one sensor trigger two different sequences, one containing all the Sounds and one containing all the Moves. You would also have to factor in the times that the sounds and moves themselves take to figure out the ultimate timing of each sequence, especially when trying to synchronize the sequences to each other. Sometimes you won't need a sequence at all, you just need to have one sensor trigger multiple actions, in which case the actions will start as close to simultaneously as is possible.

Wait

Because of the multithreading issues and also for general utility, you will frequently be placing Wait actions into your sequences. Wait actions are another case of an action that can be owned by just about anything. A good practice is to have all the wait actions for your world placed inside some easy-to-find object like the first room's Actions list. Remember that you can share the same wait action for several different sequences but if you change the timing by double-clicking the Wait in any given sequence you'll be changing the "master", not a copy. You might create a library of several commonly used units of time in progressively larger steps, for example .2 seconds, 1 second, 5 seconds, 30 seconds. Then you can always insert 2 1-second waits to substitute for having to make a whole new 2-second-long wait action from scratch someplace, and you can avoid clutter in the list whenever you add an Action.

Editing actions from within a sequence

You can click on any action within a sequence to make changes to its properties listed in the Properties Box if you'd like. But again, remember that you are really just taking a "shortcut" to where that action really exists, and if you edit an action in a sequence, the changes you make will show up in every other sequence that uses that action, as well as in the action's "master" back in whatever object it's owned by. However, if you Delete an item from a sequence, you won't be deleting the "master", just a copy, and clicking the Owner button after double-clicking an action in a sequence will take you back up to the sequence, not to the action's real owner.

Sequences within sequences

Since a sequence is itself an action, there's no reason why you can't nest other sequences inside a larger sequence. Just keep in mind that the entirety of the nested sequence needs to be executed before the next item in the larger sequence's list can be started. And don't make the mistake of putting a sequence inside itself! We make no guarantees about what will happen in this case.

Animate

Animate places bitmaps on an object and cycles through them in a specified linear sequence. You can apply an animation to objects like walls that take a Materials property for textures, but you won't be able to "animate" a Shape in this way, because a Shape's textures are stored internally. If you just want to move a Shape through space (or a wall for that matter), you'll want to use the Move action instead.

Tiling is the same as the Material that existed on the wall before you start the animation. For instance, if you have tiled a wall to repeat its texture four times horizontally (250,0 tiling on a 1000-wide wall) any animation you attach to the wall will also tile four across. For this reason you might want to attach animations to separate rects rather than to architectural walls of a room.

Specific properties of Animate

• Cycle time
  Type the total time the animation should take, in milliseconds (default is "1000" or 1 second). The display time for each frame becomes this number divided by the number of frames.
• Cycles
  Type the number of times the animation should run once triggered.
• Infinite Loop
  Set to true if you want the animation to loop continuously.
• Frame list
  Type a list of all the frames that make up your animation. List the relative URL of each image file (including the extension) in order with a single space between each file name. See the screenshot below for an example. You can animate .gifs (but not animated gifs), .bmps., or .bmps

Gravity

When the Gravity action is triggered, it will pull users (their camera) to a specified point in the room. There is no escaping a Gravity action - no matter where you are in a room, if you trigger it, you will move to the designated point. When a Gravity action is applied to a wall, the user's camera will be pulled to the lower left corner of the wall (where the red dot is when the wall is selected). Since the camera height for avatars is set at 150, the user would sink into the floor until its "eye height" was at the lower left corner. Since this probably isn't the desired effect, what you need to do is create a copy of the wall to attach the gravity action to. For example, if you wanted the Gravity action to carry you to the center of a room, you would first make a copy of a wall. Attach the Gravity Action to the copied wall. Make the copied wall 1 pixel high and one pixel wide, and position it at 500,500,150 (assuming a default 1000x1000 room). Now when the Gravity action is triggered, the user will be pulled to the center of the room.

Specific properties of Gravity:

Force - This number is how "fast" the user gets pulled toward the target of the gravity action. The higher the number, the more of a "tug" the user receives. The default is set at 300.

Move

• The "playback-record" method of making a Move action
• The "by the numbers" method of making a Move action
• The properties of the Move action
• Move action tips and tricks

Move replaces the old-style behaviors that don't have sensors, like Spin and Post-spin, and also allows you to dynamically move objects through space. For instance, you can use the Move action to spin a door rectangle on its z axis to make it look like it is swinging closed, or to make a ball appear to roll across the floor instead of just spinning in place.

All Move actions take place around or from a point on any given object that usually its bottom left corner for rects or an approximate center for a Shape. But some objects that you've added, particularly default walls and floors/ceilings, may already have a transform applied to them. For instance, a floor is really just a wall pitched over 90 degrees, and a West wall is really an East wall with a 180 degree rotation , so the initial position may not be what you expect in an absolute coordinate sense. As a result, it can often take some experimenting to get the Move action to do what you want. You may have to flip objects upside down or turn them around to get the origin in the right place for your particular move action. Look for the red dot in any given object: that dot will be the origin around which move actions will take place.

There are essentially two ways to establish a Move action: a playback/record metaphor and a by-the-numbers metaphor. You can use either, but follow the instructions given here carefully.

The playback-record method

1. Right-click the object you want to move, or find it in the Hierarchy Tree.
2. In the Hierarchy Tree, click the triangle to the left of the object to reveal its deeper properties.
3. In the Actions Library, click on Move and drag it to Actions listed beneath your object in the Hierarchy Tree.
4. If it's not there already, move the object to its intended beginning position, size, rotation etc. You can do this by:
   • Using the horizontal move, vertical move, scale and various spin buttons above the Properties box.
   • Or select the object and double-click Transform listed in the Properties Box, and use the various transform boxes to move your object to its final parameters. Click OK to close the Edit Transform box.
5. In the Hierarchy Tree, click the new Move action to bring up its MoveAction Properties in the Properties Box.
6. Double-click the Copy Start/End property under the MoveAction Properties.
   
   

   This Property is actually a crude utility that allows you to view start and end parameters of an object's move, or save the present parameters as either the start or end of a move: 1: Snaps the object to the Move's start parameters. 2: Snaps the object to the Move's end parameters. 3: Records the object's current parameters as the Move's new start parameters. 4: Records the object's current parameters as the Move's new end parameters.

   
   
7. Since the object is now in its starting position, type 3 into the Edit Copy Start/End box. Click OK.
8. Now move the object to its intended final position, size, rotation etc.
9. In the Hierarchy Tree, click your Move action again.
10. Double-click the Copy Start/End property.
11. Enter 4 in the Edit box and click OK. Now you've saved the current parameters of the object as the final parameters for the Move.
12. Adjust the Cycles and Cycle Time properties as necessary. Click here for more information on these properties.
13. Add a sensor that triggers your action and see if your Move behaves like you expected. If not, return to your Move action and tweak as needed.

The by-the-numbers method

1. Right-click the object you want to move, or find it in the Hierarchy Tree.
2. In the Hierarchy Tree, click the triangle to the left of the object to reveal its deeper properties.
3. In the Actions Library, click on Move and drag it to Actions listed beneath your object in the Hierarchy Tree.
4. Enter values for the objects intended beginning position, size, rotation etc. by doing the following:
   • Double-click the Start Point property. In the Edit Start Point box, enter the X, Y, Z position you'd like the object to start at.
   • Double-click the Start Scale property. In the Edit Start Scale box, enter the X, Y, Z values you'd like the object to begin with.
   • Double-click the Start Spin property. In the Edit Start Spin box, enter values for one or more axes you want the object to spin around.
   • Double-click the Start Rotation property. Enter the facing for the desired beginning rotation.
5. Enter values for the objects ending position, size, rotation, etc. by doing the following:
   • Double-click the Translation Extent property. In the Edit Translation Extent box, enter the X, Y, Z position you'd like the object to end at.
   • Double-click the Scale Extent property. In the Edit Scale Extent box, enter the X, Y, Z values you'd like the object to scale during the move.
   • Double-click the Spin Axis for Extent property. In the Edit Scale Extent box, enter values for one or more axes you want the object to spin around.
   • Double-click the Extent Rotation Amount property. Enter the facing for the desired final rotation.
6. Adjust the Cycles and Cycle Time properties as necessary. Click here for more information on these properties.
7. Add a sensor that triggers your action and see if your Move behaves like you expected. If not, return to your Move action and tweak as needed.

Specific properties of Move

• Cycle time (in seconds)
  Specifies how long the entire move should take from beginning to end, in seconds. WorldsShaper will interpolate frames between the start and end, so slower moves will tend to look smoother, whereas quick radical moves might look a little choppy depending on your frame rate.
• Cycles
  Specifies how many times the Move will repeat when triggered. If you want it to loop infinitely, set the Loop Infinite property to true (see below).
• Copy Start/End 1/2:->Action->Owner 3/4: Owner->Action
  
  

This Property is actually a crude utility that allows you to view start and end parameters of an object's move, or save the present parameters as either the start or end of a move: 1: Snaps the object to the Move's start parameters. 2: Snaps the object to the Move's end parameters. 3: Records the object's current parameters as the Move's new start parameters. 4: Records the object's current parameters as the Move's new end parameters.

• Translation Extent
  The final point position of an object's Move.
• Scale Extent
  The final scale along each axis for an object's Move.
• Spin Axis for Extent
  The axes about which any spin takes place. Any value between 0 and 1 for any axis "makes sense" though other values are accepted.
• Extent Rotation Amount
  The final rotation for an object's Move.
• Start Point
  The start point position of an object's Move.
• Start Scale
  The start scale along each axis for an object.
• Start Spin
  The start spin position along each axis for an object.
• Start Rotation
  The initial rotation for an object's Move.
• Loop Infinite
  Set to true if you want the Move action to loop infinitely once triggered.

Move tips and tricks

• Note that if you want the object to move back to its start point instead of jumping back there, you will have to write a whole separate Move. Moves are point-to-point, and to reproduce a complicated series of Moves you'll need to create a Sequence.
• Use the "1" and "2" options in Copy Start/End 1/2:->Action->Owner 3/4: Owner->Action to view start and end positions while you're editing the Move action. That way you can avoid having to re-trigger all the time to see what it does.

Print

Print outputs text to WorldsShaper's text window, the same area where chat messages show up if you're hooked up to a multiuser server. A practical use for this is to combine Print with a Startup sensor to give your user a welcoming message when they enter the world. The Print action can be attached to any object within a room or within a room's Actions list.

Specific properties of Print

• Text Out
  Type any text you want output to the message window. Text will all appear on one line; you cannot force a line break. Use separate Print commands in a Sequence to simulate line breaks if needed.

Pickup

This action is currently under development and does not work.

RemotePortal Loading (RPAction)

A RemotePortal action is adding to portals that will be connecting worlds. To create a new RPAction, you must place it in the Actions List of the portal itself, not in the room or other objects in the room. Most often a SameRoom sensor is used to trigger the RemotePortal action. You could however use a Startup or other sensor to change the point in time where the user will "take the hit" of having to stop and load a .WORLD file into memory, potentially as a download. Or you could put the SameRoom Sensor in a different room, for instance to have the world behind the RemotePortal start loading while you're still two or three rooms away, rather than when you're already in the room.

Note: The major modifiable characteristics of a RemotePortal Loading action are which portal it's placed in and what type of sensor triggers it.

Parallel

This action is currently under development and does not work.

Activating a Parallel action will activate all of its targets simultaneously, allowing you to set several sequences into motion at once.

Sound

In a Sound action, you may specify a sound in any number of formats.

If you enter a URL to a Sound ending with .wav or .mid, then that WAV or MIDI file will be played. These types of files may point to files on the user's local hard drive bundled with the world.

For URL's ending with any other extension, the URL will be passed as-is to Windows Media Player, which will attempt to play the URL given. You could in this manner point to streaming audio for example. Unfortunately, since Windows Media Player can't interpret Worlds' home:/ URL's, you can't specify local files in a sound action other than wav or midi files, since Windows Media Player doesn't know where the world was installed on the user's hard drive. This is a known limitation that we hope to resolve, in order to allow things like playing MP3 files and other new audio formats that come along.

The Music Manager (in the Options menu of the WorldsPlayer Interface), used primarily for room-based background music, works similarly. .WAV and .MID files are processed by Worlds through Windows' Media Control Interface. Any other file extensions are passed to Windows Media Player, which will play the sound if it can.

Note that only the Windows Media Player "engine" is utilized by Worlds; specifying a URL to be handled by WMP will not result in the Windows Media Player application being launched or displayed; it will simply play whatever audio you have sent it in the background.

• Properties of a sound
• Allowed sound types

Specific properties of Sound

• Sound File URL: Type the file location of your sound here, relative to the WorldsShaper root. You can also give absolute paths like C:\sounds\loudsound.wav.
• Max Volume: This is set to a default of 1. You can think of 1 being about 100%, but since sound volumes are always variable depending on speakers, volume of the source sound and other intangibles, you should experiment with different levels here to get the desired effect. You can set Max Volume very high, to numbers like 500 or more, but you are risking blowing out your speakers if this sound gets triggered while you are close by, or at least you'll get a nasty surprise! Ideally this should be set below 1.0, otherwise thre is the potential for distortion. If your sound is still too low-level try raising the level in the soundfile itself by editing the .WAV file. If you don't have a good .WAV editor, check out this site.
• Stop Distance: Defines the range in which the sound can be heard. If Attenuate With Distance is set to True (the default), the sound will be maximum volume when you are standing next to it, and the sound will fall off gradually as you move away. At the Stop Distance, the sound level will finally be zero. The attenuation is linear relative to distance from the object.
• Times to Repeat:Equivalent to the Loop property of many other actions. Once triggered, this sound will play that many times in a row. Setting to -1 will make the sound loop endlessly until you exit the World.
• Attenuate with Distance: Can be set to True or False. If you set it to False, the sound won't fall off as you move away but will cut off abruptly at the Stop Distance.
• Do panning: If Do Panning is set to True, the sound will be louder through the right speaker if it's off to your right, louder in the left if it's left of you, and that sound will generally behave "in stereo". If Do Panning is set to False, that sound will be "mono" and won't change relatively left or right, but will diminish with distance to the same degree in both speakers if you set Attenuate with Distance to True.
• Room Hops til sound dies
  Room Hops let you "carry" a sound with you from room to room as you pass through portals. Each number above one carries the sound through that many rooms; if you set it to 2, you can hear the sound in two rooms, after having passed through one portal. If you go through a second portal, into a third room, the sound stops. The volume falls off with distance from the original sound in each case, by two different algorithms (see below). Also make sure to read about limitations of using room hopping.
• Door based audibility
  Can be set to True or False. Sounds heard via room hopping can either be handled as if they had to go the "long way" through the door in order to be heard (Door Based Audibility = True), or if they went the "short way", as if whatever walls the rooms might have had in between don't block out sound (Door Based Audibility = False). This affects the volume you will hear the sound at because the two distances will typically result in two different proximity-based volume levels. See the diagram below:
  The red line indicates a distance path for Door Based Audibility = True, the blue line is a distance path for Door Based Audibility = False. Note: for Door Based Audibility = False, the two rooms are lined up against each other so that the geographies make relative sense, based on which portal you entered from. A side effect is if you have multiple room hops between two rooms connected to each other by more than one portal things can get a littlke strange.

Allowed sound types

• .WAV files: The .WAV format is a versatile PCM format that can accept a variety of sample rates and is a pure representation of the sound that does not suffer from compression glitches. The actual samplerate and bitdepth that can be played ultimately depends on the sound card that each user has in their machine, but there are safe choices that you can make which almost all modern sound cards can successfully play back:

• 44.1 kHz 16 bit
  44.1 kHz 8 bit
  22.05 kHz 16 bit
  22.05 kHz 8 bit
  11.025 kHz 16 bit
  11.025 kHz 8 bit
  

• MIDI: General MIDI is a blanket term for a .MID file that stores a MIDI sequence intended for playback on the built-in synthesizers of a computer's soundcards. Voicing, quality, and the individual sounds of each MIDI instrument are determined entirely locally by the soundcard, so a typical General MIDI sequence needs to be finessed for a variety of common soundcards and tested on different cards and platforms. You must use the .MID extension for MIDI file URL's.

SetVisibleBumpable

Modifies the Visible and Bumpable property of an object "on the fly" in response to a sensor. After you trigger a SetVisibleBumpable action and then look at the object's Visible and Bumpable properties, you'll see that they've been switched in response to the action and will remain that way until you edit them by hand or set off another action that changes them back.

Specific properties of SetVisibleBumpable

• Target Bumpable
  Set to No (false) to be able to pass through the object and disable any Bump sensors it contains.
• Target Visible
  Set to No (false) to make the object invisible.

Teleport

When triggered, the Teleport action causes the user to be teleported to a designated room or world. After adding a Teleport action to an object, go to the room or world where you want the user to be teleported. Find the spot where you want them to land and stand there. Use the WorldsMark/Change Location option to see the URL of your current position (See image below). Copy the full URL and return to the object that has your teleport action attached to it. Use the various parts of the copied URL to set the Teleport properties (see examples next to each property listed below).

Specific properties of Teleport

• X,Y,Z
  Specifies where in a room the user will land. (In the Change Location URL, the xyz coordinates come after the "@" symbol, in the above example: 3127.0, 134.0, 150.0)
• Dir
  Enter 0 - 360 to specify the direction the user will face. (In the Change Location URL, the direction number comes after the xyz coordinates, in the above example: 322.0)
• Room Name
  Specifies the Room the user will land in. (In the Change Location URL, the Room Name comes after the "#" symbol, in the above example: Reception)
• World URL
  Specifies the World the user will land in. (In the Change Location URL, the World URL is the part of the URL before the "#", in the above example: home:GroundZero/GroundZero.world)
• Use Default Coordinates
  If true, the user will land in the default "landing spot" in a room. All other "position" properties (X,Y,Z etc.) will be overridden if this is set to true.
• Dimension Name
  Not currently used. A dimension is basically a copy of a room that occupies the same "space" but is physically a different room. Currently dimensions are created when the capacity of the original room reaches a maximum.
• Show dialog
  The default for this is "true". When a user is teleported to another world, a small dialog box comes up that says, "Hang On! Teleporting..." with the option to cancel the process. If you do not want this dialogue box to pop up when your Teleport action is triggered, set this property to false.

URL (SendURL)

URL allows you to launch web pages in response to the triggering event. The default browser used by WorldsPlayer is Internet Explorer.

Specific properties of URL

• Destination
  Type the URL of the desired web page location here. Will accept all the common protocols like http, ftp, mailto etc.
• Description
  A default property of SendURL is that a dialogue box is displayed when a SendURL action is triggered. It's a small pop-up box titled "Browse?" that says "Would you like more information?". The user is given options to click "Yes" or "No". If you want the dialogue box to say something else, in the Description property type whatever text you would like. When a description is entered into this property, the options in the pop-up window will change to "OK" and "Cancel".
• Destination Override
  This property is not generally used. It currently is in use only with the world called Hang. Destination Override is used when an Override World has been designated.
• Override World
  This property is not generally used. It currently is in use only with the world called Hang. An Override World property might be used if a world exists on two servers and certain properties of the world change depending on which server a user is logged in to.
• Send User Info (auto-login)
  If set to true, this will log the user in to the requested page using their Worlds user information. If set to true, another property appears below this one:
• CGI uses GET instead of POST
  This property appears only if Send User Info is set to true. This property designates whether the Send User Info is sent using the cgi command GET or POST.
• Display Dialogue Box
  Change this to false if you do not want a dialogue box to pop-up before launching the URL.
• Cancel only
  Cancels the dialog allowing nothing to happen. Not generally used.

Talk

Talk is another way that you can attach triggerable text messages to an object. But this time the talk will appear to be coming from the username who created the action in the object rather than just appearing in the interface, and it requires that anyone receiving a Talk action be online (Print does not).

Dispenser

Currently under development. This action does not work at this time.

Playback Recording

New actions have been added to WorldsShaper as of revision 1830 to control the new Recorder feature. With these actions, you could record "3D cutscenes" and play them back in response to some trigger in the world... for example, a cheat button in a puzzle could play back a recording of a user solving the puzzle.

The only property of the Playback Recording action is the "FileName", which should be a URL to the recording file you wish to play back.

Stop Recording

This action, which has no properties, will stop any currently playing recording (See Playback Recording above).

The SET Actions

These actions alter the properties of another object. As an example, if you wanted to let the user select the force on a Gravity Action, you could set up 2 buttons that have a SetInteger Action (since Force is an Integer) on them with different settings and with the Gravity Action as a target. Click one and you go fast, click the other and you go slow.

Specific properties of the SET actions

• Set To
  Set To tells the action what you want to set the target to. For example, if you want to set an Integer value to 3, put a 3 here.
• Duration
  The Duration property will change the value you set over time. For example, if an integer starts at 10 and goes to 100, you could give it a duration of 9 seconds so that it goes smoothly. SetString and SetBoolean don't have this property because you can't scale them over time.
• Target, Target Room, Target Name, Property Name, Use Parameter, Parameter Name
  These are all used to select the target attribute to be changed by the SetXXXAction. The target is chosen through WorldsShaper either by room and object name, or by selecting the target object from a list of objects. If the name is present, then the object is searched for using the name (room defaults to the action's room). If the name is not present, or if the object was not found, then the selection from the list of objects is used. If the object hasn't been chosen in any way, return the object that this action is attached to.

SetInteger

This action alters any property of an object that is an integer.

SetFloat

This action alters any property of an object that is a floating-point number (one that can have a decimal value).

SetBoolean

This action alters any property of an object that can be set to true or false.

SetString

This action alters any property of an object that is a string (of text).

SetColor

This action alters any property of an object that is an RGB value.

Set2DPoint

This action alters any property of an object that is a 2-dimensional point in space.

Set3DPoint

This action alters any property of an object that is a 3-dimensional point in space.

SetURL

Under development.

SelectAvatar

When a Select Avatar action is applied to an object and then triggered, the user is presented with a dialogue box that asks "Change avatar to (specified avatar)?". If the user selects "yes", their avatar changes to the specified avatar.

Specific properties of Select Avatar

• Avatar URL
  You'll need to specify which avatar you want the user to select. Check the list of avatars available in the VIP/Change Avatar menu. In the Avatar URL edit box, type:
  avatar:avatarname.rwg
  where "avatarname" is the name of the avatar you want. All the articulated avatars are .rwg files.
• Display Dialogue Box
  The default for this property is "true" - when the user triggers a Select Avatar action, a dialogue box comes up which asks "Change avatar to (avatar name)?" with the option to click yes or no. If you don't want the user to see the dialogue box (and therefore to change their avatar without asking them) then in the Display Dialogue Box edit box, select "Don't ask". Change the property back to "Ask user to ok choice" if you want the dialogue box to appear.
• Cancel only
  Cancels the dialog allowing nothing to happen. Not generally used.

Wear

This action is used in the creation of a "Wear Wall" (e.g. in the Gallery of Metamorphics). To learn how to create a Wear Wall, see the How to Create a Wear Wall section of this document.

Posable

The Posable action allows you to assign triggerable actions to a "bot" or avatar that you have placed within a world. You can only use the actions that a particular avatar already possesses - see the Actions list of each avatar. For example, if you have the avatar Charlie in your world, you can assign the following Posable actions to him: Wave, Yes, No, Happy, Upset, GetLost, Look, Flip, Dance, Rocknroll, Macarena, Pirouette, Twirl, Achoo, Bow, and Sleep. If you assign a Move action (make it move from point A to point B) to an avatar you have placed in a world, the avatar will automatically use a walking action while in motion.

To assign a Posable action, you will first need to add an avatar (Articulated object) to your world. See Articulated under Object Catalog. You then add the Posable action to the avatar (listed as PosableShape in the Hierarchy Tree) and some kind of sensor to trigger the Posable action.

NOTE: At this time, Posable actions will only run through the specified action once (you cannot loop them) and they also cannot be added to a Sequence action.

Specific properties of Posable

• Action
  The default for the Action property is "wave". If you want the avatar to do any other action when triggered, type in the name of an action (see your particular avatars actions list) into the Edit Action box.

Trade

This action is currently under development.

MoveCamera

This is a new action that is still under development. It is an action that would affect whatever camera triggers it. Designed for events like "fly-throughs" of a world.

OpenURL

The OpenURL action opens a 2D browser window within the 3D chat window, not as a separate window. This 2D browser has a simple toolbar (back, forward, stop, refresh, home and back to 3D). The 2D window is anchored at the lower right corner of the 3D viewing window, so if you specify the width and height of the OpenURL action to be smaller than the 3D window, the resulting 2D browser window sits in the lower right corner of the 3D viewer.

Specific properties of OpenURL

• Target URL
  The URL of the page you would like to display
• X Overlay % or width
  Default is 100, or 100% of the width of the 3D viewer window. You can change this percentage, however don't make it bigger than 100 or make it too small - if you can't see the "back to 3D" button on the 2D browser window when it's open, you can't close the window! If you want to use pixels to measure the width (instead of a percentage), enter the width in pixels and change the Fixed Size property to "Yes - pixels specified".
• Y Overlay % or height
  Default is 100, or 100% of the height of the 3D viewer window. You can change this percentage, however don't make it bigger than 100 or make it too small - if you can't see the "back to 3D" button on the 2D browser window when it's open, you can't close the window! If you want to use pixels to measure the width (instead of a percentage), enter the height in pixels and change the Fixed Size property to "Yes - pixels specified".
• Has Toolbar
  Set this to false if you don't want a toolbar to appear on the 2D browser window. If you do this however, the user can't close the 2D window.
• Fixed Size
  The default is false, which means that whatever numbers you enter in the X Overlay and Y Overlay properties are percentages of the 3D viewing window.
If you want to specify pixels for the width and height of the 2D browser window, set this property to true (choose "Yes - pixels specified") and use number of pixels for the width (X Overlay) and height (Y Overlay).

VideoControl

These controls are used with a VideoWall that will play an .asf (video) file on a rect. The VideoControl actions (one for on, one for off) must be attached to the rect that will have the video on it. For an example, see the TV above the counter in the Burkittsville Diner (BlairWitch World).

Specific properties of VideoControl

• 1=Play, 2=Stop
  For a control that starts the video, set this property to 1. For a control that stops the video, set this property to 2.
• Repeat count
  Used when the VideoControl is set to "Play". Set the Repeat count to -1 for an infinite loop or an integer to designate the number of times the video repeats.

NotifyScript

This action only used in Worlds.com produced worlds.

CameraHeight

When triggered, the Camera Height action causes the camera of the user to change to the specified height. If the user is in a third person mode (shoulder, overhead, etc.) the camera changes relative to it's current height and angle.

Specific properties of CameraHeight

• New Eye Height
  When the Camera Height action is triggered, this will be the new height of the camera (the avatar's eye height).

Adding a Behavior

To add an item from the Behaviors Library, follow these steps:

1. Currently most the Behaviors are actually sensors that you use to trigger actions (see steps below). There are a few Behaviors that actually effect an object - check the description of individual behaviors in the Behaviors Catalog to see what types of objects to apply them to.
2. Click the Behaviors tab in the libraries section of WorldsShaper to see the catalog of Behaviors.
3. In the library, click on the behavior you want, holding down the mouse button, and drag it to the Event Handler property listed under the object that you want to hold the behavior. Release the mouse button. The behavior you selected is now attached to the object.
4. If you would like to give your behavior a distinctive name (and this is a good idea if you intend to have several behaviors throughout your world), double-click on Name in the Properties Box and enter a new name in the Edit Name box. Click OK.
5. Check the description of individual behaviors in the Behaviors Catalog to see how to set a particular behavior's properties.

   Adding a Sensor

   Anytime you add an Action to a room, you will need a Sensor (trigger) to initiate the Action. Below are the steps for adding a Sensor.

   1. Click the Behaviors tab in the libraries section of WorldsShaper to see which sensor you want to add.
   2. In the Behaviors Library, click on the sensor you want, holding down the mouse button, and drag it to the Event Handler property listed under the object that you want to hold the sensor. Release the mouse button. The sensor you selected is now attached to the object.
   3. If you would like to give your sensor a distinctive name (and this is a good idea if you intend to have several sensors throughout your world), double-click on Name in the Properties Box and enter a new name in the Edit Name box. Click OK.
   4. In the Hierarchy Tree, click on the triangle to the left of the Sensor to reveal the Targets property.
   5. Click on Targets to select it.
   6. Click the Add button to the right of the Properties Box. A window comes up with a list of all the actions you have in your world.
   7. Select which action you would like this sensor to trigger, and click OK. The action is now listed beneath the Sensor's Targets in the Hierarchy Tree.

Behaviors Catalog

Click Sensor

A Click Sensor triggers its target whenever the user clicks anywhere on the object's bounding box. There are several parameters you can adjust in addition to the name: Left Button, Right Button, Center Button and Wait for Upclick. Setting any of the first three to True enables that type of mouse-click to trigger the target action. If you set multiple buttons to True, the relationship is an OR relationship, as in either the left or right button could trigger the action, does not require both to be pressed together. Wait for Upclick won't perform the target action until the depressed mouse button is released (applies to any enabled mouse button).

Click sensor limitations and considerations

• If an object has been declared to be Invisible, you cannot click it, so an invisible object 's click sensor will be inactive until that object becomes visible again.
• Note that a lot of mouse-handling information is affected by an individual's Windows setup. If there's too much time between downclick and upclick, WorldsShaper won't even register the upclick, so use Wait for Upclick=True with caution.
• If you're actively building a world, right-clicking an object will always bring up the properties box, in addition to whatever click sensor activity you may have assigned. This limits the usefulness of right-click triggering until you have disabled WorldsShaper functionality.
• You can left-click through portals, but you can't right-click through them, because you will be selecting the portal and opening its Properties box.
• Many objects have bounding boxes that are shaped differently than you might expect, and it is the bounding box that detects being clicked. The bounding box can be viewed when you right-click an object; it's the thin white rectangle that appears around the object. In particular, Shapes have bounding boxes that can extend well out from the visible portion of the object.

Bump

Bump triggers its target action whenever the user bumps into that object. The definition of what it means to be bumped for each object is handled by its bump calculator. For a Rect like a wall, that pretty much corresponds to how the bounding box appears when you right-click it. For a Shape, it's an approximate and slightly larger box that goes completely around the Shape and always faces your avatar as a perpendicular vertical plane.

For almost all objects except a Portal, the bump calculator also performs collision detection, meaning that you can bump into that object but you cannot penetrate it. Bump calculation only affects the relationship between your avatar and objects, not objects and other objects. You can superimpose two objects when you're building them and neither one will care. You can turn off all collision detection and bumpability in an object, and that will enable you to walk right through it, but it will also disable any Bump sensor that object may contain.

Portals do bump calculation, but in a different way. If you bump (pass through) a portal, all sorts of things go on in the background where WorldsShaper removes your avatar from the room you came from and adds it to the new room. This happens by default, and you don't even see a Bump trigger inside a portal that's involved in making this happen. But a portal is unique in that it registers a Bump event yet still allows an avatar to walk through it. You can use this feature to your advantage by adding a Bump sensor to the portal and using portals as invisible "trip-wire" triggers. See the section on using a Portal as an invisible but bumpable trigger.

Bump limitations and considerations

• Note that if you pass through a Rect from its non-drawing side, you will not produce a Bump event.
• If you bash into a wall, there is no built-in rebound. If your avatar is stuck to a wall that has a Bump trigger, that wall will continue to send Bump events each frame until you back away from the wall.
• As with the Click sensor, the area that produces a Bump event from a Shape can often be much larger than the Shape appears to be.
• Bump events are actually caused by the intersection of your avatar's bump calculator with any other object's bump calculator. Your own avatar has a box-shaped bump calculator much like a Shape does. In the vertical (z) direction, with a default avatar and the default camera height of 120, your avatar will produce Bump events in objects above z=30 and below z=140. Objects less than 30 in height don't register bump events because otherwise you couldn't properly use stairs. Objects whose bottoms are above z = 140 are considered to be "on the ceiling" and don't impede your forward progress. Your default avatar is considered to be approximately 70 WorldsShaper units wide and deep, though you can sometimes squeeze through gaps as small as 60 wide depending on your facing relative to blocking objects.
• The above does not hold true for portals. You do not trigger a portal Bump event or make it swap you from one room to the next, until your avatar's center intersects the portal plane.

Using a portal as an invisible but bumpable trigger

The Bump trigger only works when the object is bumpable, and when you make something unbumpable such that you can pass right through it, the Bump sensor no longer registers a BumpEvent and the trigger does nothing!

There's a way around this, particularly for triggering doors so that they open while still in your viewpoint instead of slamming in your face. The only objects that will register a Bump event and still allow people to pass through are Portals. Portals have two other important advantages as trigger objects. They are unidirectional, so you can set up pairs of portals to trigger different actions on the way in or out of a room. They can also be set to invisible, so until you select them you'll never know they are there.

The portals you use as trigger objects don't need to be hooked up to other portals or allow viewpoints into other rooms. In fact, you'll want to leave all these properties empty in most cases, or you'll slow down the framerate trying to reproduce the viewpoint. You're probably going to want an invisible portal in most cases anyway.

Instructions for setting up a trigger portal

For this example, let's assume you've already created a Rectangle doorway object that swings aside when triggered, and reveals a Portal to another room behind it. The swinging motion can be accomplished with a Move action.

1. Navigate through the Hierarchy Tree until you're either in the Contents List or Environments Contents List of your Room. In most cases you should use Environment because the trigger portal will end up being invisible and won't affect draw order.
2. From the Objects Library, click and drag a Portal to the Environment Contents of your Room (in the Hierarchy Tree). Assuming you're facing the door you want to trigger, pick the Portal that's 180 degrees opposite of your camera's viewpoint (e.g. if you're facing "West", choose an "East Portal".
3. Move the portal to the desired location, either by using the Properties Box buttons or by using the Transform property.
4. In the Hierarchy Tree, click the triangle next to the Portal.
5. From the Behaviors Library, click and drag a Bump Sensor to the Event Handlers section listed beneath your Portal in the Hierarchy Tree.
6. Click the triangle next to your newly added BumpSensor, and click on Targets.
7. Click the Add button to the right of the Properties Box, and in the Add to Targets window find and select your door's MoveAction on the list. Click OK.
8. Click your portal in the Hierarchy (or right-click the portal in the 3D window again).
9. Double-click Visible in the Properties Box, and in the Edit box, set to No (False, or Invisible).
10. Make sure you're in Drive mode, and try your new trigger out.

Remember that if you want the door to close properly, you have to put a portal coming the opposite direction or put a sequence together that closes the door after a certain time. For a fully working door that opens and closes from both sides, you'll need 2 pairs of portals, one on each side. One of the pair controls a door's opening action, the other faces 180 degrees opposite in the same spot and controls the door's separately defined closing action. If your door has sound, you can use the same trigger portal to trigger the sound or a sequence containing sounds.

SameRoom

SameRoom will trigger the action as soon as your avatar walks into that room. It will trigger again if you walk out of the room and then back into it. This can be a problem if your SameRoom sensor is setting off something like a Sound or Animate action that are set to loop several times. Nevertheless, SameRoom is a pretty handy sensor.

DifferentRoom

DifferentRoom sends an event whenever your avatar is outside the room that the DifferentRoom sensor is in. Unfortunately, it will check back almost every frame to see if you're in a different room, and if you are in a different room that's still connected by portal to that room then it will send another DifferentRoom event every frame. Not only is this detrimental to performance, it's also not very useful. Ignore this sensor for now until we refine it, unless you can come up with some use we haven't thought of.

Startup

Startup sends an event whenever the .world file is first loaded. Unlike the SameRoom sensor, this means it will trigger once and never again, until you quit the program entirely and reload. It's an ideal trigger for things that you will want to be infinitely looping anyways, for example if you have an animation of a fountain that you want to be running for the duration of a user's stay in the world.

Proximity

Proximity sends an event whenever the user gets within a certain distance from the object. The Double Doorway and Animating Door objects have Proximity sensors attached to them that trigger the doors to open when a user gets a certain distance from them, and to close when a user walks away from them. Unfortunately, their seem to be some problems when adding a Proximity sensor to any other object, and this sensor is under development.

Spin

Adding a Spin behavior to an object immediately sets the object to spinning (you don't need a sensor to trigger it). NOTE: If you decide to stop the spin, the object will stop wherever it is in the cycle, so it's very difficult if not impossible to return the object to its beginning position. You can alter the Cycle Time (the higher the number, the slower the spin) and the Axis on which the object will spin. If you change Enabled to false, the object will stop spinning wherever it is in the cycle.

Post-Spin

Adding a Post-Spin behavior to an object immediately sets the object to spinning (you don't need a sensor to trigger it). NOTE: If you decide to stop the spin, the object will stop wherever it is in the cycle, so it's very difficult if not impossible to return the object to its beginning position. You can alter the Cycle Time (the higher the number, the slower the spin), the Center, and the Axis on which the object will spin. If you change Enabled to false, the object will stop spinning wherever it is in the cycle.

Velocity

Under development.

BuildStairs

A BuildStairs behavior is a onetime behavior that you attach to a portal in order to build a set of stairs. Once the stairs are built, the BuildStairs behavior disappears.

NOTE: There's currently a bug with BuildStairs that only allows you to build stairs in the UP direction (see Total Rise below). Also, if you build the stairs too steep, or build the risers too high, when the stairs are built you won't be able to climb the stairs.

Texturing the Stairs

You can specify textures for your stairs before they are even built. The good thing about this is that you don't have to add textures to all the risers and treads individually once the stairs are built. The bad thing is that you can't specify the tiling - the tiling is "built in". You can change the tiling once the stairs are built, but you're still stuck changing each riser and tread individually.

If you click on the triangle to the left of the BuildStairs behavior that you just added to a portal (under Event Handlers), you'll notice several Material listings: Ceiling, Door Post, Left Wall, Right Wall, Lintel, Riser, and Tread. Add textures as you would for normal rects. The stairs will be built with the textures you designated. Once the stairs are built (a stair "room" is added to the Rooms list), you'll be able to change any texture or tiling on the rects in that room.

Specific properties of BuildStairs

• Build Now?
  Set this to true when all the other properties have been set, you've designated the textures (see above), and you want the stairs to be built. Once you've set this to true and clicked OK, there's no going back! Your staircase will be built.
• Staircase Name
  The BuildStairs behavior actually builds a room that has a portal at each end and stairs in the middle. The new staircase will be listed under Rooms in the Hierarchy Tree. Give it a distinct name if you want to.
• Number of Steps
  Specify the number of steps your staircase will have. The default is 10.
• Portal-to-Portal Distance
  Specify the distance from the bottom of the stairs to the top of the stairs. The default is 1000.
• Stairwell Width
  How wide do you want the stairwell. If you specify a width that is greater than the width of the portals, BuildStairs will add walls on flanking the portals on either side.
• Portal Width
  Since BuildStairs creates a room, the room will have portals on either end of the stairs. Specify a Width for the portals. It should be the same width as the portal that has the BuildStairs behavior attached to it.
• Portal Height
  Specify a Height for the portals. It should be the same width as the portal that has the BuildStairs behavior attached to it.
• Total Rise
  Specify the rise or "steepness" of the stairs.
• Lintel Height
  Specify the Lintel Height (the height of the rect above the bottom portal. This will determine the height of the stairwell ceiling).

BuildRamp

The BuildRamp behavior is just like the BuildStairs behavior except you get a ramp instead of stairs.

NOTE: There's currently a bug with BuildRamp (different than the BuildStairs bug). Once the Ramp is built, you'll notice you can't get through the portal to get to the ramp. You'll have to look for the new Ramp room that has been added to the Rooms in the Hierarchy Tree. Go to the Ramp room's Environment Contents and look for the 2 Polygons listed there. Click on each one individually and change their Bumpable property to false. Now you can enter the Ramp room and go up (or down) the ramp.

Specific properties of BuildRamp

Most of the properties for BuildRamp are the same as BuildStairs (see above). However with the BuildRamp, you are able to designate the tiling for the textures before the ramp gets built. If you want to add textures to the ramp prior to building it (see Texturing the Stairs above), you can specify Ceiling Tile Size, Floor Tile Size, Right Wall Tile Size, and Left Wall Tile Size in the BuildRamp properties.

Move & Roll

Under development.

Adding a Texture

Currently the Textures Library has just a few simple textures and is not generally used when building new worlds.

To add an item from the Textures Library, follow these steps:

1. Items in the Textures Library can be added to two places in the Hierarchy:
   • Rect Material Texture property (walls, floors and ceilings)
   • Portal Material Texture property (walls, floors and ceilings)
2. Click the Textures tab in the libraries section of WorldsShaper to see the catalog of Textures.
3. In the library, click on the texture you want, holding down the mouse button, and drag it to the rect or portal that you want. Release the mouse button. The texture you selected is applied to the object. The default tiling is 0,0 which stretches the texture once over the object. To change the tile size, go the the Material Properties of the rect/portal and change Tile Size.

Attributes Catalog

The shared state Attributes are currently under development, and shared state has been disabled.

Creating Mirrors and Magnifying Mirrors

Mirrors are very easy to create, they are simply Portals that have been connected to themselves rather than to another Portal. To create a mirror, follow these steps:

1. Add a Portal at the location where you want the mirror.
2. Resize it to the size you want the mirror.
3. Under the Portal Properties, change Destination Room Name to the name of the room the mirror is in.
4. Under the Portal Properties, change Destination Portal Name to the name of the portal itself. The portal turns into a mirror.
5. You'll notice, however, that the room and objects are not truly "mirrored". Under Portal Properties, double-click Mirrored and select the "mirrored" option to designate this property as true.
6. VERY IMPORTANT - if you leave the mirror as is, you can walk through the mirror with some very strange results - you'll end up walking on the ceiling of the next room, the right arrow key will make you turn left, the left arrow key will make you turn right, and you won't be able to walk out of this upsidedown room! Assuming you don't want this effect, you'll need to do the following steps:
1. Make the portal unbumpable (make the Bumpable property = false).
2. Place a rect of the same size directly over the portal.
3. Either make the rect's Visible property = false, or add a "frame" by adding a texture to the rect that has transparency in the center.

NOTE: It's not a good idea to put mirrors facing each other. Although possible, it's not advised since this will slow your world down considerably due to the number of "reflections" WorldsPlayer will be forced to render.

Creating a Wear Wall

The interactive walls in the Gallery of Metamorphics contain a "Wear Wall" which allows small samples of avatar textures/heads/faces to be displayed for the user to choose from. The following instructions are specifically for the walls in the Gallery of Metamorphics (use these for reference), but they can be adapted as far as size and placement.

These instructions are based on having the following 6 textures:

colors1.mov - 128x128 This file contains six frames and is one of the textures used for the "title" above the Wear Wall. The frames are: head size skin color hair color shirt color coat color dress color		colors2.mov - 128x128 This file contains five frames and is one of the textures used for the "title" above the Wear Wall. The frames are: pants color left glove color right glove color left shoe color right shoe color
faces.mov - 128x128 This file contains six frames and is one of the textures used for the "title" above the Wear Wall. The frames are: male faces female faces animal faces winged faces surreal faces cartoon faces		heads.mov - 128x128 This file contains six frames and is one of the textures used for the "title" above the Wear Wall. The frames are: male heads female heads animal heads winged heads surreal heads cartoon heads
vancat5t.mov - 256x256 This is a "hi-res" texture that is actually broken down into four frames that are 128x128 each. This texture contains the top buttons to the left of the Wear Wall.		vancat5b.mov - 256x256 This is a "hi-res" texture that is actually broken down into four frames that are 128x128 each. This texture contains the bottom buttons to the left of the Wear Wall.

1. From the Objects Library, add a Wear Wall to your room. Make it 125w x 250h, and set its Color to 255,252,235 (under Material Properties). NOTE: a Wear Wall can be any size. The size of the textures (or heads or faces) that display on the wall will depend on 1.) the size of the Wear Wall and 2.) the number of textures/heads/faces that have to fit on the wall.
2. Add a SetString Action to the Wear Wall. Name it SetStringAction1.
3. For the titles above the Wear Wall, create a rect above the Wear Wall that is 125w x 25h. Set the tiling on this rect to 0,125 and the tile origin to 0,-25.
4. Add an Animate Action to this top rect, naming it AnimateAction1. Set the AnimateAction's Cycle Time to 0, and its Cycles to 1.
5. Add 3 rects to the left of the Wear Wall, one at the top that is 125x125, another 125x125 rect below that, and a 125x25 rect on the bottom (make the color of this bottom one 160,181,255).
6. Add the vancat5t.mov texture to the top rect on the left.
7. Add the vancat5b.mov texture to the middle rect on the left.
8. Add a WearAction to the top rect, naming it WearAction1. Set the WearAction's Limb to Q.
9. Add a ClickSensor to the top rect (vancat5t), and in its targets add WearAction1, SetStringAction1, and AnimateAction1. Set the ClickSensor's config file to "Top.clk", and store the Top.clk file in the same directory as your .world file (see below for more info on .clk files).
10. Add a ClickSensor to the middle rect (vancat5b) and in its targets add SetStringAction1 and AnimateAction1. Set the ClickSensor's config file to "Bottom.clk" and store the Bottom.clk file (see below) in the same directory as your .world file.

.CLK Files

Within your WorldsShaper directory, look in the AvatarGallery folder (if you have that world installed) to see the Top.clk and Bottom.clk files. Open them in Notepad and you'll see that there are a list of coordinates for each of the "buttons" on the textures to the left of the Wear Wall. Each button has textures, colors, or heads assigned to it, and each button calls up a different "title" above the Wear Wall (see the Frame List within the .clk files). Below is a more detailed description of each line.

We'll use Top.clk from the AvatarGallery folder for reference:

43 256 256
Line1: The top three numbers in the file are the number of lines in the file (43) and the size of the texture this file references (256 256). Top.clk references vancat5t.mov

Each button on vancat5t.mov uses three lines in the .clk file:

103 202 65 21 SetString "Property Name" Limb "Set To" H
Line 2: The four numbers represent the coordinates of the button on vancat5t. The lower left corner of the vancat5t texture is 0,0, and 103 202 is the x,y coordinate of the lower left corner of the "Male Heads" button. Limb "Set To" H tells the program that the head (H) texture will change if this button is clicked.

103 202 65 21 SetString "Property Name" "Tile List" "Set To" "axel cassius charlie ..."
Line 3: Here you list the "Tile List", that is, the textures you want to display when a user clicks on this button. In this instance the list of textures contains axel cassius charlie dude guru etc. which tells the Wear Wall to display these "head" files when a user clicks on the "Male Heads" button.

103 202 65 21 Animate "Frame List" heads1s*.mov
Line 4: This line tells the program which title to display above the Wear Wall (colors1, colors2, head, or faces.mov). In this instance, heads1s*.mov is listed, which means "display the first frame of the heads.mov file". If you want a different frame to display, replace the 1 within heads1s*.mov with whatever frame number you desire.

Lines 5,6,7: These next three lines are for the Male Faces button. You'll notice that the coordinates change, as do the Limb (E for "face"), and the list of frames (ztx cassius charlie dude etc.)

12 20 23 31 Wear Value qqq
Line 37: At the bottom of this .clk file, you'll notice that the last 7 lines are different than the others. These refer to the "Head Size" buttons at the bottom of vancat5t.mov. The first four numbers are again the coordinates of that particular head size button. Then the Wear Value of qqq tells the program to shrink the avatar's head to that size. 000 is the "normal" head size (see Line 40).

Making Your World Multiuser

You most likely will want to make your world Multiuser so that people can see each other when they're online in your world. To make your world multiuser, follow these steps:

1. Scroll up to the very top of the Hierarchy Tree for your world.
2. Click on the world name at the top to bring up the World Properties in the Properties Box.
3. Double-click Multiuser under World Properties.
4. Select "yes" in the Edit Multiuser box and click OK.
5. Save your world.

How to Register Your World

1. Ensure you have enough web space available to you (through your ISP) to hold all of the files associated with your world.
2. Verify the links to textures and shapes. Serving your new world is very much like serving a web page. Your .world file is like the html file that points to various images, except it instead points to 3D textures and shapes. As with an html file, you should go back and make sure you aren't linking to objects directly on your hard drive. Within your world, all of the URL's to textures and objects should begin with the "rel:" prefix (in most cases this is added to the URL for you by WorldsShaper). For example:
   
   CORRECT texture URL:
   
   rel:file:c:/WorldsShaper/MyWorld/textures/grass.gif
   
   INCORRECT texture URL:
   
   file:c:/WorldsShaper/MyWorld/textures/grass.gif
   
   This is the same as absolute and relative URL's on a web page and carries the same problems... if your links point directly to your hard drive instead of a relative path from the .world file, your world won't work for anybody but you.
3. Verify the proper case on all uploaded files. The filenames of any images or shapes in your world will become case-sensitive when uploaded to a server.
4. Ensure that you haven't compressed any resources into content.zip files. While this will work locally on your machine, WorldsPlayer can't decompress ZIP files on web servers. If you don't know what that means, pretend step 4 didn't exist.
5. FTP all of the files associated with your world to your web space. Be sure to preserve whatever directory structure your world had. For example, if your .world file is within your WorldsShaper directory on your hard drive, like this:
   
   
   
   then keep that same file structure when you upload all of your files.
6. Determine the URL to your .world file; this will be used in a creating a WorldsMark to your world and telling other users how to access your world. Again, it's just like an html file. For example:
   
   http://www.myisp.net/JoesAccount/MyWorld/Joes.world
   
   
7. Create a WorldsMark for your new world by clicking on WorldsMark on the WorldsPlayer interface. Choose Add new WorldsMark.... In the Add WorldsMark box, type in the name of your world, and in the URL section put your world's URL:
   
   http://www.myisp.net/JoesAccount/MyWorld/Joes.world
   
   Then click Add....
   
   
8. IMPORTANT NOTE: You must be off-line in Worlds (not signed in) to do this step. Once your world has been registered, you will be able to access it while signed-in.
   
   Click on WorldsMark again, and use the WorldsMark you just created to teleport to your world. You should see your world form around you as its resources are downloaded, starting in the room your avatar is in. Any textures or shapes that don't come in may be absolute links to your hard drive... go back and check for that.
9. Register your world by going to http://dev.worlds.net/cgi-bin/shaper/submit_world.pl. Fill out the form, including your WorldShaper account number. At the bottom of the form, you can choose to have your world published on our User Created Worlds page, or you can have your world be unpublished (your world will still be registered, it just won't be published on our web page). Click on the Submit button. It will take a few days for the authorization process, and Worlds will let you know via email when your world has been registered.
10. Give the URL for your world to all your friends, and tell them to make a WorldsMark with it! NOTE: The URL to your world will not work for others until it has been registered with Worlds, unless they wish to view your world while off-line.