DeltaWiki - User contributions [en]

DeltaWorlds (software)

2026-02-09T14:59:54Z

Xan:

[[Image:Browser_screenshot.jpg|400px|thumb|Active Worlds Software]]

'''Delta Worlds''', home of [[AW]] (the Internet's largest virtual world) is a software package created for preserving Active Worlds history and carrying on its legacy.

== Current Version ==
*Browser: ''{{ver}}''
*World Server: ''{{ver worldserv}}''
*SDK: ''{{ver sdk}}'' 
==Version Update Logs==
*[[Early Changelists]]
*[[New Features in 6.2 | 6.2]]
*[[New Features in 5.1 | 5.1]]
*[[New Features in 3.6 Classic | 3.6 Classic]]

DeltaWorlds (software)

2026-02-09T14:59:32Z

Xan:

[[Image:Browser_screenshot.jpg|400px|thumb|Active Worlds Software]]

'''Delta Worlds''', home of [[AW]] (the Internet's largest virtual world) is a software package created for preserving Active Worlds history and carrying on its legacy.

== Current Version ==
*Browser: ''{{ver}}''
*World Server: ''{{ver worldserv}}''
*SDK: ''{{ver sdk}}''

== Classic Version ==
*Browser: ''{{ver classic}}''
*World Server: ''{{ver worldservclassic}}''
*SDK: ''{{ver sdkclassic}}''

==Version Update Logs==
*[[Early Changelists]]
*[[New Features in 6.2 | 6.2]]
*[[New Features in 5.1 | 5.1]]
*[[New Features in 3.6 Classic | 3.6 Classic]]

Main Page

2026-02-09T14:55:52Z

Xan:

{| style="padding:15px; background:#E8E8E8; width:100%; -moz-border-radius:50px; -webkit-border-radius:23px; border-radius:23px;margin-bottom:0px"
|-valign="top"
| style="padding-right:12px" align="center" valign="middle"|[[Image:Worlds_small.png|DW::Universes]]
| style="background:#FFFFFF; vertical-align: middle; padding:10px; width:100%; -moz-border-radius:23px; -webkit-border-radius:23px; border-radius:23px;" |
<big>
Welcome to the '''DeltaWiki'''
 
The virtual encyclopaedia of [[DeltaWorlds (software)|DeltaWorlds]] and the respective 3D universes.
</big>

== Current Version ==
*Browser: ''{{ver}}''
*World Server: ''{{ver worldserv}}''
*SDK: ''{{ver sdk}}''
== Linux Client ==
*Browser: 6.2 (Please use Wine or Proton)

|}
{| style="padding:15px; background:#E8E8E8; width:100%; -moz-border-radius:50px; -webkit-border-radius:23px; border-radius:23px;margin-bottom:0px"
|-valign="top"
| style="padding-right:12px" align="center" valign="middle"|
<big>
'''DeltaWorlds''' , short ''DW'', Home of the 3D Internet, the 3D virtual reality platform with an immersive experience - log in to explore 3D virtual environments that other users have built. Users chat, talk and share or [[Building | build structures]] themselves from a selection of objects in private world or publicly owned land of the Public Free Universe.
 
The intuitive building system allows even the most inexperienced users to pick-up and begin building their own environments right away.
</big>
 
'''DW::Browser''', [https://www.deltaworlds.com/downloads/ available for free download], also has [[URL | web browsing]] capabilities, voice chat, [[media | streaming media]] and instant messaging which allows users to connect, explore and [[Building | create]] more in-depth and interactive environments.
 
|}

[[Category:DeltaWiki]]

File:Cloth01.jpg

2026-02-09T14:52:02Z

Xan:

File:Cloth02.jpg

2026-02-09T14:51:26Z

Xan:

Cloth

2026-02-09T14:50:53Z

Xan: Created page with "{{feature|1194|5.1}} Category:Building Category:5.1 The '''cloth''' object type allows for realistic cloth-based objects, like flags waving in the wind or making an deformable object. * Cloth is a quiete complex topic. Before starting to build, you may want to read at least the tips below. Simulating cloth can be a quite stressing task for your PC. Avoiding a few things and always attempting to build for best performance will help you to create fascinating..."

{{feature|1194|5.1}}
[[Category:Building]]
[[Category:5.1]]

The '''cloth''' object type allows for realistic cloth-based objects, like flags waving in the wind or making an deformable object.
 

* Cloth is a quiete complex topic. Before starting to build, you may want to read at least the tips below. Simulating cloth can be a quite stressing task for your PC. Avoiding a few things and always attempting to build for best performance will help you to create fascinating content in your world using cloth, fabric and deformable objects.
 
''Note, only described features are currently supported. Some more features are already found with cloth properties, that are either greyed out or disabled for now.''
 

==Basic Principles of Cloth==
''(Source: NVIDIA® PhysX® SDK Documentation)''

[[Image:cloth01.jpg|right|200 px|thumb|]]
The cloth feature of the NVIDIA® PhysX® SDK allows for simulation of items made from cloth, such as flags, clothing, etc. This is accomplished by providing a mesh that is used to define a set of particles (vertices). The topology of the mesh allows the SDK to construct constraints between the particles that mimic how cloth can bend and stretch. In addition, cloth particles can be pinned to shapes and global positions, such as attaching a flag to a pole.

[[Image:cloth02.jpg|left|200 px|thumb|]]
 
There are two main types of cloth constraints:

* Stretching - applied to maintain distance between each particle that is connected by an edge in a cloth mesh. The strength of this constraint is assigned using the SDK; specifying a small stretching constraint factor allows the particles to move apart more easily and gives the impression of more stretchy cloth, such as lycra. Specifying a larger constraint factor makes the cloth stiffer, like denim.

* Bending - applied to maintain the angle along an edge in a cloth mesh, either by constraining the angle directly or by constraining the distance between the pair of particles on either side of the edge (see the diagram below). An example of a material that would use a low bending constraint for simulation is cotton, while a substance such as paper or cardboard would use a high bending constraint.

 
{{TOCright}}

==Cloth Attributes==
''(in alphabetical order)''

===Attachment Response Coefficient===

This coefficient controls the strength of the momentum transfer between a cloth and the shape(s) it is attached to. A large attachment response coefficient will cause the cloth to pull/push the body more easily and a lower value will mean the rigid body is more difficult to move.

Defines a factor for the impulse transfer from cloth to attached rigid bodies.
Only has an effect if the attachment response is checkmarked and the cloth is attached to a rigid body.

Default: 0.5
Range: [0,1]

===Attachment Tear Factor===

If the Attachment Tearable is checkmarked, this variable defines the elongation factor that causes the attachment to tear.

Must be larger than 1.
Only has an effect if the attachment tearable is checkmarked and the cloth is attached to a rigid body.

Default: 1.0
Range: [1,1000]

===Bending Stiffness===

Bending stiffness of the cloth in the range 0 to 1.

Default: 1.0
Range: [0,1]

===Collision Response Coefficient===

The collision response coefficient is similar to the attachment response coefficient, except instead of applying forces due to the attachment, it applies forces due to collision.

Defines a factor for the impulse transfer from cloth to colliding rigid bodies.
Only has an effect if Collision Response is checkmarked.

Default: 0.5
Range: [0,1000]

===Compression Limit===

Defines a factor up to which the cloth is weak under compression.
This factor is the lower part of a range [limit, 1]. Whenever an edge is compressed to something between [limit, 1] * original length, the stretchingStiffness is multiplied with the compressionStiffness.

Since the compressionStiffness is smaller or equal to 1, this will always define a range where the cloth reacts more softly to compressed edges.
This feature is useful to generate small wrinkles features on the cloth mesh outside the SDK.

Default: 1.0
Range: [0, 1]

===Compression Stiffness===

Defines the stiffness of the cloth under compression.
This stiffness scales the Stretching Stiffness in the range defined by Compression Limit.

Default: 1.0
Range: [0, 1]

===Damping Coefficient===

Controls how much damping is applied to the motion of cloth particles. Damping is always performed for the velocity of each individual particle. If Global Pos Damping is checkmarked, the global rigid body modes (translation and rotation) are exempted from damping. If not, the global translation and rotation of the cloth are damped, same as the internal movement of the cloth.

Spring damping of the cloth in the range 0 to 1.
Useful to reduce CPU/GPU load, and for putting cloth asleep.

Default: 0.1
Range: [0,1]

===Density===

Density indirectly specifies the mass of the cloth particles. The mass of a particle is calculated as the sum of the following equation (for triangles sharing a point):

1/3 * triangleArea * density

Default: 1.0
Range: [0,1000]

===Friction===

Friction coefficient in the range 0 to 1.
Defines the damping of the velocities of cloth particles that are in contact.

Default: 0.5
Range: [0,1]

===Hard Stretch Limitation Factor===

Defines the hard stretch elongation limit.
If Hard Strech Limit is checkmarked, the solver pulls vertices with a maxDistance greater zero towards vertices with maxDistance zero (attached). This reduces the stretchiness even for low solver iteration counts. The process is non-physical and can yield small ghost forces. The Hard Stretch Limitation Factor defines by what factor the cloth is allowed to stretch.

Default: 1.0
Range: [0,1000]

===Min Adhere Velocity===

If Enable Adhere is checkmarked, the cloth moves partially in the frame of the attached actor.
This feature is useful when the cloth is attached to a fast moving character. In that case the cloth adheres to the shape it is attached to while only velocities below the parameter Min Adhere Velocity are used for secondary effects.

Default: 1.0
Range: [0,1000]

===Pressure===

If pressure is set to another value than 0, this variable defines the volume of air inside the mesh as volume = pressure * restVolume.
For pressure < 1 the mesh contracts w.r.t. the rest shape For pressure > 1 the mesh expands w.r.t. the rest shape

Default: 0.0
Range: [0,10]

===Stretching Stiffness===

Stretching stiffness defines the strength of the constraint along a triangle edge that maintains the distance between the edge end points. A value of one will produce a cloth that is very difficult to stretch, such as denim pants, while a value near zero will produce one that can stretch easily, like nylon stockings (a value too near zero is not recommended for a stable simulation; zero is not allowed).

Stretching stiffness of the cloth in the range 0 to 1.
Note: stretching stiffness must be larger than 0.

Default: 0.5
Range: [0,1]

===Tear Factor===

If tearing is enabled, this variable defines the elongation factor that causes the cloth to tear.
Must be larger than 1.

Default: 2.0
Range: [1,1000]

===Thickness===

Thickness of the cloth. The thickness is usually a fraction of the overall extent of the cloth and should not be set to a value greater than that. A good value is the maximal distance between two adjacent cloth particles in their rest pose. Visual artifacts or collision problems may appear if the thickness is too small.

Thickness defines the triangle's level of thickness for collision detection, improving its robustness. Setting the thickness very low is not recommended as this will lead to poor collision handling.

Default: 0.5
Range: [0,1]

===Valid Bounds===

By using valid bounds you can specify an axis-aligned bounding volume to which the cloth is restricted. Any part of the cloth that leaves this volume (such as pieces torn off an otherwise attached flag) will be removed from the simulation.

If the bounds are set, this variable defines the volume outside of which cloth particle are automatically removed from the simulation.
The values for x, y, z each define a distance from the current position in world in positive and netagive directions.

Default: 0
Range: [0,1000]

===Wind===

As with external acceleration this applies an acceleration on each vertex. However this acceleration is only applied in the vertex normal direction, i.e. only the component of the external force that lies in the direction of the vertex normal is applied to the vertex. This makes it easy to simulate effects such as wind.

Wind is an acceleration (unit length / s^2) which acts normal to the cloth surface at each vertex.

Default: (0,0,0)

==Tips==

===General tips (basic rules)===

* Do not intersect cloth with static colliders. This causes odd behavior of the cloth and adds lots of CPU/GPU load (10 times more!) onto the PC.
* Look at the yellow bounding box of rigid body objects that you want to collide with cloth or any other rigid body. If the shape matches the size of the bounding box, use primitives like box, sphere or capsule. Do not use cylinder for static shapes. If the shape of the object does not match the bounding box, i.e. the bounding box is much bigger than the object's geometry, use a hull (convex mesh) for dynamic rigid bodies and tree (triangle mesh) for static rigid bodies.
* Models with very irregular order of triangles, as well models with many clumps (submeshes) will not work well for used for cloth objects.
* Geometry with less or equal 3 verticies, or less than 2 triangles will be rejected.

===How to create stiff cloth===

* Use fewer vertices (fewer vertices makes stiffer cloth).
* Use higher iteration counts (associated performance impact).
* Use Ortho Bendning mode (results in stiffer, more realistic cloth bending).

===How to improve cloth performance===

* Use fewer vertices, a lower resolution.
* Use simple bending constraints (Bending Stiffness only and not Ortho Bending).
* Disable cloths that are not relevant using Static (checkmark static).
* Disable tearing for cloths which do not need tearing (uncheck tearing).
* Avoid cloth self collision (uncheck Selfcollision).
* Avoid cloth intersecting with static colliders.

===How to use pressure===

* If the pressure is set to a value less than 1.0 (the default), the pressure will be insufficient to preserve the initial shape of the cloth and it will collapse until it has been compressed enough to have an internal pressure of 1.0.
* If the pressure is set to a value greater than 1.0, the cloth will expand beyond its initial size; how much will depend on the stretching stiffness of the cloth.
* Pressure only works well on closed geometries. If pressure is applied to flat panels or objects like trees, you may experience unexpected events.

Reset

2026-02-09T14:50:02Z

Xan: Created page with "{{TOCright}} {{feature|1255|5.2}} ==Usage== '''reset''' ''physics'' [name=''name''] [''global''] The '''reset''' ''physics'' statement resets all physical objects including cloth-objects of the same builder within visible range. ===name=== The ''name'' optionally specifies objects of the given name to be reset. ===global=== A command with the ''global'' argument appended will cause the triggered command to be sent to all neighbors in view, if enabled with the wor..."

{{TOCright}}
{{feature|1255|5.2}}
==Usage==
'''reset''' ''physics'' [name=''name''] [''global'']

The '''reset''' ''physics'' statement resets all physical objects including cloth-objects of the same builder within visible range.

===name===
The ''[[name]]'' optionally specifies objects of the given name to be reset.

===global===
A command with the ''global'' argument appended will cause the triggered command to be sent to all neighbors in view, if enabled with the world feature settings.

==Notes==
* This command has no effect when used with ''create'', ''adone'' or similar triggers.
* The command can not be used to reset another builder's physics scene.

==See also==
* [[Physics]]

{{Build}}
[[Category:Building commands]]
[[Category:Physics]]
[[Category:5.2]]

Name

2026-02-09T14:49:23Z

Xan: Created page with "{{feature|N/A|N/A}} The '''name''' command assigns a name to an object so that it may be referenced by an action on another object. This allows the implementation of multi-object behaviors. For example, clicking an object can cause another object to appear or disappear. ==Usage== '''name''' ''name'' ===name=== The ''name'' argument is the only argument required for this command. Names are limited to 15 characters and can only contain alphanumeric and underscore charac..."

{{feature|N/A|N/A}}
The '''name''' command assigns a name to an object so that it may be referenced by an action on another object. This allows the implementation of multi-object behaviors. For example, clicking an object can cause another object to appear or disappear.

==Usage==
'''name''' ''name''

===name===
The ''name'' argument is the only argument required for this command. Names are limited to 15 characters and can only contain alphanumeric and underscore characters.

==Examples==
Object #1:
create name door
Object #2:
[[bump]] [[visible]] door off
Creates an object with the name ''door''. This name is referrable by other objects, such as the second object which hides the named object on bump.

==Notes==
* Multiple objects may have the same name. In this case, any actions applied to a given name will affect all objects within visibility range with that name assigned to them.
* Named objects can only be affected by objects owned by the same citizen or by other tourists.

{{Build}}
[[Category:Building commands]]
[[nl:Commando:Name]]

Say

2026-02-09T14:48:45Z

Xan: Created page with "{{feature|1018|4.2}} The Say command in action. The text printed by the command is shown in baby blue, italic lettering. The '''say''' command allows a line of text to be printed to the Activeworlds chat window. ==Usage== '''say''' [text=]''text'' ===text=== A string value to print into the browser's chat log. ==Examples== activate say "Welcome to Ground Zero!" When the user clicks the object, the text..."

{{feature|1018|4.2}}
[[Image:Say1.jpg|300px|thumb|The Say command in action. The text printed by the command is shown in baby blue, italic lettering.]]

The '''say''' command allows a line of text to be printed to the Activeworlds chat window.

==Usage==
'''say''' [text=]''text''

===text===
A [[Object scripting#String|string]] value to print into the browser's chat log.

==Examples==
[[activate]] say "Welcome to Ground Zero!"
When the user clicks the object, the text Welcome to Ground Zero! will be printed in the chat window.

{{Build}}

[[Category:Building commands]]
[[Category:4.2]]

File:AWR cabin windball.png

2026-02-09T14:47:00Z

Xan:

File:AWR cabin wind.jpg

2026-02-09T14:46:38Z

Xan:

File:Zarco entropy.png

2026-02-09T14:46:23Z

Xan:

File:Zarco chamber.png

2026-02-09T14:46:10Z

Xan:

File:Zarco.png

2026-02-09T14:45:11Z

Xan:

Guide:Physics tricks

2026-02-09T14:44:39Z

Xan: Created page with "Physics can be used for two techniques to enhance interactivity; a [http://en.wikipedia.org/wiki/Random random] generator and to simulate wind dynamics. == Random generator == For this tutorial, I will be making use of a recent creation: Zarco, the coin-operated boy wonder. His function is to provide fortunes to visitors. As the browser does not contain a random command, I use physics (and juju) to randomly decide the fortune. This can be used to pick fortunes,..."

[[Physics]] can be used for two techniques to enhance interactivity; a [http://en.wikipedia.org/wiki/Random random] generator and to simulate wind dynamics.

== Random generator ==
For this tutorial, I will be making use of a recent creation: Zarco, the coin-operated boy wonder. His function is to provide fortunes to visitors. As the [[browser]] does not contain a random command, I use physics (and juju) to randomly decide the fortune. This can be used to pick fortunes, numbers, names or any values and actions you desire (e.g. randomly decided traps)

=== Basic operation ===
[[Image:Zarco.png|frame|center|Zarco in his cabinet, giving out wise directions. Watch him operate on [http://www.youtube.com/watch?v=uEl6hEtfv-k YouTube]]]
Zarco is triggered by a button, which sets of a chain of animate commands. These commands cause a physical ball to spin around in an enclosure of panels with the [[collide]] panel. The ball is then given a "local axis" (ltm) force, pushing it toward a panel. The collided panel then gives its fortune. There are 24 possible fortunes that Zarco may give at any time.

=== Setting up the "picker" ===
A random fortune is given by a spinning <code>nograv</code> ball enclosed in a chamber. First, create the "picker" ball using a small object such as "p1sph0005" (Note: Despite the fact that this object has a bottom-center axis, the physics engine correctly sets its axis to the mesh's center). Give it the following code:

[[create]]
[[name]] rand,
[[colltag]] 10,
[[collider]] nograv;
[[collide]]
[[reset]] physics,
[[addtorque]] 250 20 59

The <code>create</code> trigger sets properties for the ball:
* Its name is "rand", which will allow other objects to modify it
* Its "colltag" is 10; this will be used to allow collision events between it and the fortune panels
* "collider" makes it a physics object. The "nograv" attribute is '''important''' as it makes it float instead of falling.

The <code>collider</code> trigger causes the ball to:
* "reset physics"; when the ball collides with a fortune panel, it will return to its original position
* "addtorque"; this causes the ball to spin wildly after resetting. This gives it some "randomness" to the next choice.

=== Setting up the "fortune panels" ===
[[Image:Zarco chamber.png|frame|center|Zarco's random chamber; this is where the "picker" ball is kept. Watch the picker in action on [http://www.youtube.com/watch?v=OaoBC_tjd0w YouTube]]]
Surrounding the ball is the chamber, which is made up of small panels. In Zarco's case, this chamber is a cube consisting of four panels on each side (using the "a" [[object]] to reduce [[cell space]]). All sides must be enclosed to prevent the ball from flying off into the unknown. Each panel should contain the following code:

[[create]]
[[collider]] static,
[[colltag]] 10;
[[collide]]
[[say]] "Zarco: <MESSAGE>"

The <code>create</code> trigger sets properties for the panel:
* "collider" makes it a physics object. The "static" attribute is '''important''' as it makes the panel unmovable.
* Its "colltag" is 10; this will be used to allow collision events between it and the picker ball

At this point, the code after the <code>collider</code> trigger is up to you; you can make an object nearby [[move]], play a [[sound]], start a [[media]], anything. In Zarco's case, all panels use the same command:
* "say" causes the object to say something in chat. In this case, all messages start with "Zarco: " with an invisible tab character between his name and the message; this makes him look like a nearby person. Example fortunes that Zarco say are:
** <code>collide say "Zarco: Probably."</code>
** <code>collide say "Zarco: Reception is fuzzy; ask again later"</code>
** <code>collide say "Zarco: Keep taking left turns and you will find out"</code>

=== Setting up this button ===
To invoke the randomizer and spit out a random fortune, a button (or bump panel) is required. Zarco's button uses a complex [[astart]] mechanism, but I will explain a more simple method. With this code, a second or two after the button is clicked, a random action should be performed. Create a button with the following code:

[[activate]]
[[addtorque]] 9 -7 8 name=rand,
[[addforce]] 5 3 1 ltm name=rand;

The <code>activate</code> trigger causes the button to do the following when clicked:
* "addtorque" causes the picker ball to spin. The numbers are not significant; you should change these to random values. This is the fundamental "random" functionality.
* "addforce" is what causes the ball to move into a fortune panel, eventually colliding with it.

=== Entropy and why Zarco is not actually random ===
This trick will never be truly random; this and other random generation techniques used by computers are always "psuedo-random". Especially with the technique in this tutorial, it can be predictable. For example, Zarco's first fortune would always be "Oh... I've been meaning to ask you about that...". This is because (using the above code example) Zarco will always start with a spin of "9 -7 8".

To make Zarco more random, something called "entropy" needs to be added. Entropy is what makes real-world random number generators more "random"; this entropy can be readings from the atmosphere, monitoring static on radio waves or even monitoring cosmic background radiation. While Active Worlds does not yet have the ability to read from cosmic background radiation, it is still possible to add "entropy" to the randomizer.

[[Image:Zarco entropy.png|frame|center|A floorboard that provides entropy to the randomizer for those who approach Zarco.]]

To do this, I have added "bump" triggers on floor objects around Zarco that addtorque to the picker ball. For example, this code is on the wooden floorboards in front of Zarco:

[[bump]] [[addtorque]] 10 2 18 name=rand global

The <code>bump</code> trigger causes the random picker ball to spin around when the floor is walked on. Again, these numbers are insignificant; you should change them to different numbers for each bump trigger. An '''important''' attribute of this command is "global"; this causes the ball to spin for others nearby, giving them additional entropy.

This way, when a visitor approaches Zarco, he ideally should get a different first answer than others. Other triggers can be combined too, such as [[enter zone]] or VRT timers using the [[at]] trigger to provide entropy every minute.

=== Error handling ===
One problem with this trick is that it requires physics. This can present a problem when visitors have physics disabled; triggering Zarco would make nothing happen (or in the AWReunion version's case, it simply says "Zarco whirrs to life in his machine..."). To prevent confusion, error handling should be implemented. Change the button code to the following:

:''Note: Although I use a legacy animate timer here, you can also use the [[timer]] command and [[at]]. Personal experience has shown me that [[timer]] is an unpredictable command, however. YMMV.''
[[create]]
[[name]] zerror,
[[animate]] me . 1 1 5000;
[[activate]]
[[addtorque]] 9 -7 8 name=rand,
[[addforce]] 5 3 1 ltm name=rand,
[[astart]];
[[adone]]
[[say]] "Zarco is unable to answer as he requires physics to be enabled"

The <code>create</code> trigger sets properties for the button:
* Its name is "zerror", which will allow the random picker to stop the "error timer"
* The animate command gives it a time out of 5000 milliseconds (5 seconds); this should be more than the time it takes for the picker ball to pick a fortune.

The <code>activate</code> trigger causes a new thing to happen when clicked: It starts the five second "animate" timer. Then, the <code>adone</code> trigger causes Zarco to say a helpful error message when the five seconds are up.

Now to make the picker ball report its success upon picking a fortune, change its code to the following:

[[create]]
[[name]] rand,
[[colltag]] 10,
[[collider]] nograv;
[[collide]]
[[reset]] physics,
[[addtorque]] 250 20 59,
[[astop]] zerror

The <code>collide</code> trigger now contains the command "astop zerror". What this does is it stops the button's five second timer upon colliding with a fortune panel, preventing the error showing up as clearly, the physics engine is enabled for that particular user.

=== Notes ===
* Be careful introducing [[zone]]s with unusual gravity settings such as 0 or negative values; this can cause the randomizer to spam fortunes in chat or break it.
* Although virtually you can surround the ball with as many panels as possible, it is not recommended. The physics engine has a low resolution; the smaller the panels, the more likely the picker will trigger more than 1 fortune at a time.
* Do not add the "global" attribute to the button; as physics is not global, people near Zarco will see different fortunes to others.

== Simulating wind dynamics ==
Although [[cloth]] supports wind paramters, this is not controllable by commands. Using this trick, it is possible to make an environment feel more alive and reactive to the atmosphere. I use this in the [[AWReunion (world)]] welcome cabin to make the foyer's banner get blown away by the harsh outdoor winter winds.

[[Image:AWR cabin wind.jpg|frame|center|Opening the front doors causes the harsh winter winds to blow inside, affecting the cloth banner. Watch on [http://www.youtube.com/watch?v=XrX_Gq9xPv8 YouTube]]]

=== Basic operation ===
This trick makes use of an invisible physical ball, a looping [[animate]] timer and another time-out timer. The invisible ball is parked in front of the cloth (front toward the source of the wind). When triggered, the repeating looping timer repeatedly resets and throws the ball into the cloth banner, making it look like buffers of incoming wind. Eventually, this loop is stopped when the door is closed by using another timer.

=== Setting up the "wind ball" ===
[[Image:AWR cabin windball.png|frame|center|The "wind" ball exposed; cloth is invisible whilst in build mode.]]
Create a ball object (such as p1sph0100) in front of the cloth or physical object you wish to apply wind to. Apply it relatively high to the cloth's center point. Rotate it so that its '''X''' axis is facing the cloth. Add the following code to the ball:

[[create]]
[[name]] wind,
[[animate]] me . 1 1 1000,
[[visible]] no, [[solid]] no;
[[adone]]
[[reset]] physics name=wind,
[[addforce]] 25 ltm,
[[astart]]

The <code>create</code> trigger sets properties for the ball:
* Its name is "wind", which will allow other objects to trigger its timer
* It is given a timer of 1000 milliseconds (one second) using the legacy animate command
* It is made invisible and non-collidable by users (this will not affect physics)

The <code>adone</code> trigger causes the following to happen when the ball's one second timer is triggered:
* The physics are reset for the ball, causing it to move back into original position
* It is pushed into the cloth (assuming its X axis is toward the cloth) using the "addforce" command
* "astart" triggers this timer again after one second; this causes a loop

=== Setting up the door and "time out" ===
For this tutorial, I will explain how to trigger the "wind" using a door. However this can be applied to any event, such as falling rocks exposing an opening. Create a door that is ideally facing the cloth with the ball in between. Add the following code:

[[create]]
[[animate]] me . 1 1 10000;
[[activate]]
[[rotate]] -10 time=2 smooth wait=8,
[[collider]] name=wind,
[[astart]] wind,
[[astart]];
[[adone]]
[[astop]] wind,
[[collider]] static name=wind

The <code>create</code> trigger gives the door a timer of 10000 milliseconds (ten seconds) that will be used to end the wind's timer loop. This time is chosen to coincide with the door's eight second rotate command.

The <code>activate</code> trigger causes the following to happen when the door is clicked:
* The door opens and holds its position for eight seconds
* The wind ball is made a physical object
* The wind ball's one second looping timer is started, making it throw itself into the cloth every second
* The door's own ten second timer is started

The <code>adone</code> trigger causes the following to happen when the door's ten second timer is triggered:
* The wind ball's repeating one second timer is stopped
* The ball is made a static object, to prevent lag

[[Category:Guides|P]]

Category:Guides

2026-02-09T14:42:13Z

Xan: Created page with "A '''guide''' is a special type of page on the DeltaWiki that is written with the intent to be a personable guide of instruction regarding a particular niche of Delta Worlds. Guides are generally allowed to be much looser than standard articles, enabling the writer to engage readers personally and connect with them better for instructional purposes. Category:DeltaWiki"

A '''guide''' is a special type of page on the DeltaWiki that is written with the intent to be a personable guide of instruction regarding a particular niche of Delta Worlds. Guides are generally allowed to be much looser than standard articles, enabling the writer to engage readers personally and connect with them better for instructional purposes.

[[Category:DeltaWiki]]

Guide:INI Enhancements

2026-02-09T14:40:40Z

Xan:

INI Enhancements are additions you can make to the '''dworld.ini''' file in the '''DeltaWorlds (ex C:\DeltaWorlds)''' program folder to expand the functionality of certain features of the browser. To add these enhancements to the browser, copy the text and paste it under the appropriate subsection in the .ini file. If the subsection text does not exist in your .ini file, copy it and paste it into the end of the file.

==Geometric Settings==
'''Subsection:''' [Geometry]

'''Text:'''
ambient_mul=1.0 
diffuse_mul=1.0 
ambient_min=0.0 
diffuse_min=0.0 
bump_coef=1.0 
 
'''Description:''' These settings show the default values. 
 
The *_mul values are a multiplier to the settings read from the geometry file, independent of its format. The values' range is from 0.1 to 3.0. 
 
The *_min values are the lower limits for the settings read from the geometry file, independent of its format. The values' range is from 0.0 to 1.0. 
 
The values for bump_coef can be used as a multiplier for the intensity of bumpmaps defined within RWX scripts (Texture <tname> bump <bname>). The values' range is from 0.1 to 10.0. 
 
A useful setting for increasing texture contrast and reactivity to light is: 
[geometry] 
diffuse_mul=2.0 
ambient_mul=0.75 

==Cull Mode==
'''Subsection:''' [Performance]

'''Text:''' cull_mode=#

'''Description:''' Cull mode allows one to choose how the browser culls back faces. Replace the # with the appropriate number.

''cull_mode=1:'' Do not cull back faces. 
''cull_mode=2:'' Browser and RenderWare default. Culls faces with clockwise vertices. 
''cull_mode=3:'' Culls faces with counterclockwise vertices. 

==Fill Mode==
'''Subsection:''' [Performance]

'''Text:''' fill_mode=#

'''Description:''' Fill mode allows one to choose between render states. Replace the # with the appropriate number.

''fill_mode=1:'' Point Cloud, rendering vertices only. 
''fill_mode=2:'' Wireframe, rendering connecting lines between verticies. 
''fill_mode=3:'' Browser Default, the normal view. It's the same as setting it to 0 or leaving it undefined. 

==Object Selection Increase==
'''Subsection:''' [Special]

'''Text:''' max_pick_count=1024

'''Description:''' This value overrides the number of objects a user can select at once. The default browser setting is 128. The maximum amount of objects this override allows is 1024.

==Visibility Fixed Range Limit==
'''Subsection:''' [Visible]

'''Text:''' range_limit_fixed=#

'''Description:''' This limit will append ranges in 10 meter steps to the Visibility Menu, up to the range limit ''you'' choose. Note that the browser will only render objects beyond 200 meters if they have already been downloaded and cached. Possible values are in increments of 10 between 200 and 500. Replace the # with the appropriate number.

''Warning!'' To take advantage of this feature, you need a strong computer, a good graphics card and a lot of dedicated video memory. With today's common use of textures and pictures, the hardware hits the limits easier than some years ago.

==Visibility Floating Range Limit==
'''Subsection:''' [Visible]

'''Text:''' range_limit_float=#

'''Description:''' This limit for the floating visible range is used when 'Float' has been selected from the Visibility Menu. Note that the browser will only render objects beyond 200 meters if they have already been downloaded and cached. Possible values are in increments of 10 between 200 and 500. Replace the # with the appropriate number.

''Warning!'' To take advantage of this feature, you need a strong computer, a good graphics card and a lot of dedicated video memory. With today's common use of textures and pictures, the hardware hits the limits easier than some years ago.

[[Category:Browser]]
[[Category:Guides|I]]

Guide:INI Enhancements

2026-02-09T14:40:04Z

Xan: Created page with "INI Enhancements are additions you can make to the dworld.ini file in the DeltaWorlds program folder to expand the functionality of certain features of the browser. To add these enhancements to the browser, copy the text and paste it under the appropriate subsection in the .ini file. If the subsection text does not exist in your .ini file, copy it and paste it into the end of the file. ==Geometric Settings== '''Subsection:''' [Geometry] '''Text:''' ambient_mul=1.0<br..."

INI Enhancements are additions you can make to the dworld.ini file in the DeltaWorlds program folder to expand the functionality of certain features of the browser. To add these enhancements to the browser, copy the text and paste it under the appropriate subsection in the .ini file. If the subsection text does not exist in your .ini file, copy it and paste it into the end of the file.

==Geometric Settings==
'''Subsection:''' [Geometry]

'''Text:'''
ambient_mul=1.0 
diffuse_mul=1.0 
ambient_min=0.0 
diffuse_min=0.0 
bump_coef=1.0 
 
'''Description:''' These settings show the default values. 
 
The *_mul values are a multiplier to the settings read from the geometry file, independent of its format. The values' range is from 0.1 to 3.0. 
 
The *_min values are the lower limits for the settings read from the geometry file, independent of its format. The values' range is from 0.0 to 1.0. 
 
The values for bump_coef can be used as a multiplier for the intensity of bumpmaps defined within RWX scripts (Texture <tname> bump <bname>). The values' range is from 0.1 to 10.0. 
 
A useful setting for increasing texture contrast and reactivity to light is: 
[geometry] 
diffuse_mul=2.0 
ambient_mul=0.75 

==Cull Mode==
'''Subsection:''' [Performance]

'''Text:''' cull_mode=#

'''Description:''' Cull mode allows one to choose how the browser culls back faces. Replace the # with the appropriate number.

''cull_mode=1:'' Do not cull back faces. 
''cull_mode=2:'' Browser and RenderWare default. Culls faces with clockwise vertices. 
''cull_mode=3:'' Culls faces with counterclockwise vertices. 

==Fill Mode==
'''Subsection:''' [Performance]

'''Text:''' fill_mode=#

'''Description:''' Fill mode allows one to choose between render states. Replace the # with the appropriate number.

''fill_mode=1:'' Point Cloud, rendering vertices only. 
''fill_mode=2:'' Wireframe, rendering connecting lines between verticies. 
''fill_mode=3:'' Browser Default, the normal view. It's the same as setting it to 0 or leaving it undefined. 

==Object Selection Increase==
'''Subsection:''' [Special]

'''Text:''' max_pick_count=1024

'''Description:''' This value overrides the number of objects a user can select at once. The default browser setting is 128. The maximum amount of objects this override allows is 1024.

==Visibility Fixed Range Limit==
'''Subsection:''' [Visible]

'''Text:''' range_limit_fixed=#

'''Description:''' This limit will append ranges in 10 meter steps to the Visibility Menu, up to the range limit ''you'' choose. Note that the browser will only render objects beyond 200 meters if they have already been downloaded and cached. Possible values are in increments of 10 between 200 and 500. Replace the # with the appropriate number.

''Warning!'' To take advantage of this feature, you need a strong computer, a good graphics card and a lot of dedicated video memory. With today's common use of textures and pictures, the hardware hits the limits easier than some years ago.

==Visibility Floating Range Limit==
'''Subsection:''' [Visible]

'''Text:''' range_limit_float=#

'''Description:''' This limit for the floating visible range is used when 'Float' has been selected from the Visibility Menu. Note that the browser will only render objects beyond 200 meters if they have already been downloaded and cached. Possible values are in increments of 10 between 200 and 500. Replace the # with the appropriate number.

''Warning!'' To take advantage of this feature, you need a strong computer, a good graphics card and a lot of dedicated video memory. With today's common use of textures and pictures, the hardware hits the limits easier than some years ago.

[[Category:Browser]]
[[Category:Guides|I]]

Browser interface

2026-01-10T06:47:09Z

Xan: Created page with "The UI is can be configured in any arrangement with floating/docking windows. There are various themes and toolbars that may be used with the software to provide further options. == Main / 3D window == The 3D window, or the main window may run in windowed or fullscreen mode. There are various camera modes available with the ability to zoom in/out. ===Avatars=== A user's avatar is the representation of them within that environ..."

The UI is can be configured in any arrangement with [[floating]]/[[docking]] windows. There are various [[themes]] and [[toolbars]] that may be used with the software to provide further options.

== Main / 3D window ==
The 3D window, or the main window may run in windowed or fullscreen mode. There are various [[user camera|camera]] modes available with the ability to zoom in/out.

===Avatars===
A user's [[Avatars|avatar]] is the representation of them within that environment. Tourists have access to two avatars, typically male / female. Citizens have the world's full selection of avatars available to them. As well, citizens can have their own [[personal avatar]] to use among worlds enabled for it. Avatars may act out various [[gestures]], and ride/hold [[mover]] objects. Users may right-click an avatar to access that user's [[avatar menu]].

===Objects===
Everything seen within a world is comprised of [[objects]]. The browser allows in public building worlds, and those with rights in private worlds, to build. Most building with the browser is done by duplication, one object duplicated, and manipulated into another object with the [[Object Properties Dialog]] box. In worlds where one is able to build, they may access this dialog by right clicking any object. At the discretion of the [[caretaker]], those who do not have rights to build, may or may not access the object dialog to view the data of objects.

====Signs / Pictures / Media====
With [[sign|sign objects]], it is easy to display text to a user to give them information about the environment or describing an item. [[picture|Picture objects]] are used to display a wide variety of formats for images on the web.

A very useful feature is the ability to display [[media|media /video]] within your world, such as a music video.

====Link objects====
[[URL|Link objects]] link to other websites or email address. One can make make a mailbox, or a sign object linking to their homepage.

====Mover objects====
With version 4.1 of Active Worlds, [[mover]] objects can be used for users to ride, "place/seat", or hold. Mover objects are designated with a hand cursor with a tooltip displaying <Mover> (or <"Mover name">).

====Particles / Zones====
[[Particle Emitter|Particles]] can add beautiful, colorful effects to worlds. Splashing water, fire, smoke, and weather are various effects made easily by this.

[[Zone]]s can be used to partition world settings or a part of the environment within certain areas. Zones can be different shapes and sizes.

===Menubar===
Starting with 5.2 the menu bar is integrated into the 3D view.
The size of the menubar's font can be changed from the Menu/Options/Settings/Advanced dialog along with the toolbar's icon sizes.

''Moving the bars''

Hold the Right Alt key down, Right Click once into a frame and drag-move the frame to any position on screen. Once the mouse button and the Right Alt key are released, the position is locked again.

''Alignment and Orientation''

When you move a frame to the left or right edges of the screen, it will auto-align its orientation vertically.
When you move a frame to the top or bottom edges of the screen, it will auto-align its orientation horizonal.
To override this kind of alignment to the screen's borders, hold the Right Ctrl key down while moving the frame to either edge of the screen.

''Center''

To center a frame horizontal, again hold the Right Alt key down, and Double Right Click into the frame.
To center a frame vertically, hold the Right Alt key down along with the Right Ctrl key, and Double Right Click into the frame.

''Storing your settings''

The relative screen position of the overlay frames is independend of the screen's dimension. Whenever the 3D viewport window gets resized, the position of the HUD frames will remain at their relative position to the edges of the screen.

===Toolbar===
Starting with 5.2 the tool bar is integrated into the 3D view.

The size of the toolbar's icons can be changed from the Menu/Options/Settings/Advanced dialog.
For moving and alignment of the toolbar, please look at Menubar above.

Active Worlds supports a customizable [[toolbar]] to be used for enhanced interaction with a particular environment, or simply different styles.

===Full screen mode===
The main window can be set to full screen mode with its own seperate configuration of floating and dialog windows metrics. '''ALT+Enter''' is the keyboard shortcut used to toggle this state.

==Chat window==
Everything that is said within a world, in private [[whispers]], or displayed to inform the user is displayed here. When other users talk, a user may right click a chat line to access another's [[avatar menu]]. Various errors encountered, especially object errors, will appear here as well if configured in their options to do so.

The chat window may be docked, floating, or [[auto-hide]].

==Tabs==
The tabs pane is accessible using the 'F9' key. It may be docked, floating, or [[auto-hide]].

===Worlds===
This list displays all of the non-hidden worlds within a universe, along with the user count. The dividers at the top of the list may be clicked to sort based on world name A-Z, or population count. Worlds may be public, or private, with gray worlds representing those private.

Worlds are rated using guidelines not dissimilar to the MPAA motion picture ratings. The ratings are G "general", PG "parental guidance", PG-13, R "restricted", and X "explicit".

===Contacts===
[[Contacts]] lists are how one keeps track of other users online status, and communicates and interacts with others in the universe. You may send telegrams to your contacts, join or invite them to your location, and adjusting privacy / block settings for that user.

===Telegrams===
Telegrams that have been sent and received from users in the universe. The dividers may be clicked to sort by that divider's category.

===Voice Chat===
The voice chat tab contains the various settings for voice chat. Visit [[Voice_chat]] to learn more about this option.

===Teleports===
This tab provides a list of your saved teleports.

===User Guide===
This tab shows the User Guide.

===Users===
In some universes, this tab provides a list of users within the universe.

===Search===
In some universes, this tab provides a search function that allows users to search for specific worlds, as identified by world owners.

==Integrated web browser==
The integrated webbrowser uses Chromium Embedded Framework (CEF) to view rich web content. World owners can design websites, for example, to present the world or to guide visitors

==Building==
Active Worlds supports a [[build mode]] to provide ease building. The object properties dialog is always open, all hidden objects are shown. Physics and collision is taken out of movement, and flying is enabled.

See [[build]]ing for more information regarding the building interface.

[[Category:Browser interface]]

Privacy

2026-01-10T06:46:25Z

Xan:

The Privacy dialog allows you to control some of the information which other citizens of DeltaWorlds can learn about you. It also lets you control whether or not people you have not specified individual settings for in your contact list can send you files or join requests.

To adjust your privacy settings, go to the Options menu and select Settings..., then click on the Privacy tab.

==Defaults==

* Hide my online/offline/AFK status: This setting places a question mark icon next to your name in people's contact lists where the online checkmark of AFK icon would otherwise be displayed to indicate that you are online or in "Away From Keyboard" (AFK) mode.

* Hide my current world: This setting allows you to hide which world you are currently in so that it will not be displayed next to your name in people's contact lists. By default, if someone else has you on their contact list, they will be able to see what world you are in when you are logged in.

* Block telegrams and whispers: This setting blocks incoming telegrams and whispers.

* Block join requests: With this option set, if anyone tries to send you a join request they will receive a message stating that their request to join was refused.

* Block file transfers: With this option set, if anyone tries to send you a file they will receive a message stating that you did not accept their File Transfer request. Note that for security reasons, you will always be asked to verify a file transfer request before it is accepted. Note: File transfers have been disabled in the Active Worlds Universe.

== Other Settings ==

* Confirm contact list add requests: This allows the user to select which people are allowed on their contact lists.

* Confirm join requests: Causes a confirmation message to be displayed when someone tries to join you.

* Automatically enter AFK mode: Set the number of minutes where you want to automatically be set as AFK.

* Automatically leave AFK mode on keyboard activity: Leaves AFK mode automatically when you start typing.

* Allow relay my chat to non-privileged bots: Enables or disables chat to be relayed to non-privileged bots. By unchecking this, you deny bots the opportunity of logging or rebroadcasting your chat.

Privacy

2026-01-10T06:46:08Z

Xan: Created page with "The Privacy dialog allows you to control some of the information which other citizens of Active Worlds can learn about you. It also lets you control whether or not people you have not specified individual settings for in your contact list can send you files or join requests. To adjust your privacy settings, go to the Options menu and select Settings..., then click on the Privacy tab. ==Defaults== * Hide my online/offline/AFK status: This setting places a question ma..."

The Privacy dialog allows you to control some of the information which other citizens of Active Worlds can learn about you. It also lets you control whether or not people you have not specified individual settings for in your contact list can send you files or join requests.

To adjust your privacy settings, go to the Options menu and select Settings..., then click on the Privacy tab.

==Defaults==

* Hide my online/offline/AFK status: This setting places a question mark icon next to your name in people's contact lists where the online checkmark of AFK icon would otherwise be displayed to indicate that you are online or in "Away From Keyboard" (AFK) mode.

* Hide my current world: This setting allows you to hide which world you are currently in so that it will not be displayed next to your name in people's contact lists. By default, if someone else has you on their contact list, they will be able to see what world you are in when you are logged in.

* Block telegrams and whispers: This setting blocks incoming telegrams and whispers.

* Block join requests: With this option set, if anyone tries to send you a join request they will receive a message stating that their request to join was refused.

* Block file transfers: With this option set, if anyone tries to send you a file they will receive a message stating that you did not accept their File Transfer request. Note that for security reasons, you will always be asked to verify a file transfer request before it is accepted. Note: File transfers have been disabled in the Active Worlds Universe.

== Other Settings ==

* Confirm contact list add requests: This allows the user to select which people are allowed on their contact lists.

* Confirm join requests: Causes a confirmation message to be displayed when someone tries to join you.

* Automatically enter AFK mode: Set the number of minutes where you want to automatically be set as AFK.

* Automatically leave AFK mode on keyboard activity: Leaves AFK mode automatically when you start typing.

* Allow relay my chat to non-privileged bots: Enables or disables chat to be relayed to non-privileged bots. By unchecking this, you deny bots the opportunity of logging or rebroadcasting your chat.

Contacts

2026-01-10T06:45:28Z

Xan:

Over time, you’ll make many new friends within DeltaWorlds. To keep up with these friends, you can add them to your contact list. From your contact list, you’ll be able to see when they are online, you can send them telegrams, and you can join or invite them to different locations.

There are three ways to add a new contact to this list:

* Right click on their avatar, then click “Add to Contacts”, or
* Right click on their name in chat, then click “Add to Contacts”, or
* Right click in the contacts tab and click “Add New Contact”. From there, type in their name exactly as it appears.

Contacts

2026-01-10T06:45:14Z

Xan: Created page with "Over time, you’ll make many new friends within Active Worlds. To keep up with these friends, you can add them to your contact list. From your contact list, you’ll be able to see when they are online, you can send them telegrams, and you can join or invite them to different locations. There are three ways to add a new contact to this list: * Right click on their avatar, then click “Add to Contacts”, or * Right click on their name in chat, then click “Add to..."

Over time, you’ll make many new friends within Active Worlds. To keep up with these friends, you can add them to your contact list. From your contact list, you’ll be able to see when they are online, you can send them telegrams, and you can join or invite them to different locations.

There are three ways to add a new contact to this list:

* Right click on their avatar, then click “Add to Contacts”, or
* Right click on their name in chat, then click “Add to Contacts”, or
* Right click in the contacts tab and click “Add New Contact”. From there, type in their name exactly as it appears.

Public Speaker

2026-01-10T06:44:29Z

Xan: Created page with "The caretaker of a world may occasionally designate certain citizens to be '''Public Speakers''' (PS), who are citizens whose chat messages are transmitted to all users within a given area. Everyone in the area can hear and see a public speaker, regardless of how many other people are around. You can tell a Public Speaker by the fact that their chat messages appear in that chat window in bold text. Since by default all users hear the nearest 50 users, the Public Spe..."

The [[caretaker]] of a world may occasionally designate certain citizens to be '''Public Speakers''' (PS), who are citizens whose chat messages are transmitted to all users within a given area. Everyone in the area can hear and see a public speaker, regardless of how many other people are around. You can tell a Public Speaker by the fact that their chat messages appear in that chat window in bold text.

Since by default all users hear the nearest 50 users, the Public Speaker effect is only really useful in situations where there are more than 50 people gathered in a single location, such as very large gatherings and events.

If you encounter a public speaker in a world, remember that they can hear all the conversations going on around them, so be patient if he/she does not respond immediately to your questions. In really crowded areas it is can be quite difficult for a public speaker to hold individual conversations since there are so many people talking at once.

Public Speakers have access to additional [[Special Avatars|special avatars]] which other citizens cannot use.

[[Category: World administration]]

Category:Communicating

2026-01-10T06:44:04Z

Xan: Redirected page to Communication

#REDIRECT [[Communication]]

{{R from gerund}}

Communicating

2026-01-10T06:43:21Z

Xan: Created page with "DeltaWorlds is a social environment. From chatting to building in groups, the application is designed around interaction. Within DeltaWorlds, you will meet people from a wide variety of places. Knowing the various ways to talk with people is important to forming relationships. ==Communicating== Chatting with other people is an important part of the Active Worlds experience. When you enter a world, after the scene loads you may see avatars around you representing o..."

DeltaWorlds is a social environment. From chatting to building in groups, the application is designed around interaction. Within DeltaWorlds, you will meet people from a wide variety of places. Knowing the various ways to talk with people is important to forming relationships.

==Communicating==

Chatting with other people is an important part of the Active Worlds experience. When you enter a world, after the scene loads you may see avatars around you representing other people who are near you in the same world. Depending on the world's settings, you might also notice that avatars have names above their heads when you get close to them, or after that person has said something while they are in your chat range. When other people talk, in most worlds, what they say will generally also appear above their avatar's head. Eventually, the above-head messages might disappear or be replaced, but the names will remain. You can either read what people say as it appears above their heads, or in the Chat History frame which also displays messages from people who are behind you or off to the side, as long as they are within your chat range. The Chat History will also display whispers, and messages from parts of the system such as the Immigration Officer or the Building Inspector, and console messages.

===The Chat Window===
At the core of this social interaction is the chat window. After first arriving in Active Worlds, the chat box is shown at the bottom of the screen.

The top portion of the chat window is where you will see most of the chat. This chat contains text from users as well as bots and system messages. Some of the things that you will encounter include:

* System Messages: These are the first messages that appear in the chat window when first entering. Occasionally they may appear during system maintenance. Usually, these messages contain important information from Active Worlds.
* World Messages: These messages usually immediately follow the system messages, and appear after you first enter a new world. These messages are from the world owners and may contain a welcome message, the name of the world, and other information that the world owners think you may need. World messages also appear in a green colored text.
* Public Speakers: Public speakers appear in bold text and serve various functions.
* Public Speakers in Private Worlds: These consist of world owners and individuals that the world owners have given the authority to speak in bold.
* Bots: Bots are computer generated characters that serve a function in the world. Bots are usually created to add functions to the software. Functions could include games or chat additions, like colored chat. The bots are always identified with brackets surrounding their name in the "whisper" section at the bottom of the main chat window, as such: [bot]
* Users: These are other users on the program. Their text may appear black, brown, or blue, according to your listening settings. In worlds where chat bots are in use, users may appear in a variety of colors.
* Whispers: These are private chat that only you can see. It is always in blue italics.

'''Local, Global, and GZ Chat Options:'''
In the Active Worlds browser, there are two sections immediately under the main chat area that consist of “Talk to” and “Listen to” options. The drop-down box to the right of “Talk to” provides three options: Global, GZ, and Local. Global allows you to talk to anyone within the world, regardless of distance. GZ restricts chat to those who are located at the “Gatezone”, or landing area. This is a certain distance from the center of the world. Local restricts chat to those who are near you.

Similarly, the options located next to “Listen to” define who you can hear. Checking “Global” enables you to hear anyone else who is on global chat no matter their distance away from you. Local restricts listening to only those who are near you.

Some worlds offer further options that enable you to listen to or chat with certain parts of that particular world. To find out which areas they cover, you would have to contact the world owner for those details.

'''To talk to other people:'''
Under the “Talk to” section is the chat input area. This is where you can type to send chat messages to other users. What you type appears in the Message box, also known as the Chat Entry box, which is located just below the Chat History. After typing your chat message, pressing the Enter key sends your message. Then you'll see your message appear in the Chat History window, and other people that you are within chat range of will see it also.

'''To mute other people:'''
If someone is speaking that you would rather not see any more chat messages from, you can mute them. To mute someone, right click on that person's avatar and select Mute from the avatar pop-up menu. You can un-mute them again later by repeating the same procedure.

'''Whispering:'''
The bottom section of the chat window is for private text, called “whispers”. The whisper box is not shown by default and must be enabled. To enable whispers, select Show and then check Whispers. With the whisper box, use thedrop-downn to select the person that you want to whisper to and then type the private message in the message box to the right.

'''Resizing the Chat Window'''
You can resize the chat window by changing the border between the main 3D-view window and the Chat History frame. Just position the cursor over the border between the 3D-window and the chat window until you see an up-down arrow, then hold down your primary mouse button and drag the border to the desired position.

'''Reading Past Chat'''
You can also use the scroll-up and scroll-down buttons next to the chat history to look at messages that have scrolled off of the screen. These buttons move the text in the window up or down one line at a time. You can also click either above or below the 'slider bar' divider between the scroll buttons to move the text up or down one 'page' at a time.

The Chat History window displays any error messages you may get while building, for instance, if you try to build too many objects in one place, or change someone else's property. These errors are given to you as a message from the all-powerful "Building Inspector".

===Avatar Pop-up menu===
Right-clicking on an avatar brings up additional options. These include:

* Mute on Sight: This silences all chat coming from this person.
* Whisper: Activates the avatar in the Whisper box below chat.
* View Home Page: If the user has defined a home page, this enables you to visit the website they have designated. The home page can be designated by your Citizen Attributes. Click on Options in the menu, then click on Citizen. When the Citizen Attributes box appears, type in the URL of your home page with he label "Home Page".

'''Joining'''
Using the Contact List, you can join other people in Active Worlds, wherever they happen to be. To join someone, right-click on their name and select Join. You will be teleported to their current location.

A successful join requires that the join be allowed by the person whom you are trying to join. It also requires that you have Enter privileges in the world in which that person's avatar is located at that time. Don't take it personally if people fail to accept your join requests. They may have left their computer unattended briefly and missed the request, or they may have set it to auto-reject join requests during a private meeting and simply forgotten to change it back. In fact, there are many possible reasons why a join request may not be accepted. It's generally a good idea to establish communication through telegrams before attempting to join someone. You can control who can join you with the Privacy dialog box.

If the person you are attempting to join has set their privacy options to block join requests from you or from all people, your join request will automatically be rejected. If the person does not accept or reject your request within 30 seconds, the request will expire.

===Contact List===

Over time, you’ll make many new friends within Active Worlds. To keep up with these friends, you can add them to your contact list. From your contact list, you’ll be able to see when they are online, you can send them telegrams, and you can join or invite them to different locations.

There are three ways to add a new contact to this list:

* Right click on their avatar, then click “Add to Contacts”, or
* Right click on their name in chat, then click “Add to Contacts”, or
* Right click in the contacts tab and click “Add New Contact”. From there, type in their name exactly as it appears.

===Telegrams===
Telegrams are instant messages that you can send to people for them to read at a later date. To send or receive a telegram, you must add the person to your contact list as shown above.

Telegrams can be found in the Telegram Tab. The telegram tab consists of a simple list of telegrams sent and received. These can be sorted by name or by date by clicking on the top row. New telegrams appear with a notification in the chat window, and they will have a red telegram icon in the telegram tab. To read the telegram, simply click on it and it will appear in your chat window. To reply, right click on the telegram in the telegram tab and select reply. To send a new telegram, open the Contacts tab, right click on the person you want to send a message to, and then click on send telegram.

In the telegram tab, when you right click on a telegram you also have the option to delete the message or to block the user.

===Sending Files===
Sending files is accomplished by right-clicking on a name in the contacts tab. A confirmation window opens for them and once they agree by clicking ok, a file transfer window opens up. You select the file folder and the file or files to be sent. The other person has another window where they select the destination folder.

If either person is behind a router, the port that is used for this (port 3000) has to be forwarded to the computer where the AW browser is running. If this is not set the file transfer will fail.

This option is disabled in some universes running the Active Worlds software.

'''Public Speakers'''
See: [[Public Speaker]]

[[Category: Communicating]]

==Some Chat Tips For Beginners==

===General Tips===

Talking to other users, or "chatting", in Active Worlds is similar to chatting in any other Internet chat environment. Simply type whatever it is you would like to say and hit the ENTER key. Your words will be broadcast to everyone else nearby. Similarly, whatever words other people type will be sent to you and will appear on your screen.

If you are new to chatting over the Internet, you will quickly discover that chat has a unique set of rules and jargon (sometimes referred to as "netiquette") that can be confusing to a newcomer. But never fear, in just a few minutes you can familiarize yourself with some basic guidelines and in no time you will be chatting like a pro!

Here are some basic tips to keep in mind if you want to have a positive chatting experience:

*Never type in all capital letters. WHEN YOU TYPE IN ALL CAPITAL LETTERS IT SOUNDS LIKE YOU ARE SHOUTING! People generally find this very annoying.
*Be polite to strangers. If you don't know the people you are talking to, it is appropriate to be as polite as if you are meeting someone for the first time in real life.
*If someone doesn't want to chat, don't harass them. There are plenty of people in Active Worlds to talk to. If one person doesn't want to chat with you, just move on, don't pester them.
*Don't be offensive. Offensive behavior is totally inappropriate unless you are in private and among good friends who have indicated that they do not mind. Otherwise, you will just annoy everyone and you will wind up getting muted. Also in certain worlds and areas within worlds (such as Ground Zero in AlphaWorld) offensive behavior may be grounds for ejection.

===Some common terms===

Over the years, Internet chat has adopted some shorthand equivalents for common terms. Here are a few of the most common:

* LOL - Laughing Out Load
* ROTFL - Rolling On The Floor Laughing
* BRB - Be Right Back
* IMO - In My Opinion (also IMHO for In My Humble Opinion)

'''Smileys'''

"Smileys" or "emoticons" are special combinations of characters that people sometimes use to indicate emotion. Most are intended to look like a smiling face turned sideways. For example:

:-)

There is an almost infinite number of variations on this simple theme.

Chat

2026-01-10T06:42:33Z

Xan:

'''''This article shares content and wording with [[Communicating]].'''''
 

Talking to other users, or "chatting", in [[Delta Worlds]] is similar to chatting in any other Internet chat environment. Simply type whatever it is you would like to say and hit the ENTER key. Your words will be broadcast to everyone else nearby. Similarly, whatever words other people type will be sent to you and will appear on your screen.

If you are new to chatting over the Internet, you will quickly discover that chat has a unique set of rules and jargon (sometimes referred to as "netiquette") that can be confusing to a newcomer. But never fear, in just a few minutes you can familiarize yourself with some basic guidelines and in no time you will be chatting like a pro!

Here are some basic tips to keep in mind if you want to have a positive chatting experience:

Never type in all capital letters. WHEN YOU TYPE IN ALL CAPITAL LETTERS IT SOUNDS LIKE YOU ARE SHOUTING! People generally find this very annoying.
Be polite to strangers. If you don't know the people you are talking to, it is appropriate to be as polite as if you are meeting someone for the first time in real life.
If someone doesn't want to chat, don't harass them. There are plenty of people in Active Worlds to talk to. If one person doesn't want to chat with you, just move on, don't pester them.
Don't be offensive. Offensive behavior is totally inappropriate unless you are in private and among good friends who have indicated that they do not mind. Otherwise, you will just annoy everyone and you will wind up getting muted. Also in certain worlds and areas within worlds (such as Ground Zero in AlphaWorld) offensive behavior may be grounds for ejection.

'''Some common terms'''

Over the years, Internet chat has adopted some shorthand equivalents for common terms. Here are a few of the most common:

* LOL - Laughing Out Load
* ROTFL - Rolling On The Floor Laughing
* BRB - Be Right Back
* IMO - In My Opinion (also IMHO for In My Humble Opinion)
* AFK - Away From Keyboard

Here are a few of the most common abbrivations/emoticons you will find users using exclusively in the Activeworlds Browser:

* ((<User Name>)) - This is to give someone a hug, adding parentheses around someone's name will let them know you hugged them.
* AFAW - Away From Activeworlds

'''Smileys'''

"Smileys" or "emoticons" are special combinations of characters that people sometimes use to indicate emotion. Most are intended to look like a smiling face turned sideways. For example:

:-)

There are an almost infinite number of variations on this simple theme.

'''To talk to other people:'''

To talk to other people, all you have to do is type your message. What you type appears in the Message box, also known as the Chat Entry box, which is located just below the Chat History. After typing your chat message, pressing the Enter key sends your message. Then you'll see your message appear in the Chat History window, and other people that you are within chat range of will see it also.

'''To mute other people:'''

If someone is speaking that you would rather not see any more chat messages from, you can mute them. To mute someone, right click on that person's avatar and select Mute from the avatar pop-up menu. You can un-mute them again later by repeating the same procedure.

'''Chat Window'''

You can resize the chat window by changing the border between the main 3D-view window and the Chat History frame. Just position the cursor over the border between the 3D-window and the chat window until you see an up-down arrow, then hold down your primary mouse button and drag the border to the desired position.

You can also use the scroll-up and scroll-down buttons next to the chat history to look at messages that have scrolled off of the screen. These buttons move the text in the window up or down one line at a time. You can also click either above or below the 'slider bar' divider between the scroll buttons to move the text up or down one 'page' at a time.

The Chat History window displays any error messages you may get while building, for instance if you try to build too many objects in one place, or change someone else's property. These errors are given to you as a message from the all-powerful "Building Inspector".

The avatar "pop-up" menu can be invoked in one of two ways: you can right-click with the mouse directly on an avatar in the 3D window, or you can right-click on a line of chat text in the chat window to bring up the avatar menu for that user.

The various options available on this menu depend on what rights you have and what type of user they are:

The top line of the menu identifies the name of the user you clicked on. If the user is a citizen, it also displays their citizen number. If the user is a bot, it displays the citizen number of the bot's owner. Citizen number and bot owner information is only available if the world server is running version 3.1 or later. The other menu options are as follows:

Mute
Allows you to mute the user. When a user is muted, you no longer receive any of their chat messages.

Whisper
Allows you to whisper to the user. Whispers are private chat messages that only the recipient sees.

Add to contacts
This option is enabled if the user is a citizen. It adds them to your contact list.

Eject...
This option is enabled if you have eject rights in the world. It allows you to eject the user from the world.

View Home Page
This option is new in Active Worlds 3.1 and is enabled if the user is a citizen. It allows you to view their home page if they have one set.

Look up citizen...
This final option is only enabled for universe administrators and if the user is a citizen. It opens the citizens dialog and looks up the user's account.

'''Whispering'''
A whisper is a chat message sent directly to another user. When you whisper, the recipient is the only person who can hear what you say.

The whisper controls are disabled by default in simple mode. If the whisper controls are not visible in your browser, either press the Advanced Mode button, or select Whisper from the Show Menu.

To whisper to someone, first select their name in the "Whisper To" list. Then simply type your message in the whisper field and press Enter like you would for a normal chat message. You can also whisper to someone by selecting Whisper from the avatar pop-up menu.

Whispers appear in your chat history window in blue italics to distinguish them form normal chat. Whispers that you send are listed along with the name of the person you whispered to.

Note that you can quickly switch back and forth between the normal chat field, the whisper list and the whisper chat field by simply pressing the Tab key.

Also note that in order to whisper to someone, they must be physically nearby and they must have already revealed their identity by speaking (either via normal chat, or by first whispering to you.) Mute blocks whispers as well as normal chat. If there is currently no one around to whisper to, the whisper field will automatically disable itself.

Be aware that in some worlds the ability to whisper may be disabled for tourists. This option is set in the World Features dialog.

If you don't want to whisper you can hide the extra whisper controls from the Show Menu or by pressing the F8 key.

[[Category: Communicating]]
[[nl:Chatten]]

Chat

2026-01-10T06:42:15Z

Xan: Created page with "'''''This article shares content and wording with Communicating.''''' Talking to other users, or "chatting", in Active Worlds is similar to chatting in any other Internet chat environment. Simply type whatever it is you would like to say and hit the ENTER key. Your words will be broadcast to everyone else nearby. Similarly, whatever words other people type will be sent to you and will appear on your screen. If you are new to chatting over the Internet..."

'''''This article shares content and wording with [[Communicating]].'''''
 

Talking to other users, or "chatting", in [[Active Worlds]] is similar to chatting in any other Internet chat environment. Simply type whatever it is you would like to say and hit the ENTER key. Your words will be broadcast to everyone else nearby. Similarly, whatever words other people type will be sent to you and will appear on your screen.

If you are new to chatting over the Internet, you will quickly discover that chat has a unique set of rules and jargon (sometimes referred to as "netiquette") that can be confusing to a newcomer. But never fear, in just a few minutes you can familiarize yourself with some basic guidelines and in no time you will be chatting like a pro!

Here are some basic tips to keep in mind if you want to have a positive chatting experience:

Never type in all capital letters. WHEN YOU TYPE IN ALL CAPITAL LETTERS IT SOUNDS LIKE YOU ARE SHOUTING! People generally find this very annoying.
Be polite to strangers. If you don't know the people you are talking to, it is appropriate to be as polite as if you are meeting someone for the first time in real life.
If someone doesn't want to chat, don't harass them. There are plenty of people in Active Worlds to talk to. If one person doesn't want to chat with you, just move on, don't pester them.
Don't be offensive. Offensive behavior is totally inappropriate unless you are in private and among good friends who have indicated that they do not mind. Otherwise, you will just annoy everyone and you will wind up getting muted. Also in certain worlds and areas within worlds (such as Ground Zero in AlphaWorld) offensive behavior may be grounds for ejection.

'''Some common terms'''

Over the years, Internet chat has adopted some shorthand equivalents for common terms. Here are a few of the most common:

* LOL - Laughing Out Load
* ROTFL - Rolling On The Floor Laughing
* BRB - Be Right Back
* IMO - In My Opinion (also IMHO for In My Humble Opinion)
* AFK - Away From Keyboard

Here are a few of the most common abbrivations/emoticons you will find users using exclusively in the Activeworlds Browser:

* ((<User Name>)) - This is to give someone a hug, adding parentheses around someone's name will let them know you hugged them.
* AFAW - Away From Activeworlds

'''Smileys'''

"Smileys" or "emoticons" are special combinations of characters that people sometimes use to indicate emotion. Most are intended to look like a smiling face turned sideways. For example:

:-)

There are an almost infinite number of variations on this simple theme.

'''To talk to other people:'''

To talk to other people, all you have to do is type your message. What you type appears in the Message box, also known as the Chat Entry box, which is located just below the Chat History. After typing your chat message, pressing the Enter key sends your message. Then you'll see your message appear in the Chat History window, and other people that you are within chat range of will see it also.

'''To mute other people:'''

If someone is speaking that you would rather not see any more chat messages from, you can mute them. To mute someone, right click on that person's avatar and select Mute from the avatar pop-up menu. You can un-mute them again later by repeating the same procedure.

'''Chat Window'''

You can resize the chat window by changing the border between the main 3D-view window and the Chat History frame. Just position the cursor over the border between the 3D-window and the chat window until you see an up-down arrow, then hold down your primary mouse button and drag the border to the desired position.

You can also use the scroll-up and scroll-down buttons next to the chat history to look at messages that have scrolled off of the screen. These buttons move the text in the window up or down one line at a time. You can also click either above or below the 'slider bar' divider between the scroll buttons to move the text up or down one 'page' at a time.

The Chat History window displays any error messages you may get while building, for instance if you try to build too many objects in one place, or change someone else's property. These errors are given to you as a message from the all-powerful "Building Inspector".

The avatar "pop-up" menu can be invoked in one of two ways: you can right-click with the mouse directly on an avatar in the 3D window, or you can right-click on a line of chat text in the chat window to bring up the avatar menu for that user.

The various options available on this menu depend on what rights you have and what type of user they are:

The top line of the menu identifies the name of the user you clicked on. If the user is a citizen, it also displays their citizen number. If the user is a bot, it displays the citizen number of the bot's owner. Citizen number and bot owner information is only available if the world server is running version 3.1 or later. The other menu options are as follows:

Mute
Allows you to mute the user. When a user is muted, you no longer receive any of their chat messages.

Whisper
Allows you to whisper to the user. Whispers are private chat messages that only the recipient sees.

Add to contacts
This option is enabled if the user is a citizen. It adds them to your contact list.

Eject...
This option is enabled if you have eject rights in the world. It allows you to eject the user from the world.

View Home Page
This option is new in Active Worlds 3.1 and is enabled if the user is a citizen. It allows you to view their home page if they have one set.

Look up citizen...
This final option is only enabled for universe administrators and if the user is a citizen. It opens the citizens dialog and looks up the user's account.

'''Whispering'''
A whisper is a chat message sent directly to another user. When you whisper, the recipient is the only person who can hear what you say.

The whisper controls are disabled by default in simple mode. If the whisper controls are not visible in your browser, either press the Advanced Mode button, or select Whisper from the Show Menu.

To whisper to someone, first select their name in the "Whisper To" list. Then simply type your message in the whisper field and press Enter like you would for a normal chat message. You can also whisper to someone by selecting Whisper from the avatar pop-up menu.

Whispers appear in your chat history window in blue italics to distinguish them form normal chat. Whispers that you send are listed along with the name of the person you whispered to.

Note that you can quickly switch back and forth between the normal chat field, the whisper list and the whisper chat field by simply pressing the Tab key.

Also note that in order to whisper to someone, they must be physically nearby and they must have already revealed their identity by speaking (either via normal chat, or by first whispering to you.) Mute blocks whispers as well as normal chat. If there is currently no one around to whisper to, the whisper field will automatically disable itself.

Be aware that in some worlds the ability to whisper may be disabled for tourists. This option is set in the World Features dialog.

If you don't want to whisper you can hide the extra whisper controls from the Show Menu or by pressing the F8 key.

[[Category: Communicating]]
[[nl:Chatten]]

Teleports

2026-01-10T06:40:06Z

Xan:

==The Coordinate System==
Each world within DeltaWorlds is set up based on the real world. Locations in the real world can be found by using GPS coordinates. The same method is used within Active Worlds. These virtual GPS coordinates are based on the center of each world.

Your coordinates can be found by clicking “SHOW” in the menu bar and then enabling “Position”. Your rough coordinates can now be found in the header bar above the menu.

==Visiting Other Areas, Also Known as Teleporting==
While you may wish to walk around to visit different areas, in many worlds, this can be very time-consuming. For example, the world “AW”, also known as Alpha World, is larger than the U.S. State of California. Imagine trying to walk from one end of the state to the other.

An easier way of moving about is to “teleport”. Teleporting uses the World Coordinate System to move you from one location to another, similar to finding GPS locations on a map.

* To teleport to a specific location, select Teleport in the menu, and then click on To… This will bring up a box that includes two fields named World and Teleport. The world field is the world that you want to teleport to. This matches the world name in the Worlds Tab. The Coordinates field is the “GPS” locations that you want to teleport to. Both fields must be completed in order to teleport. The “teleport” field must have a North/South designation and an East/West designation. Once the fields are entered, press OK to teleport to that location.
* To teleport forward, select Forward in the teleport menu. This only works if you have teleported back from a previous location. You can also use the Teleport Forward icon located on the toolbar.
* To teleport back to a previous location, select Back in the teleport menu. You can also use the Teleport Back icon located on the toolbar.
* To teleport to your home location, select Home in the teleport menu. You can also use the Home icon located on the toolbar.
* To set a new location as your starting location, select Make This My Home in the teleport menu. This will create a new starting location for you when you enter the Active Worlds browser.
* To remember a location, select Remember. This is essentially the same as bookmarking a website to visit later. After selecting Remember, a box will appear where you can give the location a name. Hint: When naming locations, it’s best to be specific. Leave the world name but add in a descriptive phrase so that you can easily remember what the bookmark was at a later date.

==Accessing Teleports through the Teleport Tab==
The teleports tab is similar to your web browsers bookmark menu. All of the teleports that you have saved using the “Remember” function are stored in the teleport tab in a list. To visit a saved teleport, simply click on the name of the teleport. In addition, several actions can be taken inside of the tab box. These actions include:

*Rename: Change the name of a teleport by right-clicking on them and then selecting “Rename”.
* Delete: Delete a teleport by right-clicking on the teleport and selecting “Delete”.
* Teleport: This functions the same as the Teleport option in the menu bar.
* Teleport Back: This functions the same as the Teleport option in the menu bar.
* Teleport Home: This functions the same as the Teleport option in the menu bar.
* Remember: This functions the same as the Teleport option in the menu bar.

== Advanced Information on the Coordinate System==
From the center of the world, the coordinates increase according to the direction that the person is moving. For example, the base coordinates can be 0N, or 0 North, and 0E, or 0 East. If you traveled due north 10 meters, the coordinates would then be 10N, or 10 meters north by 0E. The coordinates are exact, up to two decimal places out.

The center of each world is commonly known as the “Landing Zone”, however, the world owner may choose to move the landing zone to another location.

Because of the way virtual reality works, two additional coordinate points must also be included. These include the direction the avatar is facing and the location vertically of the avatar. The location vertically of the avatar is represented with an “a”, immediately following the north/south and east/west coordinates. The direction the avatar is facing is represented by degrees between 0 and 360.

As an example, the initial coordinates of an avatar could be seen as “0N 0E 0a 0”. This would place the avatar facing north at the exact central point of the world. If the avatar moved north by 10 meters, flew up 10 meters, and faced south, this would then read as “10N 0E 10a 90”.

Teleports

2026-01-10T06:39:46Z

Xan: Created page with "==The Coordinate System== Each world within Active Worlds is set up based on the real world. Locations in the real world can be found by using GPS coordinates. The same method is used within Active Worlds. These virtual GPS coordinates are based on the center of each world. Your coordinates can be found by clicking “SHOW” in the menu bar and then enabling “Position”. Your rough coordinates can now be found in the header bar above the menu. ==Visiting Other..."

==The Coordinate System==
Each world within Active Worlds is set up based on the real world. Locations in the real world can be found by using GPS coordinates. The same method is used within Active Worlds. These virtual GPS coordinates are based on the center of each world.

Your coordinates can be found by clicking “SHOW” in the menu bar and then enabling “Position”. Your rough coordinates can now be found in the header bar above the menu.

==Visiting Other Areas, Also Known as Teleporting==
While you may wish to walk around to visit different areas, in many worlds, this can be very time-consuming. For example, the world “AW”, also known as Alpha World, is larger than the U.S. State of California. Imagine trying to walk from one end of the state to the other.

An easier way of moving about is to “teleport”. Teleporting uses the World Coordinate System to move you from one location to another, similar to finding GPS locations on a map.

* To teleport to a specific location, select Teleport in the menu, and then click on To… This will bring up a box that includes two fields named World and Teleport. The world field is the world that you want to teleport to. This matches the world name in the Worlds Tab. The Coordinates field is the “GPS” locations that you want to teleport to. Both fields must be completed in order to teleport. The “teleport” field must have a North/South designation and an East/West designation. Once the fields are entered, press OK to teleport to that location.
* To teleport forward, select Forward in the teleport menu. This only works if you have teleported back from a previous location. You can also use the Teleport Forward icon located on the toolbar.
* To teleport back to a previous location, select Back in the teleport menu. You can also use the Teleport Back icon located on the toolbar.
* To teleport to your home location, select Home in the teleport menu. You can also use the Home icon located on the toolbar.
* To set a new location as your starting location, select Make This My Home in the teleport menu. This will create a new starting location for you when you enter the Active Worlds browser.
* To remember a location, select Remember. This is essentially the same as bookmarking a website to visit later. After selecting Remember, a box will appear where you can give the location a name. Hint: When naming locations, it’s best to be specific. Leave the world name but add in a descriptive phrase so that you can easily remember what the bookmark was at a later date.

==Accessing Teleports through the Teleport Tab==
The teleports tab is similar to your web browsers bookmark menu. All of the teleports that you have saved using the “Remember” function are stored in the teleport tab in a list. To visit a saved teleport, simply click on the name of the teleport. In addition, several actions can be taken inside of the tab box. These actions include:

*Rename: Change the name of a teleport by right-clicking on them and then selecting “Rename”.
* Delete: Delete a teleport by right-clicking on the teleport and selecting “Delete”.
* Teleport: This functions the same as the Teleport option in the menu bar.
* Teleport Back: This functions the same as the Teleport option in the menu bar.
* Teleport Home: This functions the same as the Teleport option in the menu bar.
* Remember: This functions the same as the Teleport option in the menu bar.

== Advanced Information on the Coordinate System==
From the center of the world, the coordinates increase according to the direction that the person is moving. For example, the base coordinates can be 0N, or 0 North, and 0E, or 0 East. If you traveled due north 10 meters, the coordinates would then be 10N, or 10 meters north by 0E. The coordinates are exact, up to two decimal places out.

The center of each world is commonly known as the “Landing Zone”, however, the world owner may choose to move the landing zone to another location.

Because of the way virtual reality works, two additional coordinate points must also be included. These include the direction the avatar is facing and the location vertically of the avatar. The location vertically of the avatar is represented with an “a”, immediately following the north/south and east/west coordinates. The direction the avatar is facing is represented by degrees between 0 and 360.

As an example, the initial coordinates of an avatar could be seen as “0N 0E 0a 0”. This would place the avatar facing north at the exact central point of the world. If the avatar moved north by 10 meters, flew up 10 meters, and faced south, this would then read as “10N 0E 10a 90”.

Touch Devices

2026-01-10T06:38:35Z

Xan:

__NOEDITSECTION__
{{TOCright|clear=right}}
Touch and Pen Controls | Mobile Devices 
 

DeltaWorlds client browser version 6.2.0.1410 and later support Touch and Pen Controls, in particular useful for Mobile Devices such as smart phones and tablets.

==Touch Gestures==

[[File:TouchGesturesOverview1.png]]

DeltaWorlds uses ''Tap/Double Tap'', ''Panning'', ''Selection/Drag'', ''Press and Tap'', ''Zoom'', and ''Press and Hold'' gestures.

 
===Tap===

====Click====

''Tapping'' onto the screen triggers a single click, used to select from menu, activate an item of a list, change input focus, activate an action in world.

====Double Click====

''Tapping'' onto the 3D window twice quick triggers a double click, e.g. used cancel an ongoing action, such as object selection, terrain selection, or mouse-move modes.

====Right Click====

''Press and Hold'' gesture triggers a right click event, e.g. used to open context menus, to select an object, or pick terrain in world.

===Look around===

''Pan'' gestures are used to look around while ''mouse move mode'' (mouse icon in the toolbar) is deactivated.

Moving the finger from the center of the screen upwards is equal to look up.

Moving the finger from the center of the screen downwards is equal to look down.

Moving the finger from the center of the screen to the left is equal to turn left.

Moving the finger from the center of the screen to the right is equal to turn right.

Combinations of these while keeping the finger pressed are possible.

===Move around===

''Pan'' gestures are used to move around while ''mouse move mode'' (mouse icon in the toolbar) is activated.

If ''freelook'' was selected in the option settings, the behavior is the same as ''Look around''. Thus, ''freelook'' makes little sense for touch devices, default is freelook disabled.

Moving the finger from the center of the screen upwards moves the avatar forward.

Moving the finger from the center of the screen downwards moves the avatar backward.

Moving the finger from the center of the screen to the left moves the avatar to the left.

Moving the finger from the center of the screen to the right moves the avatar to the right.

Combinations of these while keeping the finger pressed are possible.

===Flying===

''Press and Tap'' gestures are used to fly up and down.

Press first finger to any point on the 3D window, tap second finger above the position of the first finger to fly up. Release fingers to stop flying up.

Press first finger to any point on the 3D window, tap second finger below the position of the first finger to fly down. Release fingers to stop flying down.

===Zoom Avatar===

''Zoom'' gestures are used to adjust the view distance to your avatar in world in 3rd person view.

The zoom gesture is sensitive and inertia is applied. The y-distance between fingers is used. Zoom slowly and hold both fingers down for a second.

===Web===

The integrated web browser supports all touch gestures, for docking web windows and for external web windows, as well as for popups.

Web rendered on panels in world, accept tap and pan gestures.

 
==Virtual Keyboard==

[[File:VirtualKeyboard1.png|640px]]

Windows devices on touch devices show an icon to the [http://windows.microsoft.com/en-US/windows-8/type-with-the-on-screen-keyboard virtual keyboard] in the task bar by default. It offers various options and styles, including handwriting.

It is particular useful to enter chat text, or action commands during building, as well as all modifier keys like Ctrl or Shift are available, useful to speed up move or to pass through objects. ActiveWorlds does not open the virtual keyboard automatically since it can use most of the screen space and thereby may cover the target field where you want to enter text into.

 
==Alternative Input Methods==

Alternative text input methods, like Microsoft's speech recognition that comes with Windows 7 and later, can be used for ActiveWorlds as well.

 
==Screen Orientation==

Most Mobile devices offer the feature to switch screen orientation by rotating the device. ActiveWorlds detects changes in screen orientation and will adjust itself to either landscape or portrait mode and switches back to maximized window.

 
==Touch/Pen Requirements==

''Required OS:'' Windows 7 or later

''Required CPU:'' Intel x86 or x64 or compatible – i.e. Intel Core, Intel ATOM, AMD

==Example Mobile Devices==
(excerpt, as of December 2014)

''Acer'' Aspire Switch (various), Iconia (various)

''ASUS'' VivoTab (various), Transformer Book (various)

''Dell'' Venue 8 Pro, Inspiron 11 3000,

''HP'' Stream 7/8, ENVY 15 x2, Pavilion x360 Series, Pavilion 10/13 x2

''Lenovo'' Miix 3, Yoga 3 Pro

''Microsoft'' Surface Pro 2, Surface Pro 3

''Toshiba'' Encore 2 (various), Encore Mini, Satellite Click 2 Pro

''... and many more ...''

Touch Devices

2026-01-10T06:37:58Z

Xan: Created page with "__NOEDITSECTION__ {{TOCright|clear=right}} Touch and Pen Controls | Mobile Devices ActiveWorlds client browser version 6.2.0.1410 and later support Touch and Pen Controls, in particular useful for Mobile Devices such as smart phones and tablets. ==Touch Gestures== File:TouchGesturesOverview1.png ActiveWorlds uses ''Tap/Double Tap'', ''Panning'', ''Selection/Drag'', ''Press and Tap'', ''Zoom'', and ''Press and Hold'' gestures. ===Tap=== ====Click=..."

__NOEDITSECTION__
{{TOCright|clear=right}}
Touch and Pen Controls | Mobile Devices 
 

ActiveWorlds client browser version 6.2.0.1410 and later support Touch and Pen Controls, in particular useful for Mobile Devices such as smart phones and tablets.

==Touch Gestures==

[[File:TouchGesturesOverview1.png]]

ActiveWorlds uses ''Tap/Double Tap'', ''Panning'', ''Selection/Drag'', ''Press and Tap'', ''Zoom'', and ''Press and Hold'' gestures.

 
===Tap===

====Click====

''Tapping'' onto the screen triggers a single click, used to select from menu, activate an item of a list, change input focus, activate an action in world.

====Double Click====

''Tapping'' onto the 3D window twice quick triggers a double click, e.g. used cancel an ongoing action, such as object selection, terrain selection, or mouse-move modes.

====Right Click====

''Press and Hold'' gesture triggers a right click event, e.g. used to open context menus, to select an object, or pick terrain in world.

===Look around===

''Pan'' gestures are used to look around while ''mouse move mode'' (mouse icon in the toolbar) is deactivated.

Moving the finger from the center of the screen upwards is equal to look up.

Moving the finger from the center of the screen downwards is equal to look down.

Moving the finger from the center of the screen to the left is equal to turn left.

Moving the finger from the center of the screen to the right is equal to turn right.

Combinations of these while keeping the finger pressed are possible.

===Move around===

''Pan'' gestures are used to move around while ''mouse move mode'' (mouse icon in the toolbar) is activated.

If ''freelook'' was selected in the option settings, the behavior is the same as ''Look around''. Thus, ''freelook'' makes little sense for touch devices, default is freelook disabled.

Moving the finger from the center of the screen upwards moves the avatar forward.

Moving the finger from the center of the screen downwards moves the avatar backward.

Moving the finger from the center of the screen to the left moves the avatar to the left.

Moving the finger from the center of the screen to the right moves the avatar to the right.

Combinations of these while keeping the finger pressed are possible.

===Flying===

''Press and Tap'' gestures are used to fly up and down.

Press first finger to any point on the 3D window, tap second finger above the position of the first finger to fly up. Release fingers to stop flying up.

Press first finger to any point on the 3D window, tap second finger below the position of the first finger to fly down. Release fingers to stop flying down.

===Zoom Avatar===

''Zoom'' gestures are used to adjust the view distance to your avatar in world in 3rd person view.

The zoom gesture is sensitive and inertia is applied. The y-distance between fingers is used. Zoom slowly and hold both fingers down for a second.

===Web===

The integrated web browser supports all touch gestures, for docking web windows and for external web windows, as well as for popups.

Web rendered on panels in world, accept tap and pan gestures.

 
==Virtual Keyboard==

[[File:VirtualKeyboard1.png|640px]]

Windows devices on touch devices show an icon to the [http://windows.microsoft.com/en-US/windows-8/type-with-the-on-screen-keyboard virtual keyboard] in the task bar by default. It offers various options and styles, including handwriting.

It is particular useful to enter chat text, or action commands during building, as well as all modifier keys like Ctrl or Shift are available, useful to speed up move or to pass through objects. ActiveWorlds does not open the virtual keyboard automatically since it can use most of the screen space and thereby may cover the target field where you want to enter text into.

 
==Alternative Input Methods==

Alternative text input methods, like Microsoft's speech recognition that comes with Windows 7 and later, can be used for ActiveWorlds as well.

 
==Screen Orientation==

Most Mobile devices offer the feature to switch screen orientation by rotating the device. ActiveWorlds detects changes in screen orientation and will adjust itself to either landscape or portrait mode and switches back to maximized window.

 
==Touch/Pen Requirements==

''Required OS:'' Windows 7 or later

''Required CPU:'' Intel x86 or x64 or compatible – i.e. Intel Core, Intel ATOM, AMD

==Example Mobile Devices==
(excerpt, as of December 2014)

''Acer'' Aspire Switch (various), Iconia (various)

''ASUS'' VivoTab (various), Transformer Book (various)

''Dell'' Venue 8 Pro, Inspiron 11 3000,

''HP'' Stream 7/8, ENVY 15 x2, Pavilion x360 Series, Pavilion 10/13 x2

''Lenovo'' Miix 3, Yoga 3 Pro

''Microsoft'' Surface Pro 2, Surface Pro 3

''Toshiba'' Encore 2 (various), Encore Mini, Satellite Click 2 Pro

''... and many more ...''

Moving Around

2026-01-10T06:36:35Z

Xan:

=== Beginner Keyboard Commands ===

After arriving in-world, you’ll want to begin exploring the world. This is done by using your keyboard. The following common movement controls are set as the default keys:

* Up Arrow: Walk forward
* Down Arrow: Walk backward
* Left Arrow: Turn Left
* Right Arrow: Turn Right
* Plus (+) symbol: Fly up
* Minus (-) symbol: Fly down
* Swimming begins automatically when you enter the water.
* Left mouse click: Activates an object. Objects can be activated when the mouse cursor turns to a hand.
* TAB: Quickly switch from the 3D view window to the chat box.

In addition to the basic movement keys, other keys will help you look around. These include:

*Page Up (PGUP): Look Up
*Page Down (PGDN): Look Down
*END key: Cycles through the various views, including first-person, chase (locked), chase, and front view. The chase views are the same thing as third person views.
*HOME key: Resets your view to first-person.
* * Key: Zooms in on your avatar.
* / Key: Zooms out on your avatar.

=== Intermediate Keyboard Commands ===

After learning the basic commands, there are a few key combinations that are commonly used throughout the software. These include:

* Shift + Up/Down: Using the Shift key while moving allows you to pass through objects. This is helpful if you get stuck inside of a model.
* Shift + Left/Right: Using the Shift key while pressing left or right will allow you to move sideways, or sidestep.
* Control (CTRL) + Up/Down: Using the Control key allows you to run at a faster pace.

== Advanced Movements ==

* Jumping: Although this is considered a basic movement, it is not pre-defined as such. To enable jumping, you must set a button in the Configure Controls box to use for jump. Typically, users set this to either the space bar or the 0/Ins key on the keypad. To jump, press this button. To jump higher, run forward while pressing this button. Many games in the Active Worlds universe use the jump button.
* Autowalk: The autowalk keys must be defined in the Configure Controls box as mentioned above. Autowalk enables your avatar to move without having to hold down the forward or backward keys. There are two keys that have to be defined:
* The Autowalk Key: This key begins automatic movement. To use this, hold down the up key and press the Autowalk key at the same time.
* The Stop Key: This key stops the automatic movement.

== Configuring the Controls ==
With most things in Active Worlds, the keyboard controls can be modified. To modify the keyboard controls, select Options in the menu bar, and then select Configure Controls.

Many gamers are used to using WASD type controls. These are also referred to as “Laptop” controls. To enable WASD, select the option “Reset to Laptop/Gaming defaults”.

The Keyboard Controls box allows you to change your keyboard layout. The first column defines the actions that can are possible. The second column is the first set of keys, and the third column is the second set of keys. To change your keyboard options, click on the button beside the actions you want to change. The buttons can also be mapped to a mouse, joystick, or game controller buttons.

== Mouse ==

Mouse movement: Many gamers are used to using the mouse to move around. This can easily be done within Active Worlds. To use the mouse to move around, first select your view by pressing the END key multiple times. Mouse movement is best used in the Chase, or Third Person view. Once you have your view selected, press and release the middle mouse button, or scroll wheel. You will see a white dot in the center of your screen. This is the focal point for the movement. With this, you can then use your mouse to look around while using the arrow keys (or WASD keys) to move around.

* Mouse Movement, Autowalk, and Running: To activate this key sequence is a little more complicated than simply walking forward. The steps involved are as follows:
** To walk normally: Switch your view to what is desired by pressing the END key on your keyboard, then, press the middle mouse button (scroll wheel) to enable mouse movement, then, press the Up arrow key to begin moving forward, then, while holding down the Up arrow key, press the Autowalk key that you defined to begin autowalk.
** To run: Switch your view to what is desired by pressing the END key on your keyboard, then, press the middle mouse button (scroll wheel) to enable mouse movement, then, hold down the Control Key while pressing the Up arrow key to begin moving forward, then, while holding down the Up arrow key, press the Autowalk key that you defined to begin autowalk.

Moving Around

2026-01-10T06:35:57Z

Xan: Created page with " == Keyboard == == Flying == === Beginner Keyboard Commands === After arriving in-world, you’ll want to begin exploring the world. This is done by using your keyboard. The following common movement controls are set as the default keys: * Up Arrow: Walk forward * Down Arrow: Walk backward * Left Arrow: Turn Left * Right Arrow: Turn Right * Plus (+) symbol: Fly up * Minus (-) symbol: Fly down * Swimming begins automatically when you enter the water. * Left mouse clic..."

== Keyboard ==
== Flying ==
=== Beginner Keyboard Commands ===

After arriving in-world, you’ll want to begin exploring the world. This is done by using your keyboard. The following common movement controls are set as the default keys:

* Up Arrow: Walk forward
* Down Arrow: Walk backward
* Left Arrow: Turn Left
* Right Arrow: Turn Right
* Plus (+) symbol: Fly up
* Minus (-) symbol: Fly down
* Swimming begins automatically when you enter the water.
* Left mouse click: Activates an object. Objects can be activated when the mouse cursor turns to a hand.
* TAB: Quickly switch from the 3D view window to the chat box.

In addition to the basic movement keys, other keys will help you look around. These include:

*Page Up (PGUP): Look Up
*Page Down (PGDN): Look Down
*END key: Cycles through the various views, including first-person, chase (locked), chase, and front view. The chase views are the same thing as third person views.
*HOME key: Resets your view to first-person.
* * Key: Zooms in on your avatar.
* / Key: Zooms out on your avatar.

=== Intermediate Keyboard Commands ===

After learning the basic commands, there are a few key combinations that are commonly used throughout the software. These include:

* Shift + Up/Down: Using the Shift key while moving allows you to pass through objects. This is helpful if you get stuck inside of a model.
* Shift + Left/Right: Using the Shift key while pressing left or right will allow you to move sideways, or sidestep.
* Control (CTRL) + Up/Down: Using the Control key allows you to run at a faster pace.

== Advanced Movements ==

* Jumping: Although this is considered a basic movement, it is not pre-defined as such. To enable jumping, you must set a button in the Configure Controls box to use for jump. Typically, users set this to either the space bar or the 0/Ins key on the keypad. To jump, press this button. To jump higher, run forward while pressing this button. Many games in the Active Worlds universe use the jump button.
* Autowalk: The autowalk keys must be defined in the Configure Controls box as mentioned above. Autowalk enables your avatar to move without having to hold down the forward or backward keys. There are two keys that have to be defined:
* The Autowalk Key: This key begins automatic movement. To use this, hold down the up key and press the Autowalk key at the same time.
* The Stop Key: This key stops the automatic movement.

== Configuring the Controls ==
With most things in Active Worlds, the keyboard controls can be modified. To modify the keyboard controls, select Options in the menu bar, and then select Configure Controls.

Many gamers are used to using WASD type controls. These are also referred to as “Laptop” controls. To enable WASD, select the option “Reset to Laptop/Gaming defaults”.

The Keyboard Controls box allows you to change your keyboard layout. The first column defines the actions that can are possible. The second column is the first set of keys, and the third column is the second set of keys. To change your keyboard options, click on the button beside the actions you want to change. The buttons can also be mapped to a mouse, joystick, or game controller buttons.

== Mouse ==

Mouse movement: Many gamers are used to using the mouse to move around. This can easily be done within Active Worlds. To use the mouse to move around, first select your view by pressing the END key multiple times. Mouse movement is best used in the Chase, or Third Person view. Once you have your view selected, press and release the middle mouse button, or scroll wheel. You will see a white dot in the center of your screen. This is the focal point for the movement. With this, you can then use your mouse to look around while using the arrow keys (or WASD keys) to move around.

* Mouse Movement, Autowalk, and Running: To activate this key sequence is a little more complicated than simply walking forward. The steps involved are as follows:
** To walk normally: Switch your view to what is desired by pressing the END key on your keyboard, then, press the middle mouse button (scroll wheel) to enable mouse movement, then, press the Up arrow key to begin moving forward, then, while holding down the Up arrow key, press the Autowalk key that you defined to begin autowalk.
** To run: Switch your view to what is desired by pressing the END key on your keyboard, then, press the middle mouse button (scroll wheel) to enable mouse movement, then, hold down the Control Key while pressing the Up arrow key to begin moving forward, then, while holding down the Up arrow key, press the Autowalk key that you defined to begin autowalk.

Category:SDK

2025-04-07T19:29:12Z

Xan: Created page with "Meta category holding all documentation related to the SDK. No SDK method or property articles should be categorized in here. Category:Software"

Meta category holding all documentation related to the [[SDK]]. No SDK method or property articles should be categorized in here.

[[Category:Software]]

AW AVATAR SESSION

2025-04-07T19:28:23Z

Xan: Created page with "{{SDK added in|version=2.1|sort=a|sdk=13|world=|universe=|browser=}} __NOTOC__ {{SUBPAGENAMEE}} ==Type== Integer (read only) ==Description== Session number of a user for which an event or callback was triggered (mostly avatar-related). ==Notes== Every user is assigned a unique session number at login. This session number can be used by SDK applications to track individual users as they move around the scene. Note that a new session number is assigned on every logi..."

{{SDK added in|version=2.1|sort=a|sdk=13|world=|universe=|browser=}}

__NOTOC__

{{SUBPAGENAMEE}}

==Type==
Integer (read only)

==Description==
Session number of a user for which an event or callback was triggered (mostly avatar-related).

==Notes==
Every user is assigned a unique session number at login. This session number can be used by SDK applications to track individual users as they move around the scene.

Note that a new session number is assigned on every login. This means that for example if a user exits and then re-enters then it will appear with a new session number even though its the same user as before. Changing privileges will also cause a relogin, meaning that the assigned session number will change.

==Range==
{{SDK range|minimum=1|maximum=65335|default=}}

==Usage==
void handle_avatar_add (void)
{
printf ("%s has session number %d\n",
[[aw_string]] ([[AW_AVATAR_NAME]]),
[[aw_int]] ([[AW_AVATAR_SESSION]]));
}

[[aw_event_set]] ([[AW_EVENT_AVATAR_ADD]], handle_avatar_add);

==Used by==
*[[AW_CALLBACK_ADDRESS]]
*[[AW_CALLBACK_AVATAR_LOCATION]]
*[[AW_EVENT_AVATAR_ADD]]
*[[AW_EVENT_AVATAR_CHANGE]]
*[[AW_EVENT_AVATAR_CLICK]]
*[[AW_EVENT_AVATAR_DELETE]]
*[[AW_EVENT_AVATAR_RELOAD]]
*[[AW_EVENT_ENTITY_RIDER_ADD]]
*[[AW_EVENT_ENTITY_RIDER_CHANGE]]
*[[AW_EVENT_ENTITY_RIDER_DELETE]]
*[[AW_EVENT_OBJECT_BUMP]]
*[[AW_EVENT_OBJECT_CLICK]]
*[[AW_EVENT_OBJECT_SELECT]]
*[[AW_EVENT_URL]]
*[[AW_EVENT_URL_CLICK]]

==See also==
*[[aw_address]]
*[[aw_avatar_set]]
*[[aw_url_click]]
*[[aw_url_send]]
*[[aw_avatar_location]]
*[[aw_avatar_reload]]

[[Category: SDK Attributes|A]]

AW CALLBACK ADDRESS

2025-04-07T19:28:07Z

Xan: Created page with "{{SDK added in|version=2.2|sdk=14|world=21|universe=|browser=303}} __NOTOC__ {{SUBPAGENAMEE}} ==Attributes== ;AW_AVATAR_SESSION:Queried session number; this is useful for determining which callback is for which request if multiple asynchronous calls to aw_address are outstanding. ;AW_AVATAR_ADDRESS (1):Specifies the IP address of the user, in network byte order. '''(1)''' If the reason code is RC_SUCCESS. ==Used by== *a..."

{{SDK added in|version=2.2|sdk=14|world=21|universe=|browser=303}}

__NOTOC__

{{SUBPAGENAMEE}}

==Attributes==
;[[AW_AVATAR_SESSION]]:Queried session number; this is useful for determining which callback is for which request if multiple asynchronous calls to [[aw_address]] are outstanding.
;[[AW_AVATAR_ADDRESS]] (1):Specifies the IP address of the user, in network byte order.

'''(1)''' If the reason code is [[SDK Reason Codes#RC_SUCCESS|RC_SUCCESS]].

==Used by==
*[[aw_address]]

[[Category: SDK Callbacks|A]]

Aw wait

2025-04-07T19:27:37Z

Xan: Created page with "{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}} __NOTOC__ int aw_wait (int <var>milliseconds</var>) ==Description== Processes all queued packets and waits the specified time for more to arrive, calling callback and event handlers. ==Callback== None ==Notes== Placing calls to this method from callback or event handlers should be avoided. The reason for this being that it will in turn call such handlers. Which would cause aw_wait to indirectly call itse..."

{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}}

__NOTOC__

int aw_wait (int <var>milliseconds</var>)

==Description==
Processes all queued packets and waits the specified time for more to arrive, calling callback and event handlers.

==Callback==
None

==Notes==
Placing calls to this method from callback or event handlers should be avoided. The reason for this being that it will in turn call such handlers. Which would cause aw_wait to indirectly call itself (e.g. aw_wait calls handler, handler calls aw_wait, repeat).

'''For version 4.1 and later:''' This method will deallocate [[SDK_Multiple_Instances|instances]] that have been flagged as destroyed by [[aw_destroy]]. This is done before each iteration of processing packets for all the instances. If an application places a call to [[aw_destroy]] followed by aw_wait within a callback or event handler then it could cause the SDK to dereference a pointer to freed memory.

===Blocking calls===
It helps to think of blocking calls to SDK methods as placing an implicit call to aw_wait. That is, calls that have a callback but none has been registered. A blocking call will process all packets until it receives the result. This includes packets bound for other instances. The majority of these methods look like this:

int [[aw_address]] (int session_id)
{
/* check if RC_NOT_INITIALIZED, RC_NO_INSTANCE or RC_NO_CONNECTION should be returned */
...

/* send PACKET_GET_ADDRESS to the world server */
...

/*
if this is an asynchronous call then immediately return RC_SUCCESS indicating
that the request has been _sent_ successfully.
*/
if ([[aw_callback]] ([[AW_CALLBACK_ADDRESS]]) != NULL)
return RC_SUCCESS;

/*
wait at most 18 seconds (or return RC_TIMEOUT) for a result to PACKET_ADDRESS to come
in for the current instance processing all packets in the meantime, calling event and
callback handlers.
*/
return _aw_wait (18000, PACKET_ADDRESS);
}

That blocking SDK methods can call event and callback handlers has implications. '''The rule of thumb is:''' Never place blocking SDK method calls in an event or callback handler. It requires in-depth knowledge to know when this is safe.

For example, assume that a blocking call has been placed from within an event handler. If the event is triggered multiple times while the blocking call waits for a result then it will lead to the following problems:

Problem #1:
:The first blocking call would call the event handler, which places a second blocking call. The second call must return before the first one can return. It is possible that the event is received again while the second call waits, which places a third blocking call. The third call must return before the second one can return. If more events than results are received then the call depth will increase.

Problem #2:
:Assume that problem #1 occurs and leads to a big call depth. If less events than results are received then the call depth will decrease. There might be calls that will time-out due to having waited more than 18 seconds.

Problem #3:
:Results will arrive in the same order that calls were placed. If there are multiple blocking calls waiting for results then the most recent call will receive the oldest result.

==Arguments==
'''If <var>milliseconds</var> is 0''' then it will process any queued packets and return. This is typically used in single-threaded GUI applications. Where a timer is used to call this method repeatedly. A wait of around 100 ms (1000 / AW_MAX_AVCHANGE_PER_SECOND) or less between each call is recommended. See [http://msdn2.microsoft.com/en-us/library/ms644906.aspx SetTimer] for Windows applications.

void CALLBACK TimerProc (
HWND hWnd, // handle of window for timer messages
UINT nMsg, // WM_TIMER message
UINT nIDEvent, // timer identification
DWORD dwTime) // current system time
{
[[aw_wait]] (0); /* process any queued packets and return */
}

/* put this together with the rest of the intialization code */
[[aw_init]] (AW_BUILD);
SetTimer (NULL, 0, 100, TimerProc); /* call aw_wait at 100 millisecond intervals */

'''If <var>milliseconds</var> is less than 0''' then it will keep processing packets forever (or until [[aw_term]] is called, which is not recommended). This is typically used in simple console applications. Where any input comes through the SDK. In the form of events like [[AW_EVENT_CHAT|chat]], [[AW_EVENT_OBJECT_CLICK|object clicks]], and so forth.

[[aw_wait]] (-1); /* this will never return */

'''If <var>milliseconds</var> is more than 0''' then it will process packets until it that amount of time has passed (or until [[aw_term]] is called, which is not recommended). This makes it possible to periodically check for input from a user. Or to perform an action at certain intervals. For example, use [[aw_say]] to say something out loud every minute. Like this,

/* say "A minute has passed" every minute */
while (1)
{
[[aw_wait]] (60000); /* wait 60,000 milliseconds, or 60 seconds */
[[aw_say]] ("A minute has passed");
}

This example checks for keyboard input at 100 millisecond intervals:

while (1)
{
[[aw_wait]] (100); /* wait 100 milliseconds */
if (_kbhit ())
{
int ch = _getch ();

/* if 'q' was pressed then quit */
if (_tolower (ch) == 'q')
break;

/* if 't' was pressed then print the tick count */
if (_tolower (ch) == 't')
printf ("Ticks: %u\n", [[aw_tick]] ());
}
}

Note, if [[aw_init]] has not been called (or [[aw_term]] has been called) then the call will return immediately.

==Argument attributes==
None

==Return values==
;[[SDK Reason Codes#RC_SUCCESS|RC_SUCCESS]]:
;[[SDK Reason Codes#RC_NOT_INITIALIZED|RC_NOT_INITIALIZED]]:If the milliseconds argument is 0 and aw_init has not been called (or aw_term has been called).

==Returned attributes==
None

==See also==
*[[SDK_Application_Structure|Application structure]]
*[[aw_event_set]]
*[[aw_callback_set]]

[[Category: SDK Methods|W]]

Mover Control example code

2025-04-07T19:26:50Z

Xan: Created page with "<pre> /*----------------------------------------------------------------------------- M o v e r C o n t r o l Copyright 2007 Activeworlds Inc Licensed Material -- Program Property of Activeworlds Inc. -----------------------------------------------------------------------------*/ #define MAX_MODEL_NAME 64 #define WAIT_TIME 10 // time to wait for SDK packets and events before update #defin..."

<pre>
/*-----------------------------------------------------------------------------
M o v e r C o n t r o l
Copyright 2007 Activeworlds Inc
Licensed Material -- Program Property of Activeworlds Inc.
-----------------------------------------------------------------------------*/

#define MAX_MODEL_NAME 64
#define WAIT_TIME 10 // time to wait for SDK packets and events before update
#define WAYPOINT_RESOLUTION 1 // accuracy, interpolates waypoint (1 to 10) - use as low as possible!
#define UPDATE_INTERVAL (1000 / (aw_int (AW_WORLD_AVATAR_REFRESH_RATE) * WAYPOINT_RESOLUTION))
#define IDLE_INTERVAL ((aw_int (AW_WORLD_MOVER_USED_RESET_TIMEOUT) * 1000) / 2)
#define STATE_INVALIDATE -1 // invalidate mover's state
#define MAX_WAYPOINTS 16 // number of elements in "waypoints" array

// announced messages
#define START_MSG "Bus started."
#define STOP_MSG "Bus stopped. Please leave the bus."
#define READY_MSG "Passengers are welcome! Bus will start in 15 seconds."
#define POSTPONE_MSG "Tour postponed by 15 seconds. Passengers are welcome!"
#define RIDER_ADDED_WHISPER "You joined the bus tour."
#define RIDER_DELETED_WHISPER "You left the bus tour."

#include "aw.h"
#include <windows.h>
#include <stdio.h>
#include <time.h>

struct {
int x;
int y;
int z;
int yaw;
int pitch;
int roll;
} waypoints[MAX_WAYPOINTS] = {
// X Y Z YAW PITCH ROLL
{0, 0, 0, 0, 0, 0},
{0, 100, 500, 0, -16, 32},
{500, 400, 1000, 160, -32, 64},
{1000, 300, 1500, 280, -16, 128},
{1500, 200, 2000, 360, -16, 64},
{2000, 0, 2000, 450, 0, -128},
{1000, 200, 2500, -450, -16, -256},
{500, 400, 3000, -300, -16, -64},
{0, 900, 3500, -215, -32, -32},
{0, 400, 4000, 0, -32, 0},
{0, 0, 4200, 0, -16, 0},
{0, 900, 4000, 900, -180, 180},
{500, 1500, 2000, 2400, -360, 360},
{-1500, 900, 500, 1200, 180, -90},
{-800, 400, -900, 0, 32, -32},
{0, 0, 0, 0, 0, 0},
};

struct rider {
int session;
struct rider* next;
};

struct mover {
unsigned int id;
int state;
int init_x;
int init_y;
int init_z;
int init_yaw;
int init_pitch;
int init_roll;
int cur_x;
int cur_y;
int cur_z;
int cur_yaw;
int cur_pitch;
int cur_roll;
unsigned int start;
unsigned int last_update;
unsigned int last_move;
float last_waypoint;
int rider_count;
struct rider* riders;
struct mover* next;
};

static struct mover* movers = NULL;
static int mv_owner = 0;
static char mv_model[MAX_MODEL_NAME];

void log_msg (char* format, ...)
{

va_list args;
struct tm* now;
time_t secs;
char buffer[1024];

time (&secs);
now = localtime (&secs);
strftime (buffer, sizeof (buffer), "%y-%m-%d %X ", now);
printf (buffer);

va_start (args, format);
__try {
vsprintf (buffer, format, args);
}
__except( EXCEPTION_EXECUTE_HANDLER ) {
return;
}
va_end (args);
puts (buffer);

}

void announce (char* format, ...)
{

va_list args;
char buffer[1024];

va_start (args, format);
__try {
vsprintf (buffer, format, args);
}
__except( EXCEPTION_EXECUTE_HANDLER ) {
return;
}
va_end (args);
aw_say (buffer);
log_msg ("announce : \"%s\"", buffer);
}

BOOL rider_add (unsigned int id, int session)
{

struct mover* mv;
struct rider* rd;
BOOL exists;

if (session == aw_session ())
return TRUE; // dont add own session

for (mv = movers; mv; mv = mv->next)
if (mv->id == id)
break;
if (!mv)
return FALSE;

for (exists = FALSE, rd = mv->riders; rd; rd = rd->next)
if (rd->session == session) {
exists = TRUE;
break; // exists already
}

if (!rd
&& !(rd = (struct rider*)calloc (1, sizeof (struct rider))))
return FALSE;

rd->session = session;

if (!exists) {
if (mv->riders)
rd->next = mv->riders;
mv->riders = rd;
mv->rider_count++;
aw_whisper (session, RIDER_ADDED_WHISPER);
}
return TRUE;

}

BOOL rider_del (unsigned int id, int session)
{

struct mover* mv;
struct rider* rd;
struct rider* prev;

for (mv = movers; mv; mv = mv->next)
if (mv->id == id)
break;
if (!mv)
return FALSE; // mover does not exist

for (prev = NULL, rd = mv->riders; rd; rd = rd->next) {
if (rd->session == session)
break;
prev = rd;
}
if (!rd)
return FALSE;
if (prev)
prev->next = rd->next;
else
movers->riders = rd->next;
free (rd);
mv->rider_count--;
aw_whisper (session, RIDER_DELETED_WHISPER);
return TRUE;

}

BOOL mover_add (unsigned int id, int state, int x, int y, int z,
int yaw, int pitch, int roll)
{

struct mover* mv;
BOOL exists;

if (movers)
return FALSE; // this bot controls one mover only!

for (exists = FALSE, mv = movers; mv; mv = mv->next)
if (mv->id == id) {
exists = TRUE;
break; // exists already
}

if (!mv
&& !(mv = (struct mover*)calloc (1, sizeof (struct mover))))
return FALSE;

mv->id = id;
mv->init_x = x;
mv->init_y = y;
mv->init_z = z;
mv->init_yaw = yaw;
mv->init_pitch = pitch;
mv->init_roll = roll;
mv->cur_x = waypoints[0].x;
mv->cur_y = waypoints[0].y;
mv->cur_z = waypoints[0].z;
mv->cur_yaw = waypoints[0].yaw;
mv->cur_pitch = waypoints[0].pitch;
mv->cur_roll = waypoints[0].roll;
mv->last_waypoint = 0.0f;
mv->start = aw_tick ();
mv->state = state;

if (!exists) {
if (movers)
mv->next = movers;
movers = mv;
}
return TRUE;

}

BOOL mover_change (unsigned int id, int state, int x, int y, int z,
int yaw, int pitch, int roll)
{

struct mover* mv;

for (mv = movers; mv; mv = mv->next)
if (mv->id == id)
break;
if (!mv)
return FALSE;

mv->state = state;

if (state == AW_MOVER_STATE_RESET) {
mv->cur_x = waypoints[0].x;
mv->cur_y = waypoints[0].y;
mv->cur_z = waypoints[0].z;
mv->cur_yaw = waypoints[0].yaw;
mv->cur_pitch = waypoints[0].pitch;
mv->cur_roll = waypoints[0].roll;
mv->last_waypoint = 0.0f;
mv->start = aw_tick ();
}

return TRUE;

}

BOOL mover_del (unsigned int id)
{

struct mover* mv;
struct mover* prev;
struct rider* rd;
struct rider* rd_tmp;

for (prev = NULL, mv = movers; mv; mv = mv->next) {
if (mv->id == id)
break;
prev = mv;
}
if (!mv)
return FALSE;
for (rd = mv->riders; rd; ) {
rd_tmp = rd;
rd = rd->next;
free (rd_tmp);
}
mv->riders = NULL;
if (prev)
prev->next = mv->next;
else
movers = mv->next;
free (mv);
return TRUE;

}

void reset ()
{

struct mover* mv;
struct mover* mv_tmp;
struct rider* rd;
struct rider* rd_tmp;

for (mv = movers; mv; ) {
for (rd = mv->riders; rd; ) {
rd_tmp = rd;
rd = rd->next;
free (rd_tmp);
}
mv_tmp = mv;
mv = mv->next;
free (mv_tmp);
}
movers = NULL;

}

void handle_entity_add (void)
{

if (aw_int (AW_ENTITY_TYPE) == AW_ENTITY_MOVER
&& aw_int (AW_ENTITY_ID)
&& aw_int (AW_ENTITY_OWNER_CITIZEN) == mv_owner
&& !stricmp (aw_string (AW_OBJECT_MODEL), mv_model)) {
if (mover_add (aw_int (AW_ENTITY_ID), aw_int (AW_ENTITY_STATE),
aw_int (AW_OBJECT_X), aw_int (AW_OBJECT_Y), aw_int (AW_OBJECT_Z),
aw_int (AW_OBJECT_YAW), aw_int (AW_OBJECT_TILT), aw_int (AW_OBJECT_ROLL))) {
// Reset the mover in case it's used (causes mover to blick 10 seconds)
if (aw_int (AW_ENTITY_STATE) != AW_MOVER_STATE_IDLE)
aw_mover_set_state (aw_int (AW_ENTITY_ID), AW_MOVER_STATE_RESET, 0);

log_msg ("Mover ADD: %u %s", aw_int (AW_ENTITY_ID), aw_string (AW_OBJECT_MODEL));
}

}

}

void handle_entity_change (void)
{

if (mover_change (aw_int (AW_ENTITY_ID), aw_int (AW_ENTITY_STATE),
aw_int (AW_ENTITY_X), aw_int (AW_ENTITY_Y), aw_int (AW_ENTITY_Z),
aw_int (AW_ENTITY_YAW), aw_int (AW_ENTITY_PITCH), aw_int (AW_ENTITY_ROLL))) {
// Reset the mover when bot isn't owner! (somewhere else is using it)
if (aw_int (AW_ENTITY_STATE) != AW_MOVER_STATE_RESET
&& aw_int (AW_ENTITY_STATE) != AW_MOVER_STATE_IDLE
&& aw_int (AW_ENTITY_OWNER_SESSION) != aw_session ())
aw_mover_set_state (aw_int (AW_ENTITY_ID), AW_MOVER_STATE_RESET, 0);
log_msg ("Mover CHG: %u state: %d", aw_int (AW_ENTITY_ID), aw_int (AW_ENTITY_STATE));
}

}

void handle_entity_delete (void)
{

if (mover_del (aw_int (AW_ENTITY_ID)))
log_msg ("Mover DEL: %u", aw_int (AW_ENTITY_ID));

}

void handle_entity_rider_add (void)
{

if (rider_add (aw_int (AW_ENTITY_ID), aw_int (AW_AVATAR_SESSION)))
log_msg ("Rider ADD: %u session# %d", aw_int (AW_ENTITY_ID), aw_int (AW_AVATAR_SESSION));

}

void handle_entity_rider_change (void)
{

if (rider_add (aw_int (AW_ENTITY_ID), aw_int (AW_AVATAR_SESSION)))
log_msg ("Rider CHG: %u session# %d", aw_int (AW_ENTITY_ID), aw_int (AW_AVATAR_SESSION));

}

void handle_entity_rider_delete (void)
{

if (rider_del (aw_int (AW_ENTITY_ID), aw_int (AW_AVATAR_SESSION)))
log_msg ("Rider DEL: %u session# %d", aw_int (AW_ENTITY_ID), aw_int (AW_AVATAR_SESSION));

}

void handle_enter (int rc)
{

reset ();
if (rc) {
log_msg ("world enter failed [%d]", rc);
return;
}

// announce our position in the world
aw_int_set (AW_MY_X, 0); // 0W
aw_int_set (AW_MY_Y, 0); // 0a
aw_int_set (AW_MY_Z, 0); // 0N
aw_int_set (AW_MY_YAW, 0); // facing south
aw_int_set (AW_MY_PITCH, 0);
if (rc = aw_state_change ()) {
log_msg ("Unable to change state (reason %d)", rc);
exit (1);
}

log_msg ("%s entered world %s",
aw_string (AW_LOGIN_NAME), aw_string (AW_WORLD_NAME));

}

void handle_world_disconnect (void)
{

reset ();
log_msg ("world disconnected [%d]", aw_int (AW_DISCONNECT_REASON));

}

void pause (int id)
{

aw_mover_set_state (id, AW_MOVER_STATE_PAUSE, 0);

}

void start (int id)
{

struct mover* mv;
struct rider* rd;
int num_riders;
int angle;

aw_mover_set_state (id, AW_MOVER_STATE_CONTINUE, 0);

// optionally position all riders to their seats,
// starting with world build 86 and browser build 969
for (mv = movers; mv; mv = mv->next)
if (mv->id == (unsigned int)id)
break;
if (!mv)
return;
for (num_riders = 0, rd = mv->riders; rd; rd = rd->next)
num_riders++;
for (angle = 0, rd = mv->riders; rd; rd = rd->next) {
aw_mover_rider_change (aw_int (AW_ENTITY_ID), rd->session, 100, angle, -35, 1800, 0);
angle += 3600 / num_riders;
log_msg ("Rider %d changed to riding position", rd->session);
}

}

void move_to (struct mover* mv)
{

int interval;
int wp;
int dx;
int dy;
int dz;
int dyaw;
int dpitch;
int droll;

interval = aw_int (AW_WORLD_AVATAR_REFRESH_RATE) * WAYPOINT_RESOLUTION;
wp = (int)mv->last_waypoint;
if (wp < 0 || wp >= MAX_WAYPOINTS)
wp = 0;

if (wp) {
dx = mv->cur_x + ((waypoints[wp].x - waypoints[wp - 1].x) / interval);
dy = mv->cur_y + ((waypoints[wp].y - waypoints[wp - 1].y) / interval);
dz = mv->cur_z + ((waypoints[wp].z - waypoints[wp - 1].z) / interval);
dyaw = mv->cur_yaw + ((waypoints[wp].yaw - waypoints[wp - 1].yaw) / interval);
dpitch = mv->cur_pitch + ((waypoints[wp].pitch - waypoints[wp - 1].pitch) / interval);
droll = mv->cur_roll + ((waypoints[wp].roll - waypoints[wp - 1].roll) / interval);
} else {
dx = waypoints[wp].x;
dy = waypoints[wp].y;
dz = waypoints[wp].z;
dyaw = waypoints[wp].yaw;
dpitch = waypoints[wp].pitch;
droll = waypoints[wp].roll;
}
mv->cur_x = dx;
mv->cur_y = dy;
mv->cur_z = dz;
mv->cur_yaw = dyaw;
mv->cur_pitch = dpitch;
mv->cur_roll = droll;

aw_mover_set_position (mv->id,
mv->init_x + dx, mv->init_y + dy, mv->init_z + dz,
mv->init_yaw + dyaw, mv->init_pitch + dpitch, mv->init_roll + droll);

mv->last_move = aw_tick ();

log_msg ("Mover MOV: %u delta: %d %d %d %d %d %d", mv->id,
dx, dy, dz, dyaw, dpitch, droll);

}

void idle (struct mover* mv)
{

if (mv->last_move + IDLE_INTERVAL < aw_tick ())
move_to (mv);

}

int update ()
{

struct mover* mv;
struct rider* rd;
int count;
unsigned int frame_time;

for (count = 0, mv = movers; mv; mv = mv->next) {

if (!mv->start
|| mv->last_update + UPDATE_INTERVAL > aw_tick ())
continue;

frame_time = aw_tick () - mv->start;
// log_msg ("UPDATE : %u state %d dt %d", mv->id, mv->state, frame_time);

if (mv->state != AW_MOVER_STATE_PAUSE
&& mv->state != AW_MOVER_STATE_MOVE) {
if (mv->state != AW_MOVER_STATE_IDLE)
continue;
// Set state to Pause, so other users can join in
pause (mv->id);
mv->state = STATE_INVALIDATE; // invalidate state
// Move to first waypoint
mv->last_waypoint = 0.0f;
move_to (mv);
// Add bot as driver to first mover
if (mv == movers)
aw_mover_rider_add (mv->id, aw_session (), 450, 1800, -30, 1800, 0);
mv->start = aw_tick ();
announce (READY_MSG);
continue;
}
idle (mv); // see if we have to send pos to prevent timeout
if (frame_time < 15000) {
// wait to get ready or something else?
continue;
} else if (mv->last_waypoint >= 0.0f) {
if (mv->state != AW_MOVER_STATE_MOVE
&& mv->state != STATE_INVALIDATE) {
if (mv->rider_count <= 0) {
mv->start = aw_tick ();
announce (POSTPONE_MSG);
continue;
}
start (mv->id);
mv->state = STATE_INVALIDATE; // invalidate state
announce (START_MSG);
} else if (mv->state == AW_MOVER_STATE_MOVE) {
mv->last_waypoint += 1.0f / (float)(aw_int (AW_WORLD_AVATAR_REFRESH_RATE) * WAYPOINT_RESOLUTION);
if (mv->last_waypoint >= MAX_WAYPOINTS)
mv->last_waypoint = 0.0f;
move_to (mv);
count++;
if (mv->last_waypoint == 0.0f)
mv->last_waypoint = -1.0f;
}
} else if (mv->last_waypoint < 0.0f && mv->state == AW_MOVER_STATE_MOVE) {
// Don't pause before mover has reached the last waypoint,
if (mv->last_update + (2000 / aw_int (AW_WORLD_AVATAR_REFRESH_RATE)) < aw_tick ()) {
pause (mv->id);
mv->state = STATE_INVALIDATE; // invalidate state
announce (STOP_MSG);
} else
continue;
} else if (mv->last_waypoint < 0.0f && mv->state == AW_MOVER_STATE_PAUSE) {
for (rd = mv->riders; rd; rd = rd->next)
if (rd->session != aw_session ())
aw_mover_rider_delete (mv->id, rd->session);
mv->start = aw_tick ();
mv->last_waypoint = 0.0f;
announce (READY_MSG);
count++;
}
mv->last_update = aw_tick ();
}

return count;

}

main (int argc, char *argv[])
{

int rc;
int owner;
char* pw;
char* world;

// check command line
if (argc < 4) {
log_msg ("Usage: %s citnumber password world", argv[0]);
exit (1);
}

// initialize Active Worlds API
if (rc = aw_init (AW_BUILD)) {
log_msg ("Unable to initialize API (reason %d)", rc);
exit (1);
}

// install handler for callbacks and events
aw_callback_set (AW_CALLBACK_ENTER, handle_enter);
aw_event_set (AW_EVENT_WORLD_DISCONNECT, handle_world_disconnect);

aw_event_set (AW_EVENT_ENTITY_ADD, handle_entity_add);
aw_event_set (AW_EVENT_ENTITY_CHANGE, handle_entity_change);
aw_event_set (AW_EVENT_ENTITY_DELETE, handle_entity_delete);
aw_event_set (AW_EVENT_ENTITY_RIDER_ADD, handle_entity_rider_add);
aw_event_set (AW_EVENT_ENTITY_RIDER_DELETE, handle_entity_rider_delete);
aw_event_set (AW_EVENT_ENTITY_RIDER_CHANGE, handle_entity_rider_change);

// create bot instance
if (rc = aw_create ("", 0, 0)) {
log_msg ("Unable to create bot instance (reason %d)", rc);
exit (1);
}

owner = atoi (argv[1]);
pw = argv[2];
world = argv[3];

// log bot into the universe
aw_int_set (AW_LOGIN_OWNER, owner);
aw_string_set (AW_LOGIN_PRIVILEGE_PASSWORD, pw);
aw_string_set (AW_LOGIN_APPLICATION, "MoverControlSample");
aw_string_set (AW_LOGIN_NAME, "MoverControl");
if (rc = aw_login ()) {
log_msg ("Unable to login (reason %d)", rc);
exit (1);
}

log_msg ("Successfully logged into Universe");

strcpy (mv_model, "trolly.rwx");
mv_owner = 101;

// log bot into the world
if (rc = aw_enter (world)) {
log_msg ("Unable to enter world (reason %d)", rc);
exit (1);
}

log_msg ("Successfully entered World %s", world);

// main event loop
while (!aw_wait (WAIT_TIME))
update ();

// close everything
aw_destroy ();
aw_term ();
return 0;

}

/*-----------------------------------------------------------------------------
E O F
-----------------------------------------------------------------------------*/
</pre>

[[Category: SDK]]

Aw tick

2025-04-07T19:26:19Z

Xan: Created page with "{{SDK added in|version=4.1|sdk=53|world=|universe=|browser=}} __NOTOC__ unsigned int aw_tick (void) ==Description== Returns the number of milliseconds that have elapsed since the SDK was initialized. ==Callback== None (returns immediately) ==Notes== This method provides a high precision reference time for time critical operations or application timers. The degree of precision depends largely on the operating system being used. :{| border cellpadding=4 cellspacing=..."

{{SDK added in|version=4.1|sdk=53|world=|universe=|browser=}}

__NOTOC__

unsigned int aw_tick (void)

==Description==
Returns the number of milliseconds that have elapsed since the SDK was initialized.

==Callback==
None (returns immediately)

==Notes==
This method provides a high precision reference time for time critical operations or application timers. The degree of precision depends largely on the operating system being used.

:{| border cellpadding=4 cellspacing=0
|- valign=bottom align=left
!Precision (1) !!Operating system
|-
| 1 ms || Linux variants
|-
| 1 ms || Windows Vista
|-
| ~10 ms || Windows 2000, Windows XP and Windows 2003
|-
| ~15 ms || Windows NT 3.1
|-
| ~50 ms || Windows 95, Windows 98 and Windows ME
|}

'''(1)''' Precision is defined as the smallest difference between tick counts from successive calls to this method.

The return value is always equal to or larger than one from a previous call, with one exception. As it is only a 32-bit number it will wrap around to zero after 49.7 days (or 0xFFFFFFFF milliseconds). This has the potential to cause problems in bots that run for extended periods.

==Arguments==
None

==Argument attributes==
None

==Return values==
Number of milliseconds that have elapsed since [[aw_init]] or [[aw_init_bind]] was called.

==Returned attributes==
None

==Usage==
while (1)
{
[[aw_wait]] (1);
/*
The tick count is likely to go past 1000000 without assuming that exact value.
It is not possible to use the == operator to test for a particular tick count.
*/
if ([[aw_tick]] () >= 1000000)
{
puts ("One million milliseconds have elapsed since the SDK was initialized!");
break;
}
}

==See also==
*[[Mover Control example code]]
*[[aw_init]]
*[[aw_init_bind]]

[[Category: SDK Methods|T]]

Aw random

2025-04-07T19:26:01Z

Xan: Created page with "{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}} __NOTOC__ int aw_random (void) ==Description== Returns a random number. ==Notes== The psuedo-random number generator (PRNG) employed by this method is [http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html Mersenne Twister] (MT) by Matsumoto and Nishimura. It sets new standards for the period, quality and speed of random number generators. The incredible period is 219937 - 1, a number with about 6000 d..."

{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}}

__NOTOC__

int aw_random (void)

==Description==
Returns a random number.

==Notes==
The psuedo-random number generator (PRNG) employed by this method is [http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html Mersenne Twister] (MT) by Matsumoto and Nishimura. It sets new standards for the period, quality and speed of random number generators. The incredible period is 219937 - 1, a number with about 6000 digits. The 32-bit random numbers exhibit best possible equidistribution properties in dimensions up to 623 and it's very fast.

===Predictability===
This PRNG is should '''not''' be used in cryptography as it has major vulnerabilities:

*Observing a sufficiently long sequence of outputs from MT is enough to predict all future outputs.
*It takes many iterations before the initial non-random state produces output that will pass a randomness test.

Two steps can be taken to mitigate the problems:

*Generate multiple 32-bit outputs (e.g. 8 would be sufficient) and digest them using a [http://en.wikipedia.org/wiki/Cryptographic_hash_function cryptographic hash function] such as RIPEMD or SHA-1.
*Throw away the first x number of outputs from MT (e.g. call aw_random a million times when the SDK application is initialized).

===Seed search attack===
The implementation used in the SDK is also vulnurable to a "seed search attack" due to only using a 32-bit number for the seed (i.e. it can only produce 2^32 different sequences of psedo-random numbers). This means that attackers would need to try at most 2^32 different seeds before finding the one being used.

If a large number of initial outputs of MT have been thrown away then attackers would need to generate a longer sequence of numbers to test each seed. If 1,000,000 numbers were thrown away and 1000 have been passed to users then an attacker would need to generate roughly 1001000 * 2^32 numbers to be sure of finding the correct seed (in addition to seeding 2^32 times).

==Arguments==
None

==Argument attributes==
None

==Return values==
Signed 32-bit number (i.e. a range of -2147483648 to +2147483647).

==Returned attributes==
None

==Usage==

Naive

if ([[aw_random]] () == 547891)
puts ("You sure are lucky");

Better

void random_init (void)
{
int i;

for (i = 0; i < 1000000; i++)
[[aw_random]] ();
}

int random_secure (void)
{
int n;
int i;

n = 0;

/*
combine multiple outputs into a single number using xor
*/
for (i = 0; i < 8; i++)
n ^= [[aw_random]] ();

return n;
}

random_init ();

if (random_secure () == 547891)
puts ("You sure are lucky");

Secure

void random_init (void)
{
int i;

for (i = 0; i < 1000000; i++)
[[aw_random]] ();
}

int random_secure (void)
{
int buf[8];
int i;

for (i = 0; i < 8; i++)
buf[i] = [[aw_random]] ();

/*
function that takes a buffer as input, digests it using RIPEMD-128
and returns a 32-bit hash value from the output
*/

return ripemd128_32 ((char*)&buf, sizeof (buf));
}

random_init ();

if (random_secure () == 547891)
puts ("You sure are lucky");

==See also==
*[[aw_init]]

[[Category: SDK Methods|R]]

Aw init bind

2025-04-07T19:25:42Z

Xan: Created page with "{{SDK added in|version=4.1|sdk=61|world=|universe=|browser=}} __NOTOC__ int aw_init_bind (int <var>build</var>, unsigned long <var>addr</var>) ==Description== Initializes the SDK and specifies the source IP address for outbound connections. ==Callback== None (returns immediately) ==Notes== Specifying the source IP address is useful when you have multiple network interface cards (NIC) or a single NIC with multiple IP addresses. The source IP address must either matc..."

{{SDK added in|version=4.1|sdk=61|world=|universe=|browser=}}

__NOTOC__

int aw_init_bind (int <var>build</var>, unsigned long <var>addr</var>)

==Description==
Initializes the SDK and specifies the source IP address for outbound connections.

==Callback==
None (returns immediately)

==Notes==
Specifying the source IP address is useful when you have multiple network interface cards (NIC) or a single NIC with multiple IP addresses. The source IP address must either match or be within range of the IP address(es) used by a network interface on the system.

This method or [[aw_init]] must be called once before any other methods in the API. It will do an implicit [[aw_term]] if the SDK has already been successfully initialized. Thus, there is no need to call [[aw_term]] for each additional call to this method, as there is no reference count.

If successful then the tick count returned by [[aw_tick]] is reset to 0 and the pseudo-random number generator used by [[aw_random]] is seeded.

==Arguments==
;build:AW_BUILD in Aw.h defines the build of Aw.dll (or libaw_sdk.so for Linux) it was distributed with and should be passed as the value of this argument.
;addr:Source IP address for outbound connections (in network byte order.) If set to 0 (0.0.0.0) then it will be the same as calling [[aw_wait]].

==Argument attributes==
None

==Return values==
;[[SDK Reason Codes#RC_SUCCESS|RC_SUCCESS]]:
;[[SDK Reason Codes#RC_VERSION_MISMATCH|RC_VERSION_MISMATCH]]:Aw.h and Aw.dll (or libaw_sdk.so for Linux) are from different builds of the SDK.

==Returned attributes==
None

==Usage==
#include "Aw.h"
#include "[[Reason.h]]"

int main (int argc, char *argv[])
{
/* use 192.168.0.1 as the source for outbound connections */
if ([[aw_init_bind]] (AW_BUILD, inet_addr ("192.168.0.1")) != [[SDK Reason Codes#RC_SUCCESS|RC_SUCCESS]])
{
printf ("Build #%d of Aw.dll is required to run this bot.\n", AW_BUILD);
return 1;
}

/* ... */

[[aw_term]] ();
return 0;
}

==See also==
*[[SDK_Application_Structure|Application structure]]
*[[aw_init]]
*[[aw_random]]
*[[aw_term]]
*[[aw_tick]]

[[Category: SDK Methods|I]]

Aw term

2025-04-07T19:25:14Z

Xan: Created page with "{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}} __NOTOC__ void aw_term (void) ==Description== Terminates use of the SDK. ==Callback== None (returns immediately) ==Notes== This method deallocates any resources used by instances that have been created. Instances are created using aw_create, aw_create_resolved and aw_server_admin. If a call is placed to this method from within a callback or event handler then it cou..."

{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}}

__NOTOC__

void aw_term (void)

==Description==
Terminates use of the SDK.

==Callback==
None (returns immediately)

==Notes==
This method deallocates any resources used by [[SDK_Multiple_Instances|instances]] that have been created. Instances are created using [[aw_create]], [[aw_create_resolved]] and [[aw_server_admin]]. If a call is placed to this method from within a callback or event handler then it could leave dangling pointers in the SDK. Possibly causing a general protection fault (GPF) when it tries to access memory that has been freed.

Any installed callback or event handlers will remain and be used again if the SDK is initialized.

The [[aw_destroy]] method should be used to safely destroy [[SDK_Multiple_Instances|instances]] from within callback or event handlers. This is because [[aw_destroy]] does not deallocate them at once. They merely get flagged as "destroyed" which stops the SDK from processing packets for them.

Calling [[aw_destroy]] for all instances followed by [[aw_wait]] (0) is almost the same as calling aw_term. This is because [[aw_wait]] will deallocate instances marked as "destroyed". Only difference is that it would not be necessary to call [[aw_init]] again before creating instances.

Note that [[aw_destroy]] followed by [[aw_wait]] (0) within a callback or event handler is as bad as aw_term because both would deallocate the instance.

==Arguments==
None

==Argument attributes==
None

==Return values==
None

==Returned attributes==
None

==Usage==
#include "Aw.h"
#include "[[Reason.h]]"

int main (int argc, char *argv[])
{
if ([[aw_init]] (AW_BUILD) != [[SDK Reason Codes#RC_SUCCESS|RC_SUCCESS]])
{
printf ("Build #%d of Aw.dll is required to run this bot.\n", AW_BUILD);
return 1;
}

/* ... */

[[aw_term]] ();
return 0;
}

==See also==
*[[SDK_Application_Structure|Application structure]]
*[[aw_init]]
*[[aw_init_bind]]
*[[aw_create]]
*[[aw_create_resolved]]
*[[aw_server_admin]]

[[Category: SDK Methods|T]]

Reason.h

2025-04-07T19:24:46Z

Xan: Created page with " #define RC_SUCCESS 0 #define RC_CITIZENSHIP_EXPIRED 1 #define RC_LAND_LIMIT_EXCEEDED 2 #define RC_NO_SUCH_CITIZEN 3 #define RC_MESSAGE_LENGTH_BAD 4 #define RC_LICENSE_PASSWORD_CONTAINS_SPACE 5 #define RC_LICENSE_PASSWORD_TOO_LONG 6 #define RC_LICENSE_PASSWORD_TOO_SHORT 7 #define RC_LICENSE_RANGE_TOO_LARGE 8 #define RC_LICENSE_RANGE_TOO_SMALL 9 #define RC_LICENSE_USERS_TOO_LARGE 10 #define RC_LICENSE_USERS_TOO_SMALL 11 #define RC_LICENSE_CONTAINS_INVALID_CHAR..."

#define RC_SUCCESS 0
#define RC_CITIZENSHIP_EXPIRED 1
#define RC_LAND_LIMIT_EXCEEDED 2
#define RC_NO_SUCH_CITIZEN 3
#define RC_MESSAGE_LENGTH_BAD 4
#define RC_LICENSE_PASSWORD_CONTAINS_SPACE 5
#define RC_LICENSE_PASSWORD_TOO_LONG 6
#define RC_LICENSE_PASSWORD_TOO_SHORT 7
#define RC_LICENSE_RANGE_TOO_LARGE 8
#define RC_LICENSE_RANGE_TOO_SMALL 9
#define RC_LICENSE_USERS_TOO_LARGE 10
#define RC_LICENSE_USERS_TOO_SMALL 11
#define RC_LICENSE_CONTAINS_INVALID_CHAR 12
#define RC_INVALID_PASSWORD 13
#define RC_UNABLE_TO_MAIL_BACK_NUMBER 14
#define RC_LICENSE_WORLD_TOO_SHORT 15
#define RC_LICENSE_WORLD_TOO_LONG 16
#define RC_SERVER_OUT_OF_MEMORY 17
#define RC_INVALID_WORLD 20
#define RC_SERVER_OUTDATED 21
#define RC_WORLD_ALREADY_STARTED 22
#define RC_NO_SUCH_WORLD 27
#define RC_NOT_LOGGED_IN 31
#define RC_UNAUTHORIZED 32
#define RC_WORLD_ALREADY_EXISTS 33
#define RC_NO_SUCH_LICENSE 34
#define RC_IDENTITY_ALREADY_IN_USE 39
#define RC_UNABLE_TO_REPORT_LOCATION 40
#define RC_INVALID_EMAIL 41
#define RC_NO_SUCH_ACTING_CITIZEN 42
#define RC_ACTING_PASSWORD_INVALID 43
#define RC_UNIVERSE_FULL 45
#define RC_BILLING_TIMEOUT 46
#define RC_BILLING_RECV_FAILED 47
#define RC_BILLING_RESPONSE_INVALID 48
#define RC_BILLING_REJECTED 55
#define RC_BILLING_BLOCKED 56
#define RC_TOO_MANY_WORLDS 57
#define RC_MUST_UPGRADE 58
#define RC_BOT_LIMIT_EXCEEDED 59
#define RC_WORLD_EXPIRED 61
#define RC_CITIZEN_DOES_NOT_EXPIRE 62
#define RC_LICENSE_STARTS_WITH_NUMBER 64
#define RC_NO_SUCH_EJECTION 66
#define RC_NO_SUCH_SESSION 67
#define RC_EJECTION_EXPIRED 69
#define RC_ACTING_CITIZEN_EXPIRED 70
#define RC_ALREADY_STARTED 71
#define RC_WORLD_RUNNING 72
#define RC_WORLD_NOT_SET 73
#define RC_NO_SUCH_CELL 74
#define RC_NO_REGISTRY 75
#define RC_CANT_OPEN_REGISTRY 76
#define RC_CITIZEN_DISABLED 77
#define RC_WORLD_DISABLED 78
#define RC_BETA_REQUIRED 79
#define RC_ACTING_CITIZEN_DISABLED 80
#define RC_INVALID_USER_COUNT 81
#define RC_PRIVATE_WORLD 91
#define RC_NO_TOURISTS 92
#define RC_EMAIL_CONTAINS_INVALID_CHAR 100
#define RC_EMAIL_ENDS_WITH_BLANK 101
#define RC_NO_SUCH_OBJECT 101
#define RC_EMAIL_MISSING_DOT 102
#define RC_NOT_DELETE_OWNER 102
#define RC_EMAIL_MISSING_AT 103
#define RC_EMAIL_STARTS_WITH_BLANK 104
#define RC_EMAIL_TOO_LONG 105
#define RC_EMAIL_TOO_SHORT 106
#define RC_NAME_ALREADY_USED 107
#define RC_NAME_CONTAINS_NONALPHANUMERIC_CHAR 108
#define RC_NAME_CONTAINS_INVALID_BLANK 109
#define RC_NAME_DOESNT_EXIST 110
#define RC_NAME_ENDS_WITH_BLANK 111
#define RC_NAME_TOO_LONG 112
#define RC_NAME_TOO_SHORT 113
#define RC_NAME_UNUSED 114
#define RC_PASSWORD_TOO_LONG 115
#define RC_PASSWORD_TOO_SHORT 116
#define RC_PASSWORD_WRONG 117
#define RC_UNABLE_TO_DELETE_NAME 119
#define RC_UNABLE_TO_GET_CITIZEN 120
#define RC_UNABLE_TO_INSERT_CITIZEN 121
#define RC_UNABLE_TO_INSERT_NAME 122
#define RC_UNABLE_TO_PUT_CITIZEN_COUNT 123
#define RC_UNABLE_TO_DELETE_CITIZEN 124
#define RC_NUMBER_ALREADY_USED 126
#define RC_NUMBER_OUT_OF_RANGE 127
#define RC_PRIVILEGE_PASSWORD_IS_TOO_SHORT 128
#define RC_PRIVILEGE_PASSWORD_IS_TOO_LONG 129
#define RC_NOT_CHANGE_OWNER 203
#define RC_CANT_FIND_OLD_ELEMENT 204
#define RC_UNABLE_TO_CHANGE_ATTRIBUTE 210
#define RC_CANT_CHANGE_OWNER 211
#define RC_IMPOSTER 212
#define RC_INVALID_REQUEST 213
#define RC_CANT_BUILD_HERE 216
#define RC_ENCROACHES 300
#define RC_OBJECT_TYPE_INVALID 301
#define RC_TOO_MANY_BYTES 303
#define RC_UNABLE_TO_STORE 305
#define RC_UNREGISTERED_OBJECT 306
#define RC_ELEMENT_ALREADY_EXISTS 308
#define RC_RESTRICTED_COMMAND 309
#define RC_NO_BUILD_RIGHTS 310
#define RC_OUT_OF_BOUNDS 311
#define RC_RESTRICTED_OBJECT 313
#define RC_RESTRICTED_AREA 314
#define RC_OUT_OF_MEMORY 400
#define RC_NOT_YET 401
#define RC_TIMEOUT 402
#define RC_NULL_POINTER 403
#define RC_UNABLE_TO_CONTACT_UNIVERSE 404
#define RC_UNABLE_TO_CONTACT_WORLD 405
#define RC_INVALID_WORLD_NAME 406
#define RC_SEND_FAILED 415
#define RC_RECEIVE_FAILED 416
#define RC_STREAM_EMPTY 421
#define RC_STREAM_MESSAGE_TOO_LONG 422
#define RC_WORLD_NAME_TOO_LONG 423
#define RC_MESSAGE_TOO_LONG 426
#define RC_TOO_MANY_RESETS 427
#define RC_UNABLE_TO_CREATE_SOCKET 428
#define RC_UNABLE_TO_CONNECT 429
#define RC_UNABLE_TO_SET_NONBLOCKING 430
#define RC_CANT_OPEN_STREAM 434
#define RC_CANT_WRITE_STREAM 435
#define RC_CANT_CLOSE_STREAM 436
#define RC_NO_CONNECTION 439
#define RC_UNABLE_TO_INITIALIZE_NETWORK 442
#define RC_INCORRECT_MESSAGE_LENGTH 443
#define RC_NOT_INITIALIZED 444
#define RC_NO_INSTANCE 445
#define RC_OUT_BUFFER_FULL 446
#define RC_INVALID_CALLBACK 447
#define RC_INVALID_ATTRIBUTE 448
#define RC_TYPE_MISMATCH 449
#define RC_STRING_TOO_LONG 450
#define RC_READ_ONLY 451
#define RC_UNABLE_TO_REGISTER_RESOLVE 452
#define RC_INVALID_INSTANCE 453
#define RC_VERSION_MISMATCH 454
#define RC_IN_BUFFER_FULL 461
#define RC_PROTOCOL_ERROR 463
#define RC_QUERY_IN_PROGRESS 464
#define RC_WORLD_FULL 465
#define RC_EJECTED 466
#define RC_NOT_WELCOME 467
#define RC_UNABLE_TO_BIND 468
#define RC_UNABLE_TO_LISTEN 469
#define RC_UNABLE_TO_ACCEPT 470
#define RC_CONNECTION_LOST 471
#define RC_NO_STREAM 473
#define RC_NOT_AVAILABLE 474
#define RC_OLD_UNIVERSE 487
#define RC_OLD_WORLD 488
#define RC_WORLD_NOT_RUNNING 489
#define RC_CANT_RESOLVE_UNIVERSE_HOST 500
#define RC_INVALID_ARGUMENT 505
#define RC_WORLD_INSTANCE_ALREADY_EXISTS 521
#define RC_WORLD_INSTANCE_INVALID 522
#define RC_EMAIL_CHANGE_NOT_ALLOWED 525
#define RC_NAME_CHANGE_NOT_ALLOWED 526
#define RC_EMAIL_ALREADY_USED 527
#define RC_EMAIL_NOT_ALLOWED 528
#define RC_WORLD_REDIRECT 529
#define RC_DATABASE_ERROR 600

[[Category: Lists]]

SDK Reason Codes

2025-04-07T19:24:14Z

Xan: Created page with "__TOC__ ==Current version== <table class="sortable" border="border" cellpadding="4" cellspacing="0" width="100%"> <tr><th align="left" width="30%">Reason code</th><th align="left" width="10%">Value</th><th align="left" width="60%">Description</th></tr> <tr> <td id="RC_SUCCESS">RC_SUCCESS</td> <td id="NO_0">0</td> <td>''Success'' :<table> <tr><td>Return value from an asynchronous call:</td><td width="20"> </td><td>Request has been sent to the server.</td></tr>..."

__TOC__

==Current version==

<table class="sortable" border="border" cellpadding="4" cellspacing="0" width="100%">
<tr><th align="left" width="30%">Reason code</th><th align="left" width="10%">Value</th><th align="left" width="60%">Description</th></tr>

<tr>
<td id="RC_SUCCESS">RC_SUCCESS</td>
<td id="NO_0">0</td>
<td>''Success''
:<table>
<tr><td>Return value from an asynchronous call:</td><td width="20"> </td><td>Request has been sent to the server.</td></tr>
<tr><td>Return value from a blocking call:</td><td width="20"> </td><td>Operation has completed successfully.</td></tr>
<tr><td>When passed to a callback:</td><td width="20"> </td><td>Operation has completed successfully.</td></tr>
</table>
</td>
</tr>

<tr>
<td id="RC_CITIZENSHIP_EXPIRED">RC_CITIZENSHIP_EXPIRED</td>
<td id="NO_1">1</td>
<td>''Citizenship has expired''
:Citizenship of the owner has expired.</td>
</tr>

<tr>
<td id="RC_LAND_LIMIT_EXCEEDED">RC_LAND_LIMIT_EXCEEDED</td>
<td id="NO_2">2</td>
<td>''Land limit exceeded''
:Land limit of the universe would be exceeded if the world is started.</td>
</tr>

<tr>
<td id="RC_NO_SUCH_CITIZEN">RC_NO_SUCH_CITIZEN</td>
<td id="NO_3">3</td>
<td>''No such citizen''
:No citizenship with a matching citizen number was found.</td>
</tr>

<tr>
<td id="RC_LICENSE_PASSWORD_CONTAINS_SPACE">RC_LICENSE_PASSWORD_CONTAINS_SPACE</td>
<td id="NO_5">5</td>
<td>''License password contains space''
:Password cannot contain a space.</td>
</tr>

<tr>
<td id="RC_LICENSE_PASSWORD_TOO_LONG">RC_LICENSE_PASSWORD_TOO_LONG</td>
<td id="NO_6">6</td>
<td>''License password too long''
:Password cannot be longer than 8 characters.</td>
</tr>

<tr>
<td id="RC_LICENSE_PASSWORD_TOO_SHORT">RC_LICENSE_PASSWORD_TOO_SHORT</td>
<td id="NO_7">7</td>
<td>''License password too short''
:Password must be at least 2 characters.</td>
</tr>

<tr>
<td id="RC_LICENSE_RANGE_TOO_LARGE">RC_LICENSE_RANGE_TOO_LARGE</td>
<td id="NO_8">8</td>
<td>''License range too large''
:Range must be smaller than 3275 hectometers. That is, at most 32750 coordinates N/S/W/E or 655000 meters across.</td>
</tr>

<tr>
<td id="RC_LICENSE_RANGE_TOO_SMALL">RC_LICENSE_RANGE_TOO_SMALL</td>
<td id="NO_9">9</td>
<td>''License range too small''
:Range must be larger than 0 hectometers. That is, at least 10 coordinates N/S/W/E or 200 meters across.</td>
</tr>

<tr>
<td id="RC_LICENSE_USERS_TOO_LARGE">RC_LICENSE_USERS_TOO_LARGE</td>
<td id="NO_10">10</td>
<td>''License users too large''
:User limit cannot exceed 1024.</td>
</tr>

<tr>
<td id="RC_LICENSE_USERS_TOO_SMALL">RC_LICENSE_USERS_TOO_SMALL</td>
<td id="NO_11">11</td>
<td>''License users too small''
:User limit must be larger than 0.</td>
</tr>

<tr>
<td id="RC_INVALID_PASSWORD">RC_INVALID_PASSWORD</td>
<td id="NO_13">13</td>
<td>''Invalid password''
:Unable to login due to invalid password.</td>
</tr>

<tr>
<td id="RC_LICENSE_WORLD_TOO_SHORT">RC_LICENSE_WORLD_TOO_SHORT</td>
<td id="NO_15">15</td>
<td>''License world too short''
:Name must be at least 2 characters.</td>
</tr>

<tr>
<td id="RC_LICENSE_WORLD_TOO_LONG">RC_LICENSE_WORLD_TOO_LONG</td>
<td id="NO_16">16</td>
<td>''License world too long''
:Name cannot be longer than 8 characters.</td>
</tr>

<tr>
<td id="RC_MUST_UPGRADE">RC_MUST_UPGRADE</td>
<td id="NO_18">18</td>
<td>''SDK update required''
:The used SDK build is obsolete. Update to recent SDK build number. Similar to RC#58.</td>
</tr>

<tr>
<td id="RC_INVALID_WORLD">RC_INVALID_WORLD</td>
<td id="NO_20">20</td>
<td>''Invalid world''
:Unable to start the world due to invalid name or password.</td>
</tr>

<tr>
<td id="RC_SERVER_OUTDATED">RC_SERVER_OUTDATED</td>
<td id="NO_21">21</td>
<td>''Server outdated''
:Server build either contains a serious flaw or is outdated and must be upgraded.</td>
</tr>

<tr>
<td id="RC_WORLD_ALREADY_STARTED">RC_WORLD_ALREADY_STARTED</td>
<td id="NO_22">22</td>
<td>''World already started''
:World has already been started at a different location.</td>
</tr>

<tr>
<td id="RC_NO_SUCH_WORLD">RC_NO_SUCH_WORLD</td>
<td id="NO_27">27</td>
<td>''No such world''
:No world with a matching name has been started on the server.</td>
</tr>

<tr>
<td id="RC_UNAUTHORIZED">RC_UNAUTHORIZED</td>
<td id="NO_32">32</td>
<td>''Unauthorized''
:Not authorized to perform the operation.</td>
</tr>

<tr>
<td id="RC_NO_SUCH_LICENSE">RC_NO_SUCH_LICENSE</td>
<td id="NO_34">34</td>
<td>''No such license''
:No license with a matching world name was found.</td>
</tr>

<tr>
<td id="RC_TOO_MANY_WORLDS">RC_TOO_MANY_WORLDS</td>
<td id="NO_57">57</td>
<td>''Too many worlds''
:Limit of started worlds in the universe would be exceeded if the world is started.</td>
</tr>

<tr>
<td id="RC_MUST_UPGRADE">RC_MUST_UPGRADE</td>
<td id="NO_58">58</td>
<td>''Must upgrade''
:SDK build either contains a serious flaw or is outdated and must be upgraded.</td>
</tr>

<tr>
<td id="RC_BOT_LIMIT_EXCEEDED">RC_BOT_LIMIT_EXCEEDED</td>
<td id="NO_59">59</td>
<td>''Bot limit exceeded''
:Bot limit of the owner citizenship would be exceeded if the bot is logged in.</td>
</tr>

<tr>
<td id="RC_WORLD_EXPIRED">RC_WORLD_EXPIRED</td>
<td id="NO_61">61</td>
<td>''World expired''
:Unable to start world due to its license having expired.</td>
</tr>

<tr>
<td id="RC_CITIZEN_DOES_NOT_EXPIRE">RC_CITIZEN_DOES_NOT_EXPIRE</td>
<td id="NO_62">62</td>
<td>''Citizen does not expire''
:TODO: What is this used for?</td>
</tr>

<tr>
<td id="RC_LICENSE_STARTS_WITH_NUMBER">RC_LICENSE_STARTS_WITH_NUMBER</td>
<td id="NO_64">64</td>
<td>''License starts with number''
:Name cannot start with a number.</td>
</tr>

<tr>
<td id="RC_NO_SUCH_EJECTION">RC_NO_SUCH_EJECTION</td>
<td id="NO_66">66</td>
<td>''No such ejection''
:No ejection with a matching identifier was found.</td>
</tr>

<tr>
<td id="RC_NO_SUCH_SESSION">RC_NO_SUCH_SESSION</td>
<td id="NO_67">67</td>
<td>''No such session''
:No user with a matching session number has entered the world.</td>
</tr>

<tr>
<td id="RC_WORLD_RUNNING">RC_WORLD_RUNNING</td>
<td id="NO_72">72</td>
<td>''World running''
:World has already been started.</td>
</tr>

<tr>
<td id="RC_WORLD_NOT_SET">RC_WORLD_NOT_SET</td>
<td id="NO_73">73</td>
<td>''World not set''
:World to perform the operation on has not been set.</td>
</tr>

<tr>
<td id="RC_NO_SUCH_CELL">RC_NO_SUCH_CELL</td>
<td id="NO_74">74</td>
<td>''No such cell''
:No more cells left to enumerate.</td>
</tr>

<tr>
<td id="RC_NO_REGISTRY">RC_NO_REGISTRY</td>
<td id="NO_75">75</td>
<td>''No registry''
:Unable to start world due to missing or invalid registry.</td>
</tr>

<tr>
<td id="RC_CANT_OPEN_REGISTRY">RC_CANT_OPEN_REGISTRY</td>
<td id="NO_76">76</td>
<td>''Can't open registry''</td>
</tr>

<tr>
<td id="RC_CITIZEN_DISABLED">RC_CITIZEN_DISABLED</td>
<td id="NO_77">77</td>
<td>''Citizen disabled''
:Citizenship of the owner has been disabled.</td>
</tr>

<tr>
<td id="RC_WORLD_DISABLED">RC_WORLD_DISABLED</td>
<td id="NO_78">78</td>
<td>''World disabled''
:Unable to start world due to it being disabled.</td>
</tr>

<tr>
<td id="RC_TELEGRAM_BLOCKED">RC_TELEGRAM_BLOCKED</td>
<td id="NO_85">85</td>
<td>''Telegram blocked''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_UPDATE_TERRAIN">RC_UNABLE_TO_UPDATE_TERRAIN</td>
<td id="NO_88">88</td>
<td>''Unable to update terrain''</td>
</tr>

<tr>
<td id="RC_EMAIL_CONTAINS_INVALID_CHAR">RC_EMAIL_CONTAINS_INVALID_CHAR</td>
<td id="NO_100">100</td>
<td>''Email contains invalid char''
:Email address contains one or more invalid characters.</td>
</tr>

<tr>
<td id="RC_EMAIL_ENDS_WITH_BLANK">RC_EMAIL_ENDS_WITH_BLANK</td>
<td id="NO_101">101</td>
<td>''Email ends with blank''
:Email address cannot end with a blank.</td>
</tr>

<tr>
<td id="RC_NO_SUCH_OBJECT">RC_NO_SUCH_OBJECT</td>
<td id="NO_101b">101</td>
<td>''No such object''
:Unable to find the object to delete.</td>
</tr>

<tr>
<td id="RC_EMAIL_MISSING_DOT">RC_EMAIL_MISSING_DOT</td>
<td id="NO_102">102</td>
<td>''Email missing dot''
:Email address must contain at least one '.'.</td>
</tr>

<tr>
<td id="RC_NOT_DELETE_OWNER">RC_NOT_DELETE_OWNER</td>
<td id="NO_102b">102</td>
<td>''Not delete owner''</td>
</tr>

<tr>
<td id="RC_EMAIL_MISSING_AT">RC_EMAIL_MISSING_AT</td>
<td id="NO_103">103</td>
<td>''Email missing at''
:Email address must contain a '@'.</td>
</tr>

<tr>
<td id="RC_EMAIL_STARTS_WITH_BLANK">RC_EMAIL_STARTS_WITH_BLANK</td>
<td id="NO_104">104</td>
<td>''Email starts with blank''
:Email address cannot start with a blank.</td>
</tr>

<tr>
<td id="RC_EMAIL_TOO_LONG">RC_EMAIL_TOO_LONG</td>
<td id="NO_105">105</td>
<td>''Email too long''
:Email address cannot be longer than 50 characters.</td>
</tr>

<tr>
<td id="RC_EMAIL_TOO_SHORT">RC_EMAIL_TOO_SHORT</td>
<td id="NO_106">106</td>
<td>''Email too short''
:Email address must be at least 8 characters or longer.</td>
</tr>

<tr>
<td id="RC_NAME_ALREADY_USED">RC_NAME_ALREADY_USED</td>
<td id="NO_107">107</td>
<td>''Name already used''
:Citizenship with a matching name already exists.</td>
</tr>

<tr>
<td id="RC_NAME_CONTAINS_NONALPHANUMERIC_CHAR">RC_NAME_CONTAINS_NONALPHANUMERIC_CHAR</td>
<td id="NO_108">108</td>
<td>''Name contains nonalphanumeric character''
:Name contains invalid character(s).</td>
</tr>

<tr>
<td id="RC_NAME_CONTAINS_INVALID_BLANK">RC_NAME_CONTAINS_INVALID_BLANK</td>
<td id="NO_109">109</td>
<td>''Name contains invalid blank''
:Name contains invalid blank(s).</td>
</tr>

<tr>
<td id="RC_NAME_ENDS_WITH_BLANK">RC_NAME_ENDS_WITH_BLANK</td>
<td id="NO_111">111</td>
<td>''Name ends with blank''
:Name cannot end with a blank.</td>
</tr>

<tr>
<td id="RC_NAME_TOO_LONG">RC_NAME_TOO_LONG</td>
<td id="NO_112">112</td>
<td>''Name too long''
:Name cannot be longer than 20 characters.</td>
</tr>

<tr>
<td id="RC_NAME_TOO_SHORT">RC_NAME_TOO_SHORT</td>
<td id="NO_113">113</td>
<td>''Name too short''
:Name must be at least 4 characters.</td>
</tr>

<tr>
<td id="RC_PASSWORD_TOO_LONG">RC_PASSWORD_TOO_LONG</td>
<td id="NO_115">115</td>
<td>''Password too long''
:Password cannot be longer than 16 characters.</td>
</tr>

<tr>
<td id="RC_PASSWORD_TOO_SHORT">RC_PASSWORD_TOO_SHORT</td>
<td id="NO_116">116</td>
<td>''Password too short''
:Password must be at least 8 characters.</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_DELETE_CITIZEN">RC_UNABLE_TO_DELETE_CITIZEN</td>
<td id="NO_124">124</td>
<td>''Unable to delete citizen''
:Unable to delete citizen due to a database problem.</td>
</tr>

<tr>
<td id="RC_NUMBER_ALREADY_USED">RC_NUMBER_ALREADY_USED</td>
<td id="NO_126">126</td>
<td>''Number already used''
:Citizenship with a matching citizen number already exists.</td>
</tr>

<tr>
<td id="RC_NUMBER_OUT_OF_RANGE">RC_NUMBER_OUT_OF_RANGE</td>
<td id="NO_127">127</td>
<td>''Number out of range''
:Citizen number is larger than the auto-incremented field in the database.</td>
</tr>

<tr>
<td id="RC_PRIVILEGE_PASSWORD_IS_TOO_SHORT">RC_PRIVILEGE_PASSWORD_IS_TOO_SHORT</td>
<td id="NO_128">128</td>
<td>''Privilege password is too short''
:Privilege password must be either empty or at least 4 characters.</td>
</tr>

<tr>
<td id="RC_PRIVILEGE_PASSWORD_IS_TOO_LONG">RC_PRIVILEGE_PASSWORD_IS_TOO_LONG</td>
<td id="NO_129">129</td>
<td>''Privilege password is too long''
:Password cannot be longer than 12 characters.</td>
</tr>

<tr>
<td id="RC_NOT_CHANGE_OWNER">RC_NOT_CHANGE_OWNER</td>
<td id="NO_203">203</td>
<td>''Not change owner''
:Not permitted to change the owner of an object. It requires eminent domain or caretaker capability.</td>
</tr>

<tr>
<td id="RC_CANT_FIND_OLD_ELEMENT">RC_CANT_FIND_OLD_ELEMENT</td>
<td id="NO_204">204</td>
<td>''Can't find old element''
:Unable to find the object to change.</td>
</tr>

<tr>
<td id="RC_IMPOSTER">RC_IMPOSTER</td>
<td id="NO_212">212</td>
<td>''Imposter''
:Unable to enter world due to masquerading as someone else.</td>
</tr>

<tr>
<td id="RC_ENCROACHES">RC_ENCROACHES</td>
<td id="NO_300">300</td>
<td>''Encroaches''
:Not allowed to encroach into another's property.</td>
</tr>

<tr>
<td id="RC_OBJECT_TYPE_INVALID">RC_OBJECT_TYPE_INVALID</td>
<td id="NO_301">301</td>
<td>''Object type invalid''</td>
</tr>

<tr>
<td id="RC_TOO_MANY_BYTES">RC_TOO_MANY_BYTES</td>
<td id="NO_303">303</td>
<td>''Too many bytes''
:Cell limit would be exceeded.</td>
</tr>

<tr>
<td id="RC_UNREGISTERED_OBJECT">RC_UNREGISTERED_OBJECT</td>
<td id="NO_306">306</td>
<td>''Unregistered object''
:Model name does not exist in the registry.</td>
</tr>

<tr>
<td id="RC_ELEMENT_ALREADY_EXISTS">RC_ELEMENT_ALREADY_EXISTS</td>
<td id="NO_308">308</td>
<td>''Element already exists''</td>
</tr>

<tr>
<td id="RC_RESTRICTED_COMMAND">RC_RESTRICTED_COMMAND</td>
<td id="NO_309">309</td>
<td>''Restricted command''</td>
</tr>

<tr>
<td id="RC_OUT_OF_BOUNDS">RC_OUT_OF_BOUNDS</td>
<td id="NO_311">311</td>
<td>''Out of bounds''</td>
</tr>

<tr>
<td id="RC_RESTRICTED_OBJECT">RC_RESTRICTED_OBJECT</td>
<td id="NO_313">313</td>
<td>''Restricted object''
:Not allowed to build with 'z' objects in this world. [the same error code is used for V4 objects]</td>
</tr>

<tr>
<td id="RC_RESTRICTED_AREA">RC_RESTRICTED_AREA</td>
<td id="NO_314">314</td>
<td>''Restricted area''
:Not allowed to build within the restricted area of this world.</td>
</tr>

<tr>
<td id="RC_NOT_YET">RC_NOT_YET</td>
<td id="NO_401">401</td>
<td>''Not yet''
:Would exceed the maximum number of operations per second.</td>
</tr>

<tr>
<td id="RC_TIMEOUT">RC_TIMEOUT</td>
<td id="NO_402">402</td>
<td>''Timeout''
:Synchronous operation timed out.</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_CONTACT_UNIVERSE">RC_UNABLE_TO_CONTACT_UNIVERSE</td>
<td id="NO_404">404</td>
<td>''Unable to contact universe''
:Unable to establish a connection to the universe server.</td>
</tr>

<tr>
<td id="RC_NO_CONNECTION">RC_NO_CONNECTION</td>
<td id="NO_439">439</td>
<td>''No connection''
:Connection to the server is down.</td>
</tr>

<tr>
<td id="RC_NOT_INITIALIZED">RC_NOT_INITIALIZED</td>
<td id="NO_444">444</td>
<td>''Not initialized''
:SDK API has not been initialized (by calling [[aw_init]]).</td>
</tr>

<tr>
<td id="RC_NO_INSTANCE">RC_NO_INSTANCE</td>
<td id="NO_445">445</td>
<td>''No instance''</td>
</tr>

<tr>
<td id="RC_INVALID_ATTRIBUTE">RC_INVALID_ATTRIBUTE</td>
<td id="NO_448">448</td>
<td>''Invalid attribute''</td>
</tr>

<tr>
<td id="RC_TYPE_MISMATCH">RC_TYPE_MISMATCH</td>
<td id="NO_449">449</td>
<td>''Type mismatch''</td>
</tr>

<tr>
<td id="RC_STRING_TOO_LONG">RC_STRING_TOO_LONG</td>
<td id="NO_450">450</td>
<td>''String too long''</td>
</tr>

<tr>
<td id="RC_READ_ONLY">RC_READ_ONLY</td>
<td id="NO_451">451</td>
<td>''Read only''
:Unable to set attribute due to it being read-only.</td>
</tr>

<tr>
<td id="RC_INVALID_INSTANCE">RC_INVALID_INSTANCE</td>
<td id="NO_453">453</td>
<td>''Invalid instance''</td>
</tr>

<tr>
<td id="RC_VERSION_MISMATCH">RC_VERSION_MISMATCH</td>
<td id="NO_454">454</td>
<td>''Version mismatch''
:Aw.h and Aw.dll (or libaw_sdk.so for Linux) are from different builds of the SDK.</td>
</tr>

<tr>
<td id="RC_QUERY_IN_PROGRESS">RC_QUERY_IN_PROGRESS</td>
<td id="NO_464">464</td>
<td>''Query in progress''
:A property query is already in progress.</td>
</tr>

<tr>
<td id="RC_EJECTED">RC_EJECTED</td>
<td id="NO_466">466</td>
<td>''Ejected''
:Disconnected from world due to ejection.</td>
</tr>

<tr>
<td id="RC_NOT_WELCOME">RC_NOT_WELCOME</td>
<td id="NO_467">467</td>
<td>''Not welcome''
:Citizenship of the owner does not have bot rights in the world.</td>
</tr>

<tr>
<td id="RC_CONNECTION_LOST">RC_CONNECTION_LOST</td>
<td id="NO_471">471</td>
<td>''Connection lost''</td>
</tr>

<tr>
<td id="RC_NOT_AVAILABLE">RC_NOT_AVAILABLE</td>
<td id="NO_474">474</td>
<td>''Not available''</td>
</tr>

<tr>
<td id="RC_CANT_RESOLVE_UNIVERSE_HOST">RC_CANT_RESOLVE_UNIVERSE_HOST</td>
<td id="NO_500">500</td>
<td>''Can't resolve universe host''</td>
</tr>

<tr>
<td id="RC_INVALID_ARGUMENT">RC_INVALID_ARGUMENT</td>
<td id="NO_505">505</td>
<td>''Invalid argument''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_UPDATE_CAV">RC_UNABLE_TO_UPDATE_CAV</td>
<td id="NO_514">514</td>
<td>''Unable to update custom avatar''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_DELETE_CAV">RC_UNABLE_TO_DELETE_CAV</td>
<td id="NO_515">515</td>
<td>''Unable to delete custom avatar''</td>
</tr>

<tr>
<td id="RC_NO_SUCH_CAV">RC_NO_SUCH_CAV</td>
<td id="NO_516">516</td>
<td>''No such custom avatar''</td>
</tr>

<tr>
<td id="RC_WORLD_INSTANCE_ALREADY_EXISTS">RC_WORLD_INSTANCE_ALREADY_EXISTS</td>
<td id="NO_521">521</td>
<td>''World instance already exists''</td>
</tr>

<tr>
<td id="RC_WORLD_INSTANCE_INVALID">RC_WORLD_INSTANCE_INVALID</td>
<td id="NO_522">522</td>
<td>''World instance invalid''</td>
</tr>

<tr>
<td id="RC_PLUGIN_NOT_AVAILABLE">RC_PLUGIN_NOT_AVAILABLE</td>
<td id="NO_523">523</td>
<td>''Plugin not available''</td>
</tr>

<tr>
<td id="RC_DATABASE_ERROR">RC_DATABASE_ERROR</td>
<td id="NO_600">600</td>
<td>''Database error''</td>
</tr>

<tr>
<td id="RC_Z_BUF_ERROR">RC_Z_BUF_ERROR</td>
<td id="NO_4995">4995</td>
<td>''Buffer error (zlib)''
:Not enough room in the output buffer.</td>
</tr>

<tr>
<td id="RC_Z_MEM_ERROR">RC_Z_MEM_ERROR</td>
<td id="NO_4996">4996</td>
<td>''Memory error (zlib)''
:Memory could not be allocated for processing.</td>
</tr>

<tr>
<td id="RC_Z_DATA_ERROR">RC_Z_DATA_ERROR</td>
<td id="NO_4997">4997</td>
<td>''Data error (zlib)''
:Input data was corrupted.</td>
</tr>

</table>

==Addition older reason codes, not used by the free SDK==

<table class="sortable" border="border" cellpadding="4" cellspacing="0" width="100%">
<tr><th align="left" width="30%">Reason code</th><th align="left" width="10%">Value</th><th align="left" width="60%">Description</th></tr>
<tr>
<td id="RC_MESSAGE_LENGTH_BAD">RC_MESSAGE_LENGTH_BAD</td>
<td>4</td>
<td>''Message length bad''</td>
</tr>

<tr>
<td id="RC_LICENSE_CONTAINS_INVALID_CHAR">RC_LICENSE_CONTAINS_INVALID_CHAR</td>
<td>12</td>
<td>''License contains invalid character''</td>
</tr>

<tr>
<td id="RC_SERVER_OUT_OF_MEMORY">RC_SERVER_OUT_OF_MEMORY</td>
<td>17</td>
<td>''Server out of memory''</td>
</tr>

<tr>
<td id="RC_NOT_LOGGED_IN">RC_NOT_LOGGED_IN</td>
<td>31</td>
<td>''Not logged in''
:Must be logged in to perform the operation.</td>
</tr>

<tr>
<td id="RC_WORLD_ALREADY_EXISTS">RC_WORLD_ALREADY_EXISTS</td>
<td>33</td>
<td>''World already exists''
:Name already exists.</td>
</tr>

<tr>
<td id="RC_NO_SUCH_ACTING_CITIZEN">RC_NO_SUCH_ACTING_CITIZEN</td>
<td>42</td>
<td>''No such acting citizen''</td>
</tr>

<tr>
<td id="RC_ACTING_PASSWORD_INVALID">RC_ACTING_PASSWORD_INVALID</td>
<td>43</td>
<td>''Acting password invalid''</td>
</tr>

<tr>
<td id="RC_EJECTION_EXPIRED">RC_EJECTION_EXPIRED</td>
<td>69</td>
<td>''Ejection expired''
:Attempting to add an ejection that has already expired.</td>
</tr>

<tr>
<td id="RC_ACTING_CITIZEN_EXPIRED">RC_ACTING_CITIZEN_EXPIRED</td>
<td>70</td>
<td>''Acting citizen expired''</td>
</tr>

<tr>
<td id="RC_ALREADY_STARTED">RC_ALREADY_STARTED</td>
<td>71</td>
<td>''Already started''</td>
</tr>

<tr>
<td id="RC_ACTING_CITIZEN_DISABLED">RC_ACTING_CITIZEN_DISABLED</td>
<td>80</td>
<td>''Acting citizen disabled''</td>
</tr>

<tr>
<td id="RC_TELEGRAM_TOO_LONG">RC_TELEGRAM_TOO_LONG</td>
<td>86</td>
<td>''Telegram too long''</td>
</tr>

<tr>
<td id="RC_NAME_DOESNT_EXIST">RC_NAME_DOESNT_EXIST</td>
<td>110</td>
<td>''Name doesn't exist''</td>
</tr>

<tr>
<td id="RC_NAME_UNUSED">RC_NAME_UNUSED</td>
<td>114</td>
<td>''Name unused''</td>
</tr>

<tr>
<td id="RC_PASSWORD_WRONG">RC_PASSWORD_WRONG</td>
<td>117</td>
<td>''Password wrong''
:TODO: Where is this used?</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_DELETE_NAME">RC_UNABLE_TO_DELETE_NAME</td>
<td>119</td>
<td>''Unable to delete name''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_GET_CITIZEN">RC_UNABLE_TO_GET_CITIZEN</td>
<td>120</td>
<td>''Unable to get citizen''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_INSERT_CITIZEN">RC_UNABLE_TO_INSERT_CITIZEN</td>
<td>121</td>
<td>''Unable to insert citizen''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_INSERT_NAME">RC_UNABLE_TO_INSERT_NAME</td>
<td>122</td>
<td>''Unable to insert name''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_PUT_CITIZEN_COUNT">RC_UNABLE_TO_PUT_CITIZEN_COUNT</td>
<td>123</td>
<td>''Unable to put citizen count''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_CHANGE_ATTRIBUTE">RC_UNABLE_TO_CHANGE_ATTRIBUTE</td>
<td>210</td>
<td>''Unable to change attribute''</td>
</tr>

<tr>
<td id="RC_INVALID_REQUEST">RC_INVALID_REQUEST</td>
<td>213</td>
<td>''Invalid request''</td>
</tr>

<tr>
<td id="RC_CANT_BUILD_HERE">RC_CANT_BUILD_HERE</td>
<td>216</td>
<td>''Can't build here''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_STORE">RC_UNABLE_TO_STORE</td>
<td>305</td>
<td>''Unable to store''</td>
</tr>

<tr>
<td id="RC_NO_BUILD_RIGHTS">RC_NO_BUILD_RIGHTS</td>
<td>310</td>
<td>''No build rights''</td>
</tr>

<tr>
<td id="RC_OUT_OF_MEMORY">RC_OUT_OF_MEMORY</td>
<td>400</td>
<td>''Out of memory''</td>
</tr>

<tr>
<td id="RC_NULL_POINTER">RC_NULL_POINTER</td>
<td>403</td>
<td>''Null pointer''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_CONTACT_WORLD">RC_UNABLE_TO_CONTACT_WORLD</td>
<td>405</td>
<td>''Unable to contact world''</td>
</tr>

<tr>
<td id="RC_INVALID_WORLD_NAME">RC_INVALID_WORLD_NAME</td>
<td>406</td>
<td>''Invalid world name''</td>
</tr>

<tr>
<td id="RC_SEND_FAILED">RC_SEND_FAILED</td>
<td>415</td>
<td>''Send failed''</td>
</tr>

<tr>
<td id="RC_RECEIVE_FAILED">RC_RECEIVE_FAILED</td>
<td>416</td>
<td>''Receive failed''
:Unable to receive data from network socket.

:This can occur for any number of reasons. But in general, it means some kind of network communication problem has occurred.

:It could be that the peer host has disconnected, peer host failed to respond in time, connection is being blocked by a firewall, or anything else that would interfere with socket communications.</td>
</tr>

<tr>
<td id="RC_STREAM_EMPTY">RC_STREAM_EMPTY</td>
<td>421</td>
<td>''Stream empty''</td>
</tr>

<tr>
<td id="RC_STREAM_MESSAGE_TOO_LONG">RC_STREAM_MESSAGE_TOO_LONG</td>
<td>422</td>
<td>''Stream message too long''</td>
</tr>

<tr>
<td id="RC_WORLD_NAME_TOO_LONG">RC_WORLD_NAME_TOO_LONG</td>
<td>423</td>
<td>''World name too long''</td>
</tr>

<tr>
<td id="RC_MESSAGE_TOO_LONG">RC_MESSAGE_TOO_LONG</td>
<td>426</td>
<td>''Message too long''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_CREATE_SOCKET">RC_UNABLE_TO_CREATE_SOCKET</td>
<td>428</td>
<td>''Unable to create socket''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_CONNECT">RC_UNABLE_TO_CONNECT</td>
<td>429</td>
<td>''Unable to connect''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_SET_NONBLOCKING">RC_UNABLE_TO_SET_NONBLOCKING</td>
<td>430</td>
<td>''Unable to set nonblocking''</td>
</tr>

<tr>
<td id="RC_CANT_OPEN_STREAM">RC_CANT_OPEN_STREAM</td>
<td>434</td>
<td>''Can't open stream''</td>
</tr>

<tr>
<td id="RC_CANT_WRITE_STREAM">RC_CANT_WRITE_STREAM</td>
<td>435</td>
<td>''Can't write stream''</td>
</tr>

<tr>
<td id="RC_CANT_CLOSE_STREAM">RC_CANT_CLOSE_STREAM</td>
<td>436</td>
<td>''Can't close stream''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_INITIALIZE_NETWORK">RC_UNABLE_TO_INITIALIZE_NETWORK</td>
<td>442</td>
<td>''Unable to initialize network''</td>
</tr>

<tr>
<td id="RC_INCORRECT_MESSAGE_LENGTH">RC_INCORRECT_MESSAGE_LENGTH</td>
<td>443</td>
<td>''Incorrect message length''</td>
</tr>

<tr>
<td id="RC_OUT_BUFFER_FULL">RC_OUT_BUFFER_FULL</td>
<td>446</td>
<td>''Out buffer full''</td>
</tr>

<tr>
<td id="RC_INVALID_CALLBACK">RC_INVALID_CALLBACK</td>
<td>447</td>
<td>''Invalid callback''</td>
</tr>

<tr>
<td id="RC_IN_BUFFER_FULL">RC_IN_BUFFER_FULL</td>
<td>461</td>
<td>''In buffer full''</td>
</tr>

<tr>
<td id="RC_PROTOCOL_ERROR">RC_PROTOCOL_ERROR</td>
<td>463</td>
<td>''Protocol error''</td>
</tr>

<tr>
<td id="RC_NO_STREAM">RC_NO_STREAM</td>
<td>473</td>
<td>''No stream''</td>
</tr>

<tr>
<td id="RC_OLD_UNIVERSE">RC_OLD_UNIVERSE</td>
<td>487</td>
<td>''Old universe''
:Universe is too outdated to be compatible.</td>
</tr>

<tr>
<td id="RC_OLD_WORLD">RC_OLD_WORLD</td>
<td>488</td>
<td>''Old world''
:World is too outdated to be compatible.</td>
</tr>

<tr>
<td id="RC_WORLD_NOT_RUNNING">RC_WORLD_NOT_RUNNING</td>
<td>489</td>
<td>''World not running''
:Unable to stop a world that is not running.</td>
</tr>
</table>

==Not used by the free SDK==

<table class="sortable" border="border" cellpadding="4" cellspacing="0" width="100%">
<tr><th align="left" width="30%">Reason code</th><th align="left" width="10%">Value</th><th align="left" width="60%">Description</th></tr>
<tr>
<td id="RC_UNABLE_TO_MAIL_BACK_NUMBER">RC_UNABLE_TO_MAIL_BACK_NUMBER</td>
<td>14</td>
<td>''Unable to mail back number''</td>
</tr>

<tr>
<td id="RC_IDENTITY_ALREADY_IN_USE">RC_IDENTITY_ALREADY_IN_USE</td>
<td>39</td>
<td>''Identity already in use''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_REPORT_LOCATION">RC_UNABLE_TO_REPORT_LOCATION</td>
<td>40</td>
<td>''Unable to report location''</td>
</tr>

<tr>
<td id="RC_INVALID_EMAIL">RC_INVALID_EMAIL</td>
<td>41</td>
<td>''Invalid email''</td>
</tr>
<tr>
<td id="RC_UNIVERSE_FULL">RC_UNIVERSE_FULL</td>
<td>45</td>
<td>''Universe full''</td>
</tr>

<tr>
<td id="RC_BILLING_TIMEOUT">RC_BILLING_TIMEOUT</td>
<td>46</td>
<td>''Billing timeout''</td>
</tr>

<tr>
<td id="RC_BILLING_RECV_FAILED">RC_BILLING_RECV_FAILED</td>
<td>47</td>
<td>''Billing recv failed''</td>
</tr>

<tr>
<td id="RC_BILLING_RESPONSE_INVALID">RC_BILLING_RESPONSE_INVALID</td>
<td>48</td>
<td>''Billing response invalid''</td>
</tr>

<tr>
<td id="RC_BILLING_REJECTED">RC_BILLING_REJECTED</td>
<td>55</td>
<td>''Billing rejected''</td>
</tr>

<tr>
<td id="RC_BILLING_BLOCKED">RC_BILLING_BLOCKED</td>
<td>56</td>
<td>''Billing blocked''</td>
</tr>

<tr>
<td id="RC_BETA_REQUIRED">RC_BETA_REQUIRED</td>
<td>79</td>
<td>''Beta required''</td>
</tr>

<tr>
<td id="RC_INVALID_USER_COUNT">RC_INVALID_USER_COUNT</td>
<td>81</td>
<td>''Invalid user count''</td>
</tr>

<tr>
<td id="RC_PRIVATE_WORLD">RC_PRIVATE_WORLD</td>
<td>91</td>
<td>''Private world''</td>
</tr>

<tr>
<td id="RC_NO_TOURISTS">RC_NO_TOURISTS</td>
<td>92</td>
<td>''No tourists''</td>
</tr>

<tr>
<td id="RC_CANT_CHANGE_OWNER">RC_CANT_CHANGE_OWNER</td>
<td>211</td>
<td>''Can't change owner''</td>
</tr>

<tr>
<td id="RC_JOIN_REFUSED">RC_JOIN_REFUSED</td>
<td>250</td>
<td>''Join refused''</td>
</tr>

<tr>
<td id="RC_TOO_MANY_RESETS">RC_TOO_MANY_RESETS</td>
<td>427</td>
<td>''Too many resets''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_REGISTER_RESOLVE">RC_UNABLE_TO_REGISTER_RESOLVE</td>
<td>452</td>
<td>''Unable to register resolve''</td>
</tr>

<tr>
<td id="RC_WORLD_FULL">RC_WORLD_FULL</td>
<td>465</td>
<td>''World full''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_BIND">RC_UNABLE_TO_BIND</td>
<td>468</td>
<td>''Unable to bind''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_LISTEN">RC_UNABLE_TO_LISTEN</td>
<td>469</td>
<td>''Unable to listen''</td>
</tr>

<tr>
<td id="RC_UNABLE_TO_ACCEPT">RC_UNABLE_TO_ACCEPT</td>
<td>470</td>
<td>''Unable to accept''</td>
</tr>

<tr>
<td id="RC_EMAIL_CHANGE_NOT_ALLOWED">RC_EMAIL_CHANGE_NOT_ALLOWED</td>
<td>525</td>
<td>''Email change not allowed''</td>
</tr>

<tr>
<td id="RC_NAME_CHANGE_NOT_ALLOWED">RC_NAME_CHANGE_NOT_ALLOWED</td>
<td>526</td>
<td>''Name change not allowed''</td>
</tr>

<tr>
<td id="RC_EMAIL_ALREADY_USED">RC_EMAIL_ALREADY_USED</td>
<td>527</td>
<td>''Email already used''</td>
</tr>

<tr>
<td id="RC_EMAIL_NOT_ALLOWED">RC_EMAIL_NOT_ALLOWED</td>
<td>528</td>
<td>''Email not allowed''</td>
</tr>

<tr>
<td id="RC_WORLD_REDIRECT">RC_WORLD_REDIRECT</td>
<td>529</td>
<td>''World redirect''
:TODO: Is this ever used in the SDK?</td>
</tr>
</table>

[[Category:SDK]]

Template:SDK added in

2025-04-07T19:23:34Z

Xan: Created page with "<table id="toc" style="width:25em; margin:0 0 0.5em 1em; float:right;"> <tr><th align="center" bgcolor="55bbff" colspan="3">Minimum requirements</th></tr> <tr><th align="center" bgcolor="77ddff" colspan="3">Added in version {{{version}}}</th></tr> {{{sdk{{{sdk|}}}|<tr><td align="right" valign="top" width="50%">SDK</td><td align="left" colspan="2" valign="top">build {{{sdk}}}</td></tr>}}} {{{world{{{world|}}}|<tr><td align="right" valign="top" width="50%">World</td><td al..."

<table id="toc" style="width:25em; margin:0 0 0.5em 1em; float:right;">
<tr><th align="center" bgcolor="55bbff" colspan="3">Minimum requirements</th></tr>
<tr><th align="center" bgcolor="77ddff" colspan="3">Added in version {{{version}}}</th></tr>
{{{sdk{{{sdk|}}}|<tr><td align="right" valign="top" width="50%">SDK</td><td align="left" colspan="2" valign="top">build {{{sdk}}}</td></tr>}}}
{{{world{{{world|}}}|<tr><td align="right" valign="top" width="50%">World</td><td align="left" colspan="2" valign="top">build {{{world}}}</td></tr>}}}
{{{universe{{{universe|}}}|<tr><td align="right" valign="top" width="50%">Universe</td><td align="left" colspan="2" valign="top">build {{{universe}}}</td></tr>}}}
{{{browser{{{browser|}}}|<tr><td align="right" valign="top" width="50%">Browser</td><td align="left" colspan="2" valign="top">build {{{browser}}}</td></tr>}}}
</table><includeonly>[[Category:SDK {{{version}}}|{{{sort{{{sort|}}}|{{{sort}}}}}}]]</includeonly><noinclude>[[Category: Templates]]</noinclude>

Aw init

2025-04-07T19:23:02Z

Xan: Created page with "{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}} __NOTOC__ int aw_init (int <var>build</var>) ==Description== Initializes the SDK. ==Callback== None (returns immediately) ==Notes== This method or aw_init_bind must be called once before any other methods in the API. It will do an implicit aw_term if the SDK has already been successfully initialized. Thus, there is no need to call aw_term for each additional call to this method, as there is n..."

{{SDK added in|version=2.1|sdk=13|world=|universe=|browser=}}

__NOTOC__

int aw_init (int <var>build</var>)

==Description==
Initializes the SDK.

==Callback==
None (returns immediately)

==Notes==
This method or [[aw_init_bind]] must be called once before any other methods in the API. It will do an implicit [[aw_term]] if the SDK has already been successfully initialized. Thus, there is no need to call [[aw_term]] for each additional call to this method, as there is no reference count.

If successful then the tick count returned by [[aw_tick]] is reset to 0 and the pseudo-random number generator used by [[aw_random]] is seeded.

==Arguments==
;build:AW_BUILD in Aw.h defines the build of Aw.dll (or libaw_sdk.so for Linux) it was distributed with and should be passed as the value of this argument.

==Argument attributes==
None

==Return values==
;[[SDK Reason Codes#RC_SUCCESS|RC_SUCCESS]]:
;[[SDK Reason Codes#RC_VERSION_MISMATCH|RC_VERSION_MISMATCH]]:Aw.h and Aw.dll (or libaw_sdk.so for Linux) are from different builds of the SDK.

==Returned attributes==
None

==Usage==
#include "Aw.h"
#include "[[Reason.h]]"

int main (int argc, char *argv[])
{
if ([[aw_init]] (AW_BUILD) != [[SDK Reason Codes#RC_SUCCESS|RC_SUCCESS]])
{
printf ("Build #%d of Aw.dll is required to run this bot.\n", AW_BUILD);
return 1;
}

/* ... */

[[aw_term]] ();
return 0;
}

==See also==
*[[SDK_Application_Structure|Application structure]]
*[[aw_init_bind]]
*[[aw_random]]
*[[aw_term]]
*[[aw_tick]]

[[Category: SDK Methods|I]]

SDK Application Structure

2025-04-07T19:22:35Z

Xan: Created page with "A typical SDK application has the following organization: # '''Initialization''' ## Call aw_init to initialize the API ## Call aw_event_set to install event handlers ## Call aw_create to create one or more instances ## Call aw_login for each instance to log that instance into Active Worlds ## Call aw_enter for each instance to enter that instance into a world # '''Event Loop''' ## Call aw_wait and res..."

A typical [[SDK]] application has the following organization:

# '''Initialization'''
## Call [[aw_init]] to initialize the API
## Call [[aw_event_set]] to install [[SDK Events|event]] handlers
## Call [[aw_create]] to create one or more [[SDK Multiple Instances|instances]]
## Call [[aw_login]] for each instance to log that instance into Active Worlds
## Call [[aw_enter]] for each instance to enter that instance into a world
# '''Event Loop'''
## Call [[aw_wait]] and respond to events
# '''Shut Down'''
## Call [[aw_destroy]] to destroy each instance
## Call [[aw_term]] to shutdown the API

Applications do not necessarily need to follow this structure. However all applications must call [[aw_init]] before calling any other API methods and call [[aw_create]] at least once in order to create an instance.

An ''instance'' refers to a single login session within Active Worlds. Each session has a single connection to the universe server as well as an additional optional connection to a single world server. For example, each time you run the Active Worlds Browser it creates one instance for your login session. A single instance can only be at a single location in a single world at any one time, however an SDK application can create and manage many instances at once.

Instances are allocated and initialized for the application by [[aw_create]], and are destroyed by [[aw_destroy]]. Applications that only use a single instance (the "typical" case) are the easiest to write and do not need to worry about storing or managing the instance handle that is returned by [[aw_create]]. Applications that use multiple instances need to keep track of the instance handles returned by [[aw_create]] and must use [[aw_instance_set]] to specify which instance each particular operation is intended for.

'''Example:''' Botware Inc. wants to have two bots in their world stationed at two different locations, but which share common knowledge of which users have spoken to which bot. Botware implements their bots using a single SDK application which calls [[aw_create]], [[aw_login]], and [[aw_enter]] twice, once for each bot.

An instance must have an owner. An owner is the Active Worlds citizen who owns and is responsible for the instance. The owner is identified during the call to [[aw_create]] by his or her citizen number and privilege password. Keep in mind that a single citizen can only have a limited number of bot instances running in the universe at any one time (typically the limit is 3 although it can be adjusted by the universe administrator.) The instance owner's citizen number is used to determine permissions and object ownership (if the SDK application builds objects) as if the instance were a regular citizen. Note that an owner does not need to be logged in in order for his or her bots to run.

'''Example:''' Botware Inc. would like their bots to be able to modify signs in their world to point to different advertisers, but they don't want the public to be able to build in their world. To do this, they have their bots log in as owned by citizen Botware, who has build rights in their world according to the world options.

Note that SDK applications are neither citizens nor tourists, they are a separate class of Active Worlds user. Typically, we just refer to them as "[[bots]]."

[[Category:SDK]]

SDK

2025-04-07T19:22:02Z

Xan:

__NOTOC__ __NOEDITSECTION__

[[Image:CustomsAide.jpg|right|frame|Screenshot of the Customs Aide bot in AWGate]]

The [[Delta Worlds (software)|Active Worlds]] Software Development Kit (SDK), first released on September 8th, 1998, is a Client-API (Application Interface for programming client applications) targeted at the programmer community within Activeworlds.

It provides an easy way for programmers to develop applications that function within the Active Worlds virtual environment. The most common type of application for the SDK is a bot (typically an avatar that inhabits a virtual world and interacts with users, but which is driven by a computer program instead of a human being), however there are many other potential applications. For example, the SDK could be used to develop an automated program that explores a world and creates a map. Also, the SDK allows universe administrators to develop administration utilities to help manage their own Active Worlds universes.

The core component of the SDK is the file aw.dll, a Windows DLL that implements the entire Active Worlds client/server protocol. To develop an application using the Active Worlds SDK, a programmer simply writes a C program which includes the header file aw.h and links to the import library aw.lib. The compiled executable can be run from any PC anywhere as long as that PC has a network connection to the Active Worlds Universe and aw.dll is available on that PC.

=== SDK Versions ===

The standard C/C++ and [[PHP]]/[[COM SDK|COM]] versions of the SDK are [[#Related_Links| available]].
The SDK can be loaded directly from script engines like Python, node.js, PHP, and many more without a wrapper.

First time users of the SDK should start by downloading the version of the SDK appropriate for them, then reading over these help files and reviewing the sample programs.([[SDK Sample Program 1|1]])([[SDK Sample Program 2|2]] and [[PHP]])

==Introduction==

===Concepts===
*[[SDK Application Structure|Structure of an SDK application]]
*[[SDK Event Handlers|Event handlers]]
*[[SDK Attributes|Attributes]]
*[[SDK Multiple Instances|Multiple instances]]
*[[SDK Asynchronous Operation|Asynchronous operation]]
*[[SDK Multithreading|Multithreading model]]
*[[SDK FAQ|Frequently asked questions]]
*[[SDK Sample Program 1|Sample Program 1]]
*[[SDK Sample Program 2|Sample Program 2]]

===Uses===
*[[SDK Property|Property]]
*[[SDK Terrain|Terrain]]
*[[Propdump|Property Format & Code Sniplets]]
*[[Elevdump|Elevation Format & Code Sniplets]]
*[[Atdump|World Attributes Format & Code Sniplets]]
*[[HUD]]
*[[Toolbars]]
*[[Movers]]
*[[SDK Global Mode|Global mode]]
*[[SDK World Server Administration|World server administration]]

==Reference==
*[[Attribute|Attributes]]
*[[List of SDK Data Structures|Data structures]]
*[[:Category:SDK Events|Events]]
*[[:Category:SDK Callbacks|Callbacks]]
*[[:Category:SDK Methods|Methods]]
*[[SDK Reason Codes|Reason codes]]

=== Wrappers for Geeks ===

A third-party wrapper of the C/C++ SDK for .NET is available here: https://github.com/Bloyteg/AW.SDK.Core.

A SDK wrapper for the [https://www.autoitscript.com/site/ AutoIt scripting language] along with information on how to use it: https://github.com/locodarwin/AWSDK-For-AutoIt

Further third party wrappers for Python, Perl, LUA and Ruby have been available online, yet aren't linked to this site.

==Related Links==
*[http://www.activeworlds.com/sdk/download.htm SDK Official download page]
*[http://wiki.activeworlds.com/index.php?title=SDK Official SDK documentation]
*[https://github.com/Bloyteg/AW.SDK.Core/ ActiveWorlds SDK .NET Wrapper] - Leads to third party site on GitHub

[[Category: SDK]]

SDK

2025-04-07T19:21:37Z

Xan:

__NOTOC__ __NOEDITSECTION__

[[Image:CustomsAide.jpg|right|frame|Screenshot of the Customs Aide bot in AWGate]]

The [[Active Worlds (software)|Delta Worlds]] Software Development Kit (SDK), first released on September 8th, 1998, is a Client-API (Application Interface for programming client applications) targeted at the programmer community within Activeworlds.

It provides an easy way for programmers to develop applications that function within the Active Worlds virtual environment. The most common type of application for the SDK is a bot (typically an avatar that inhabits a virtual world and interacts with users, but which is driven by a computer program instead of a human being), however there are many other potential applications. For example, the SDK could be used to develop an automated program that explores a world and creates a map. Also, the SDK allows universe administrators to develop administration utilities to help manage their own Active Worlds universes.

The core component of the SDK is the file aw.dll, a Windows DLL that implements the entire Active Worlds client/server protocol. To develop an application using the Active Worlds SDK, a programmer simply writes a C program which includes the header file aw.h and links to the import library aw.lib. The compiled executable can be run from any PC anywhere as long as that PC has a network connection to the Active Worlds Universe and aw.dll is available on that PC.

=== SDK Versions ===

The standard C/C++ and [[PHP]]/[[COM SDK|COM]] versions of the SDK are [[#Related_Links| available]].
The SDK can be loaded directly from script engines like Python, node.js, PHP, and many more without a wrapper.

First time users of the SDK should start by downloading the version of the SDK appropriate for them, then reading over these help files and reviewing the sample programs.([[SDK Sample Program 1|1]])([[SDK Sample Program 2|2]] and [[PHP]])

==Introduction==

===Concepts===
*[[SDK Application Structure|Structure of an SDK application]]
*[[SDK Event Handlers|Event handlers]]
*[[SDK Attributes|Attributes]]
*[[SDK Multiple Instances|Multiple instances]]
*[[SDK Asynchronous Operation|Asynchronous operation]]
*[[SDK Multithreading|Multithreading model]]
*[[SDK FAQ|Frequently asked questions]]
*[[SDK Sample Program 1|Sample Program 1]]
*[[SDK Sample Program 2|Sample Program 2]]

===Uses===
*[[SDK Property|Property]]
*[[SDK Terrain|Terrain]]
*[[Propdump|Property Format & Code Sniplets]]
*[[Elevdump|Elevation Format & Code Sniplets]]
*[[Atdump|World Attributes Format & Code Sniplets]]
*[[HUD]]
*[[Toolbars]]
*[[Movers]]
*[[SDK Global Mode|Global mode]]
*[[SDK World Server Administration|World server administration]]

==Reference==
*[[Attribute|Attributes]]
*[[List of SDK Data Structures|Data structures]]
*[[:Category:SDK Events|Events]]
*[[:Category:SDK Callbacks|Callbacks]]
*[[:Category:SDK Methods|Methods]]
*[[SDK Reason Codes|Reason codes]]

=== Wrappers for Geeks ===

A third-party wrapper of the C/C++ SDK for .NET is available here: https://github.com/Bloyteg/AW.SDK.Core.

A SDK wrapper for the [https://www.autoitscript.com/site/ AutoIt scripting language] along with information on how to use it: https://github.com/locodarwin/AWSDK-For-AutoIt

Further third party wrappers for Python, Perl, LUA and Ruby have been available online, yet aren't linked to this site.

==Related Links==
*[http://www.activeworlds.com/sdk/download.htm SDK Official download page]
*[http://wiki.activeworlds.com/index.php?title=SDK Official SDK documentation]
*[https://github.com/Bloyteg/AW.SDK.Core/ ActiveWorlds SDK .NET Wrapper] - Leads to third party site on GitHub

[[Category: SDK]]