The AI-related method are grouped inside this object, for easier access

An array of all elements in this scene, use it with ID Strings. Bullets are not here

All the bullets currently active in the scene are here

An array of all characters for fast loop access. For "id" access use the .all array

Were this scene is drawn

Retrieves controller from this scene

Scene depth in pixels

The global light for this scene. Use this property to change light properties such as intensity and color

An array of all elements for fast loop access. For "id" access use the .all array. Bullets are not here

An array of all floors for fast loop access. For "id" access use the .all array

Scene height in pixels

Every Scene is automatically assigned and ID

An array of all lights for fast loop access. For "id" access use the .all array

An array of all objects for fast loop access. For "id" access use the .all array

Indicates if the scene is loaded and ready

An string indicating the scene's current status

An array of all walls for fast loop access. For "id" access use the .all array

Scene width in pixels.

Creates a new bullet and adds it to the scene. Note that bullets use their own render system. The bulletRenderer interface allows you to have complex things such as trails. If it was integrated with the standard renderer, your bullets would have to be standard Sprites, and I dind't like that.

Note to developers: bullets are reused. Creating new objects is slow, and depending on your game you could have a lot being created and destroyed. The engine uses an object pool to reuse "dead" bullets and minimize the amount of new() calls. This is transparent to you but I think this information can help tracking weird bugs

Creates a new camera associated to the scene

Creates a new character an adds it to the scene

Creates a new light and adds it to the scene. You won't see the light until you call its render() or moveTo() methods

This Method is called to disable the scene. It will disable all controllers associated to the scene and its elements. The engine no longer calls this method when the scene is hidden. Do it manually when needed. A typical use of manual enabling/disabling of scenes is pausing the game or showing a dialog box of any type.

See also

This Method is called to enable the scene. It will enable all controllers associated to the scene and its elements. The engine no longer calls this method when the scene is shown. Do it manually when needed. A typical use of manual enabling/disabling of scenes is pausing the game or showing a dialog box of any type.

See also

Starts initialization process

Removes a bullet from the scene. Bullets are automatically removed when they hit something, but you If you can't wait for them to be delete, you can do it manually.

Removes a character from the scene. This is not the same as hiding the character, this removes the element completely from the scene

Removes an omni light from the scene. This is not the same as hiding the light, this removes the element completely from the scene

Use this method to completely rerender the scene. However, under normal circunstances there shouldn't be a need to call this manually

This method sets the active camera for this scene. The camera position determines the viewable area of the scene

Normally you don't need to call this method manually. When an scene is shown, this method is called to initialize the render engine for this scene ( this involves creating all the Sprites ). This may take a couple of seconds.
Under special circunstances, however, you may want to call this method manually at some point before showing the scene. This is useful is you want the graphic assets to exist before the scene is shown ( to attach Mouse Events for example ).

This method translates scene 3D coordinates to 2D coordinates relative to the Sprite containing the scene

This method translates scene 3D coordinates to 2D coordinates relative to the Stage

This method translates Stage coordinates to scene coordinates. Useful to map mouse events into game events

       function mouseClick(evt:MouseEvent) {
         var coords:Point = this.scene.translateStageCoordsTo3DCoords(evt.stageX, evt.stageY)
         this.hero.character.teleportTo(coords.x,coords.y, this.hero.character.z)
        }
   

This method returns the element under a Stage coordinate, and a 3D translation of the 2D coordinates passed as input. To achieve this it finds which visible elements are under the input pixel, ignoring the engine's internal coordinates. Now you can find out what did you click and which point of that element did you click.

See also

The fScene.LOADCOMPLETE constant defines the value of the type property of the event object for a sceneloadcomplete event. The event is dispatched when the scene finishes loading and processing and is ready to be used

An string describing the process of loading and processing and scene XML definition file. Events dispatched by the scene while loading containg this String as a description of what is happening

The fScene.LOADPROGRESS constant defines the value of the type property of the event object for a scenecloadprogress event. The event is dispatched when the status of the scene changes during scene loading and processing. A listener to this event can then check the scene's status property to update a progress dialog