Weapon#debug()

debug(x, y, debugBodies)

Uses Game.Debug to draw some useful information about this Weapon, including the number of bullets
both in-flight, and available. And optionally the physics debug bodies of the bullets.

Parameters

Name	Type	Argument	Default	Description
`x`	integer	<optional>	16	The coordinate, in screen space, at which to draw the Weapon debug data.
`y`	integer	<optional>	32	The coordinate, in screen space, at which to draw the Weapon debug data.
`debugBodies`	boolean	<optional>	false	Optionally draw the physics body of every bullet in-flight.

Source code: plugins/weapon/WeaponPlugin.js (Line 1086)

Links:

http://phaser.io/docs/2.6.2/Phaser.Weapon.html#debug

doc_phaser

2017-02-14 11:19:49

Comments

Popular Articles

Weapon#Weapon new Weapon(game, parent) The Weapon Plugin provides the ability to easily create a bullet pool and manager. Weapons fire Phaser.Bullet objects, whi

Weapon#bulletFrameCycle bulletFrameCycle : boolean If you've added a set of frames via Weapon.setBulletFrames then you can optionallychose for each Bullet fired to use the

GameObjectFactory#weapon() weapon(quantity, key, frame, group) → {Phaser.Weapon} Weapons provide the ability to easily create a bullet pool and manager. Weapons fire Phaser.B

Weapon.KILL_WEAPON_BOUNDS [static] KILL_WEAPON_BOUNDS : integer A bulletKillType constant that automatically kills the bullets when they leave the Weapon.bounds rectangle.

Weapon#y y : number The y coordinate from which bullets are fired. This is the same as Weapon.fireFrom.y, andcan be overridden by the Weapon.fire arguments.