removeChild(child) → {DisplayObject} Removes a child from the container. Parameters Name Type Description child DisplayObject The DisplayObject to remove Returns DisplayObject - The child that was removed. Inherited From PIXI.DisplayObjectContainer#removeChild Source code: pixi/display/DisplayObjectContainer.js (Line 171)

removeChildAt(index) → {DisplayObject} Removes a child from the specified index position. Parameters Name Type Description index Number The index to get the child from Returns DisplayObject - The child that was removed. Inherited From PIXI.DisplayObjectContainer#removeChildAt Source code: pixi/display/DisplayObjectContainer.js (Line 191)

[readonly] previousPosition : Phaser.Point The position the Game Object was located in the previous frame. Inherited From Phaser.Component.Core#previousPosition Source code: gameobjects/components/Core.js (Line 225)

[readonly] previousRotation : number The rotation the Game Object was in set to in the previous frame. Value is in radians. Inherited From Phaser.Component.Core#previousRotation Source code: gameobjects/components/Core.js (Line 232)

preUpdate() → {boolean} Automatically called by World.preUpdate. Returns boolean - True if the Sprite was rendered, otherwise false. Inherited From Phaser.Sprite#preUpdate Source code: gameobjects/Sprite.js (Line 107)

play(name, frameRate, loop, killOnComplete) → {Phaser.Animation} Plays an Animation. The animation should have previously been created via animations.add. If the animation is already playing calling this again won't do anything.If you need to reset an already running animation do so directly on the Animation object itself or via AnimationManager.stop. Parameters Name Type Argument Default Description name string The name of the animation to be played, e.g. "fire", "walk", "jump". Must

pendingDestroy : boolean A Game Object is that is pendingDestroy is flagged to have its destroy method called on the next logic update.You can set it directly to allow you to flag an object to be destroyed on its next update. This is extremely useful if you wish to destroy an object from within one of its own callbackssuch as with Buttons or other Input events. Inherited From Phaser.Component.Core#pendingDestroy Source code: gameobjects/components/Core.js (Line 259)

[readonly] physicsType : number The const physics body type of this object. Inherited From Phaser.Sprite#physicsType Source code: gameobjects/Sprite.js (Line 61)

outOfCameraBoundsKill : boolean If this and the autoCull property are both set to true, then the kill methodis called as soon as the Game Object leaves the camera bounds. Inherited From Phaser.Component.InWorld#outOfCameraBoundsKill Source code: gameobjects/components/InWorld.js (Line 115)

overlap(displayObject) → {boolean} Checks to see if the bounds of this Game Object overlaps with the bounds of the given Display Object,which can be a Sprite, Image, TileSprite or anything that extends those such as Button or provides a getBounds method and result. This check ignores the hitArea property if set and runs a getBounds comparison on both objects to determine the result. Therefore it's relatively expensive to use in large quantities, i.e. with lots of Sprites at a high frequency.I