<p>Phaser is a fast, free and fun open source HTML5 game framework. It uses <ahref="https://github.com/GoodBoyDigital/pixi.js/">Pixi.js</a> for WebGL and Canvas rendering across desktop and mobile web browsers. Games can be compiled to iOS and Android apps via 3rd party tools.</p>
<p>Along with the fantastic open source community Phaser is actively developed and maintained by <ahref="http://www.photonstorm.com">Photon Storm Limited</a>. As a result of rapid support and a developer friendly API Phaser is currently one of the <ahref="https://github.com/showcases/javascript-game-engines">most starred</a> game frameworks on Github.</p>
<p>Thousands of developers worldwide use it. From indies and multi-national digital agencies to schools and Universities. Each creating their own incredible games. Grab the source and join in the fun!</p>
<li><strong>Visit:</strong> The <ahref="http://phaser.io">Phaser website</a> and follow on <ahref="https://twitter.com/photonstorm">Twitter</a> (#phaserjs)</li>
<li><strong>Learn:</strong><ahref="http://phaser.io/docs">API Documentation</a>, <ahref="http://www.html5gamedevs.com/forum/14-phaser/">Support Forum</a> and <ahref="http://stackoverflow.com/questions/tagged/phaser-framework">StackOverflow</a></li>
<li><strong>Code:</strong> 500+ <ahref="http://phaser.io/examples">Source Examples</a> (also available in this <ahref="https://github.com/photonstorm/phaser-examples">git repo</a>)</li>
<li><strong>Read:</strong> Subscribe to the <ahref="https://confirmsubscription.com/h/r/369DE48E3E86AF1E">Newsletter</a> and grab our <ahref="http://phaser.io/shop">Phaser Books</a></li>
<li><strong>Chat:</strong><ahref="http://www.html5gamedevs.com/topic/4470-official-phaserio-irc-channel-phaserio-on-freenode/">#phaserio IRC channel</a> on freenode</li>
<li><strong>Extend:</strong> With <ahref="https://github.com/photonstorm/phaser-plugins">Phaser Plugins</a></li>
<li><strong>Be awesome:</strong> Support our work via <ahref="https://gratipay.com/photonstorm/">Gratipay</a></li>
<h2>What's new in Phaser 2.3.0</h2><divalign="center"><imgsrc="http://phaser.io/images/github/news.jpg"></div>
<blockquote>
<p>26th March 2015</p>
</blockquote>
<p>Phaser 2.3.0 marks the second release in 2015 and easily one of our most significant for a while. In terms of API changes they're actually quite minimal, but under the hood we've taken Phaser for a serious workout.</p>
<p>We've traditionally had something of a 'kitchen sink' issue with Phaser. As we thought of great new features to give you we just added them in. And like too much of a good thing they contributed to an ever growing file size.</p>
<p>So two of the biggest changes 2.3.0 has is an internal shift to using Game Object components, and allowing you to exclude features in your own custom builds. The new build system lets you selectively exclude features from being bundled in: for example if your game doesn't need Gamepad or Keyboard support you can now tell Phaser to skip those parts entirely.</p>
<p><ahref="http://phaser.io/tutorials/creating-custom-phaser-builds">This tutorial</a> explains the process in detail. But the end result is that thanks to these changes we've both managed to remove thousands of lines of code and let you decide what Phaser contains. The minimum build size is now just 83KB minified and gzipped and that's still including both the WebGL and Canvas renderers.</p>
<p>Even though we've been cutting down on size we still managed to pack a whole load of great new features in. For example the new spacial sorting added to Arcade Physics allows for incredible speed increases when dealing with densely populated game worlds. The Loader has received a complete overhaul - now offering full parallel asset loading, sync points and more! The Tilemap system was upgraded to support new Tiled 0.11 editor features. Audio has been also been enhanced, with better marker and loop handling. See the Change Log for all the details.</p>
<p>Your games will run faster, have a smaller footprint and load faster than ever.</p>
<p>But it's not just Phaser that has been updated - we also finally released the <ahref="http://phaser.io">new Phaser web site</a>! For the past few years it was a huge "wall of text", with hundreds of links filling up the single page site. Now it's all changed! with a much more attractive layout and structure. We've got a healthy and constantly updating <ahref="http://phaser.io/news">news section</a>, the <ahref="http://phaser.io/examples">examples</a> have a great new visual showcase and there's even a <ahref="http://phaser.io/sandbox">Sandbox</a> to play in.</p>
<p>It was a lot of hard work but we're super-happy with the result - and judging by our page hits, which are going off the charts, you are too :) We'll be sure to keep enhancing it over the coming months, especially as Phaser 3 development ramps up.</p>
<p>That's all for now. I hope you enjoy Phaser 2.3.0, the new site, the new features and the New Year. Happy coding everyone! See you on the forums.</p>
<h2>Download Phaser</h2><p>Phaser is <ahref="https://github.com/photonstorm/phaser">hosted on Github</a>. There are a number of ways to download it:</p>
<ul>
<li>Clone the git repository via <ahref="https://github.com/photonstorm/phaser.git">https</a>, <ahref="git@github.com:photonstorm/phaser.git">ssh</a> or with the Github <ahref="github-windows://openRepo/https://github.com/photonstorm/phaser">Windows</a> or <ahref="github-mac://openRepo/https://github.com/photonstorm/phaser">Mac</a> clients.</li>
<li>Download as <ahref="https://github.com/photonstorm/phaser/archive/v2.3.0.zip">zip</a> or <ahref="https://github.com/photonstorm/phaser/archive/v2.3.0.tar.gz">tar.gz</a></li>
<li>Download just the build files: <ahref="https://github.com/photonstorm/phaser/releases/download/v2.3.0/phaser.js">phaser.js</a> and <ahref="https://github.com/photonstorm/phaser/releases/download/v2.3.0/phaser.min.js">phaser.min.js</a></li>
<li>Checkout with <ahref="https://github.com/photonstorm/phaser">svn</a></li>
</ul>
<h3>Bower / npm</h3><p>Install via <ahref="http://bower.io">bower</a></p>
<p><code>bower install phaser</code></p>
<p>Install via <ahref="https://www.npmjs.com">npm</a></p>
<p><code>npm install phaser</code></p>
<h3>CDN</h3><p><ahref="http://www.jsdelivr.com/#!phaser">jsDelivr</a> is a "super-fast CDN for developers". Include the following in your html:</p>
<h3>Phaser Sandbox</h3><p>If you'd like to try coding in Phaser right now, with nothing more than your web browser then you can head over to the <ahref="http://phaser.io/sandbox">Phaser Sandbox</a>. You'll find Quick Start templates and a user-friendly editor filled with handy code-completion features.</p>
<h3>Koding</h3><p>Want to try Phaser without downloading anything? <ahref="https://koding.com/Teamwork?import=https://github.com/photonstorm/phaser/archive/master.zip&c=git1">Clone Phaser in Koding</a> and start working right away in their web based development system.</p>
<h3>License</h3><p>Phaser is released under the <ahref="http://opensource.org/licenses/MIT">MIT License</a>.</p>
<p>We have a <ahref="http://phaser.io/tutorials/getting-started">Getting Started Guide</a> which covers all you need to begin developing games with Phaser. From setting up a web server, to picking an IDE and coding your first game.</p>
<p>Prefer <strong>videos</strong> to reading? Lynda.com have published a free course: <ahref="http://www.lynda.com/Phaser-tutorials/HTML5-Game-Development-Phaser/163641-2.html">HTML5 Game Development with Phaser</a></p>
<p>The single biggest Phaser resource is the new <ahref="http://phaser.io/news">Phaser web site</a>. It has hundreds of tutorials listed and fresh ones are added every week, so keep coming back to see what's new!</p>
<p>Using Phaser with <strong>TypeScript</strong>? Check out this great series of <ahref="http://www.gamefromscratch.com/page/Adventures-in-Phaser-with-TypeScript-tutorial-series.aspx">Game From Scratch</a> tutorials.</p>
<h3>Source Code Examples</h3><p>Ever since we started Phaser we've been growing and expanding our extensive set of source code examples. Currently there are over 500 of them!</p>
<p>Browse the <ahref="http://phaser.io/examples">Phaser Examples</a> or clone the <ahref="https://github.com/photonstorm/phaser-examples">examples repo</a> and eat your heart out!</p>
<p>We've been busy writing books about Phaser. Available now:</p>
<ul>
<li><ahref="https://leanpub.com/phasertweenmanager">A Guide to the Phaser Tween Manager</a> Book + Code Bundle</li>
<li><ahref="https://leanpub.com/phaserscalemanager">A Guide to the Phaser Scale Manager</a></li>
</ul>
<p>With more on the way. <ahref="http://www.html5gamedevs.com/topic/10962-which-phaser-book-would-you-like-to-see-next/">Vote on the next title</a> to be written.</p>
<h3>Game Mechanic Explorer</h3><p>The <ahref="http://gamemechanicexplorer.com">Game Mechanic Explorer</a> is a great interactive way to learn how to develop specific game mechanics in Phaser. Well worth exploring once you've got your dev environment set-up.</p>
<h3>Mighty Editor - Visual Game Editor</h3><p><ahref="http://mightyfingers.com/">MightyEditor</a> is a browser-based visual Phaser game editor. Create your maps with ease, position objects and share them in seconds. It also exports to native Phaser code. Excellent for quickly setting-up levels and scenes.</p>
<p><aname="using-phaser"></a></p>
<h2>Using Phaser</h2><p>Phaser is provided ready compiled in the <code>build</code> folder of the repository. There are both plain and minified versions. The plain version is for use during development and the minified version for production.</p>
<h3>Custom Builds</h3><p>As of Phaser 2.3.0 we now include a brand new build system which allows you to strip out lots of additional features you may not require, saving hundreds of KB in the process. Don't use any Sound in your game? Then you can now exclude the entire sound system. Don't need Keyboard support? That can be stripped out too.</p>
<p>As a result of this work the minimum build size of Phaser is now just 83KB minified and gzipped.</p>
<p>See the <ahref="http://phaser.io/tutorials/creating-custom-phaser-builds">Creating a Custom Phaser Build</a> tutorial for details.</p>
<h3>Building from source</h3><p>Should you wish to build Phaser from source you can take advantage of the provided <ahref="http://gruntjs.com/">Grunt</a> scripts. Ensure you have the required packages by running <code>npm install</code> first.</p>
<p>Run <code>grunt</code> to perform a default build to the <code>dist</code> folder.</p>
<p>If you change either Pixi.js or P2 then use the Grunt tasks <code>replace:pixi</code> and <code>replace:p2</code> respectively. These tasks patch their UMD strings so they work properly with Phaser under requireJS.</p>
<p><aname="games"></a></p>
<h2>Games made with Phaser</h2><p>Thousands of games have been made in Phaser. From game jam entries to titles for some of the largest entertainment brands in the world. This is just a tiny sample.</p>
<p>We add <ahref="http://phaser.io/news/category/game">new games</a> to the Phaser site regularly, be sure to send us yours when it's finished!</p>
<p><aname="requirements"></a></p>
<h2>Requirements</h2><p>Phaser requires a web browser that supports the <ahref="http://caniuse.com/#feat=canvas">canvas tag</a>. This includes Internet Explorer 9+, Firefox, Chrome, Safari and Opera on desktop. iOS Safari, Android Browser and Chrome for Android are supported on mobile.</p>
<p>While Phaser does its best to ensure a consistent cross-platform experience always be aware of browser and device limitations. This is especially important with regard to memory and GPU limitations on mobile, and legacy browser HTML5 compatibility.</p>
<h3>IE9</h3><p>If you need to support IE9 / Android 2.x <strong>and</strong> use P2 physics then you must use the polyfill in the <code>resources/IE9 Polyfill</code> folder. If you don't use P2 (or don't care about IE9!) you can skip this.</p>
<h3>JavaScript and TypeScript</h3><p>Phaser is developed in JavaScript. We've made no assumptions about how you like to code and were careful not to impose a strict structure upon you. You won't find Phaser split into modules, requiring a build step, or making you use a class / inheritance OOP approach. That doesn't mean you can't do so, it just means we don't <em>force</em> you to. It's your choice.</p>
<p>If you code with <ahref="http://www.typescriptlang.org/">TypeScript</a> there are comprehensive definition files in the <code>typescript</code> folder. They are for TypeScript 1.4+.</p>
<p><aname="road-map"></a></p>
<h2>Road Map</h2><p>All Phaser development is now taking place on the Phaser 3 project. The Phaser 2 branch will still be supported and issues fixed, but roadmap features have been migrated over to Phaser 3.</p>
<p><aname="phaser3"></a></p>
<h2>Phaser 3</h2><p>We're now several months in to development of Phaser 3. We've been working hard on creating a brand new and extremely powerful renderer. Progress reports are posted to the web site and <ahref="https://github.com/photonstorm/phaser3">Phaser 3 repo</a>.</p>
<p>There is still plenty of time to add your suggestions and feedback in <ahref="http://www.html5gamedevs.com/topic/7949-the-phaser-3-wishlist-thread/">this forum thread</a>.</p>
<p>If you are an exceptional JavaScript developer and would like to join the Phaser 3 development team then let us know. We have a limited budget available to pay towards your time.</p>
<h2>Change Log</h2><p>Version 2.3.0 - "Tarabon" - 26th March 2015</p>
<h3>Significant Updates</h3><h4>Game Objects and Components</h4><p>All of the core Game Objects have received an important internal restructuring. We have moved all of the common functions to a new set of Component classes. They cover functionality such as 'Crop', 'Physics Body', 'InCamera' and more. You can find the source code to each component in the <code>src/gameobjects/components</code> folder of the repo.</p>
<p>All of the Game Object classes have been restructured to use the new component approach. This puts an end to the "God classes" structure we had before and removes literally hundreds of lines of duplicate code. It also allowed us to add features to Game Objects; for example Bitmap Text objects are now full-class citizens with regard to physics capabilities.</p>
<p>Although this was a big internal shift from an API point of view not much changed - you still access the same methods and properties in the same way as before. Phaser is just a lot leaner under the hood now.</p>
<p>It's worth mentioning that from a JavaScript perspective components are mixins applied to the core game objects when Phaser is instantiated. They are not added at run-time or are dynamic (they never get removed from an object once added for example). Please understand that this is by design.</p>
<p>You can create your own custom Phaser classes, with your own set of active components by copying any of the pre-existing Game Objects and modifying them.</p>
<h4>Custom Builds</h4><p>As a result of the shift to components we went through the entire source base and optimised everything we could. Redundant paths were removed, debug flags removed and new stub classes and hooks were created. What this means is that it's now easier than ever to "disable" parts of Phaser and build your own custom version.</p>
<p>We have always included a couple of extra custom builds with Phaser. For example a build without P2 Physics included. But now you can strip out lots of additional features you may not require, saving hundreds of KB from your build file in the process. Don't use any Sound in your game? Then you can now exclude the entire sound system. Don't need Keyboard support? That can be stripped out too.</p>
<p>As a result of this work the minimum build size of Phaser is now just 83KB (minified and gzipped).</p>
<p>Please see the README instructions on how to create custom builds.</p>
<h4>Arcade Physics</h4><p>We've updated the core of Arcade Physics in a number of significant ways. </p>
<p>First we've dropped lots of internal private vars and moved to using non-cached local vars. Array lengths are no longer cached and we've implemented <code>physicsType</code> properties on Game Objects to speed-up the core World collideHandler. All of these small changes have lead to a nice improvement in speed as a result, and also allows us to now offer things like physics enabled BitmapText objects.</p>
<p>More importantly we're now using a spacial pre-sort for all Sprite vs. Group and Group vs. Group collisions. You can define the direction the sort will prioritize via the new <code>sortDirection</code> property. By default it is set to <code>Phaser.Physics.Arcade.LEFT_RIGHT</code>. For example if you are making a horizontally scrolling game, where the player starts on the left of the world and moves to the right, then this sort order will allow the physics system to quickly eliminate any objects to the right of the player bounds. This cuts down on the sheer volume of actual collision checks needing to be made. In a densely populated level it can improve the fps rate <em>dramatically</em>.</p>
<p>There are 3 other directions available (<code>RIGHT_LEFT</code>, <code>TOP_BOTTOM</code> and <code>BOTTOM_TOP</code>) and which one you need will depend on your game type. If you were making a vertically scrolling shoot-em-up then you'd pick <code>BOTTOM_TOP</code> so it sorts all objects above and can bail out quickly. There is also <code>SORT_NONE</code> if you would like to pre-sort the Groups yourself or disable this feature.</p>
<p>Another handy feature is that you can switch the <code>sortDirection</code> at run-time with no loss of performance. Just make sure you do it <em>before</em> running any collision checks. So if you had a large 8-way scrolling world you could set the <code>sortDirection</code> to match the direction the player was moving in and adjust it in real-time, getting the benefits as you go. My thanks to Aaron Lahman for inspiring this update.</p>
<h4>Phaser.Loader</h4><p>The Phaser.Loader has been updated to support parallel downloads which is now enabled by default (you can toggle it via the <code>Loader.enableParallel</code> flag) as well as adding future extensibility points with a pack/file unified filelist and an inflight queue.</p>
<p>There are no <em>known</em> incompatibilities with the previous Loader. Be aware that with parallel downloading enabled the order of the Loader events may vary (as can be seen in the "Load Events" example).</p>
<p>The parallel file concurrency limit is available in <code>Loader.maxParallelDownloads</code> and is set to 4 by default. Under simulated slower network connections parallel loading was a good bit faster than sequential loading. Even under a direct localhost connection parallel loading was never slower, but benefited most when loading many small assets (large assets are more limited by bandwidth); both results are fairly expected.</p>
<p>The Loader now supports synchronization points. An asset marked as a synchronization point must be loaded (or fail to load) before any <em>subsequent</em> assets can be loaded. This is enabled by using the <code>withSyncPoint</code> and <code>addSyncPoint</code> methods. Packs ('packfile' files) and Scripts ('script' files) are treated as synchronization points by default. This allows parallel downloads in general while allowing synchronization of select resources if required (packs, and potentially other assets in the future, can load-around synchronization points if they are written to delay final 'loading').</p>
<p>Additional error handling / guards have been added, and the reported error message has been made more consistent. Invalid XML (when loading) no longer throws an exception but fails the particular file/asset that was being loaded. </p>
<p>Some public methods/properties have been marked as protected, but no (except in case of a should-have-been-private-method) public-facing interfaces have been removed. Some private methods have been renamed and/or removed.</p>
<p>A new XHR object is created for each relevant asset (as there must be a different XHR for each asset loaded in parallel). Online searches indicated that there was no relevant benefit of XHR (as a particular use-case) re-use; and time will be dominated with the resource fetch. With the new flight queue an XHR cache could be re-added, at the cost of some complexity.</p>
<p>The URL is always transformed through transformUrl, which can make adding some one-off special cases like #1355 easier to deal with.</p>
<p>This also incorporates the fast-cache path for Images tags that can greatly speed up the responsiveness of image loading.</p>
<p>Loader.resetLocked is a boolean that allows you to control what happens when the loader is reset, <em>which happens automatically on a State change</em>. If you set <code>resetLocked</code> to <code>true</code> it allows you to populate the loader queue in one State, then swap to another State without having the queue erased, and start the load going from there. After the load has completed you could then disable the lock again as needed.</p>
<p>Thanks to @pnstickne for vast majority of this update.</p>
<h4>Pixi v2</h4><p>We are now using our own custom build of Pixi v2. The Pixi project has moved all development resources over to Pixi v3, but it wasn't ready in time for the release of Phaser 2.3 so we've started applying our own fixes to the version of Pixi that Phaser uses.</p>
<p>As a result we have removed all files from the <code>src/pixi</code> folder that Phaser doesn't use, in order to make this distinction clearer. This includes <code>EventTarget</code>, so if you were relying on that in your game you'll need to add it back in to your local build.</p>
<p>We've also removed functions and properties from Pixi classes that Phaser doesn't require: such as the Interaction Manager, Stage.dirty, etc. This has helped us cut down the source code size and make the docs less confusing, as they no longer show properties for things that weren't even enabled.</p>
<p>We've rolled our own fixes into our version of Pixi, ensuring we keep it as bug-free as possible.</p>
<h3>New Features</h3><ul>
<li><code>Physics.Arcade.isPaused</code> allows you to toggle Arcade Physics processing on and off. If <code>true</code> the <code>Body.preUpdate</code> method will be skipped, halting all motion for all bodies. Note that other methods such as <code>collide</code> will still work, so be careful not to call them on paused bodies.</li>
<li><code>Arcade.Body.friction</code> allows you to have more fine-grained control over the amount of velocity passed between bodies on collision.</li>
<li>BitmapData.text will render the given string to the BitmapData, with optional font, color and shadow settings.</li>
<li>MSPointer.capture allows you to optionally event.preventDefault the pointer events (was previously always on)</li>
<li>MSPointer.event now stores the most recent pointer event.</li>
<li>MSPointer.pointerDownCallback, pointerMoveCallback and pointerUpCallback all allow you to set your own event based callbacks.</li>
<li>MSPointer.button now records which button was pressed down (if any)</li>
<li>Phaser now supports rotated and flipped tiles in tilemaps, as exported from the Tiled map editor (thanks @nkholski #1608)</li>
<li>TilemapParser now supports Tiled 0.11 version maps which includes the <code>rotation</code> property on all Object types.</li>
<li>Tilemap.createFromObjects now checks for a <code>rotation</code> property on the Object and if present will set it as the Sprite.angle (#1433)</li>
<li>If for whatever reason you wish to hide the Phaser banner in the console.log you can set <code>window.PhaserGlobal.hideBanner</code> to <code>true</code> and it will skip the output. Honestly I'd rather if you didn't, but the option is now there.</li>
<li>TilemapLayer.setScale will allow you to apply scaling to a specific Tilemap layer, i.e. <code>layer.setScale(2)</code> would double the size of the layer. The way the Camera responds to the layer is adjusted accordingly based on the scale, as is Arcade collision (thanks @mickez #1605)</li>
<li>SoundManager.setDecodedCallback lets you specify a list of Sound files, or keys, and a callback. Once all of the Sound files have finished decoding the callback will be invoked. The amount of time spent decoding depends on the codec used and file size. If all of the files given have already decoded the callback is triggered immediately.</li>
<li>Sound.loopFull is a new method that will start playback of the Sound and set it to loop in its entirety.</li>
<li>left, right, top and bottom are new properties that contain the totals of the Game Objects position and dimensions, adjusted for the anchor. These are available on any Game Object with the Bounds Component.</li>
<li>Sprite.offsetX and Sprite.offsetY contain the offsets from the Sprite.x/y coordinates to the top-left of the Sprite, taking anchor into consideration.</li>
<li>Emitter.flow now works in a slightly different (and more useful!) way. You can now specify a <code>quantity</code> and a <code>total</code>. The <code>quantity</code> controls how many particles are emitted every time the flow frequency is met. The <code>total</code> controls how many particles will be emitted in total. You can set <code>total</code> to be -1 and it will carry on emitting at the given frequency forever (also fixes #1598 thanks @brianbunch)</li>
<li>ArraySet.removeAll allows you to remove all members of an ArraySet and optionally call <code>destroy</code> on them as well.</li>
<li>GameObject.input.dragStartPoint now stores the coordinates the object was at when the drag started. This value is populated when the drag starts. It can be used to return an object to its pre-drag position, for example if it was dropped in an invalid place in-game.</li>
<li>Text.padding specifies a padding value which is added to the line width and height when calculating the Text size. Allows you to add extra spacing if Phaser is unable to accurately determine the true font dimensions (#1561 #1518)</li>
<li>Game Objects now have a new <code>physicsType</code> property. This maps to a Phaser const such as <code>SPRITE</code> or <code>GROUP</code> and allows Phaser to sort out pairings for collision checks in the core World collide handler much quicker than before.</li>
<li>BitmapText objects can now have physics enabled on them. When the physics body is first created it will use the dimensions of the BitmapText at the time you enable it. If you update the text it will adjust the body width and height as well, however any applied offset will be retained.</li>
<li>BitmapText objects now have an <code>anchor</code> property. This works in a similar way to Sprite.anchor except that it offsets the position of each letter of the BitmapText by the given amount, based on the overall BitmapText width - whereas Sprite.anchor offsets the position the texture is drawn at.</li>
<li>There is a new TypeScript defs file (phaser.comments.d.ts) which now has all of the jsdocs included! (thanks @vulvulune #1559)</li>
<li>Sound.fadeTween is now used for Sound.fadeIn and Sound.fadeOut audio tweens.</li>
<li>Sound.stop and Sound.destroy now halt a fade tween if in effect.</li>
<li>Arcade Physics <code>computeVelocity</code> now allows a max velocity of 0 allowing movement to be constrained to a single axis (thanks @zekoff #1594)</li>
<li>Added missing properties to the InputHandler prototype, reducing hidden class modifications.</li>
<li>Updated docstrap-master toc.js to fix nav scrolling (thanks @abderrahmane-tj @vulvulune #1589)</li>
<li>Added missing plugins member in Phaser.Game class (thanks @Bilge #1568)</li>
<li>Lots of JSDocs fixes (thanks @vulvulune @micahjohnston @Marchys @JesseAldridge)</li>
<li>TilemapLayer.getTiles now returns a copy of the Tiles found by the method, rather than references to the original Tile objects, so you're free to modify them without corrupting the source (thanks @Leekao #1585)</li>
<li>Sprite.events.onDragStart has 2 new parameters <code>x</code> and <code>y</code> which is the position of the Sprite <em>before</em> the drag was started. The full list of parameters is: <code>(sprite, pointer, x, y)</code>. This allows you to retain the position of the Sprite prior to dragging should <code>dragFromCenter</code> have been enabled (thanks @vulvulune #1583)</li>
<li>Device.touch checks if <code>window.navigator.maxTouchPoints</code> is <code>>= 1</code> rather than <code>> 1</code>, which allows touch events to work properly in Chrome mobile emulation.</li>
<li>Loader.XDomainRequest wasn't used for atlas json loading. It has now been moved to the <code>xhrLoad</code> method to ensure it's used for all request if required (thanks @draconisNoctis #1601)</li>
<li>Loader.reset has a new optional 2nd parameter <code>clearEvents</code> which if set to <code>true</code> (the default is false) will reset all event listeners bound to the Loader.</li>
<li>If <code>Body.customSeparateX</code> or <code>customSeparateY</code> is <code>true</code> then the Body will no longer be automatically separated from a <strong>Tilemap</strong> collision or exchange any velocity. The amount of pixels that the Body has intersected the tile is available in <code>Body.overlapX</code> and <code>overlapY</code>, so you can use these values to perform your own separation in your collision callback (#992)</li>
<li>TilemapParser will now set the <code>.type</code> property for ObjectLayer Objects (thanks @mikaturunen #1609)</li>
<li>The Loader now directly calls StateManager.loadComplete rather than the StateManager listening for the loadComplete event, because Loader.reset unbinds this event (and it's easy to accidentally remove it too)</li>
<li>Loader.onLoadComplete is dispatched <em>before</em> the Loader is reset. If you have a <code>create</code> method in your State please note that the Loader will have been reset before this method is called. This allows you to immediately re-use the Loader without having to first reset it manually.</li>
<li>World.setBounds will now adjust the World.x/y values to match those given (#1555)</li>
<li>ArcadePhysics.distanceToPointer now calculates the distance in world space values.</li>
<li>Sound.fadeIn now supports fading from a marker, as well as the entire audio clip, so now works with audio sprites (thanks @vorrin #1413)</li>
<li>Text font components can now be specified as part of "style". There is a breaking change in that the <code>fontWeight</code> now only handles the CSS font-weight component. The <code>fontStyle</code> property handles 'italic', 'oblique', values from font-style. This makes the overall consistency cleaner but some code may need to be updated. This does not affect font-weight/font-style as with setStyle({font:..}). Also fixes overwrite font/size/weight oddities - which may result in different behavior for code that was relying on such. All of the text examples appear to work and modification using the new features (while respecting the change in previous behavior) work better (thanks @pnstickne #1375 #1370)</li>
<li>Loader.audiosprite has a new <code>jsonData</code> parameter. It allows you to pass a pre-existing JSON object (or a string which will be parsed as JSON) to use as the audiosprite data, instead of specifying a URL to a JSON file on the server (thanks @jounii #1447)</li>
<li>Loader.audiosprite has a new <code>autoDecode</code> parameter. If <code>true</code> the audio file will be decoded immediately upon load.</li>
<li>Tile.properties is now unique to that specific Tile, and not a reference to the Tileset index bound properties object. Tile.properties can now be modified freely without impacting other tiles sharing the same id (#1254)</li>
<li>PIXI.TextureSilentFail is a boolean that defaults to <code>false</code>. If <code>true</code> then <code>PIXI.Texture.setFrame</code> will no longer throw an error if the texture dimensions are incorrect. Instead <code>Texture.valid</code> will be set to <code>false</code> (#1556)</li>
<li>InputHandler.enableDrag with a boundsRect set now takes into account the Sprites anchor when limiting the drag (thanks @unindented #1593)</li>
<li>InputHandler.enableDrag with a boundsSprite set now takes into account both the Sprites anchor and the boundsSprite anchor when limiting the drag.</li>
<li>Sound in Web Audio now uses AudioContext.onended to trigger when it will stop playing instead of using a time based value. This is only used if the sound doesn't loop and isn't an audio sprite, but will give a much more accurate <code>Sound.onStop</code> event. It also prevents short audio files from being cut off during playback (#1471) and accounts for time spent decoding.</li>
<li>If you load an image and provide a key that was already in-use in the Cache, then the old image is now destroyed (via <code>Cache.removeImage</code>) and the new image takes its place.</li>
<li>BitmapText has a new <code>maxWidth</code> property that will attempt to wrap the text if it exceeds the width specified.</li>
<li>Group.cursorIndex is the index of the item the Group cursor points to. This replaces Group._cache[8].</li>
<li>Tween.updateTweenData allows you to set a property to the given value across one or all of the current tweens. All of the Tween methods like Tween.delay and Tween.repeat have been updated to use this.</li>
<li>Tween.repeat has a new parameter <code>repeatDelay</code> which allows you to set the delay (in ms) before a tween will repeat itself.</li>
<li>Tween.yoyo has a new parameter <code>yoyoDelay</code> which allows you to set the delay (in ms) before a tween will start a yoyo.</li>
<li>Tween.interpolation has a new parameter <code>context</code> which allows you to define the context in which the interpolation function will run.</li>
<li>ArraySet.getByKey gets an item from the set based on the property strictly equaling the value given.</li>
<li>A State swap now sets the Loader.reset <code>hard</code> parameter to <code>true</code> by default. This will null any Loader.preloadSprite that may have been set.</li>
<li>You can now set a <code>resolution</code> property in your Game Configuration object. This will be read when the Pixi renderer instance is created and used to set the resolution within that (#1621)</li>
<li>Text style has a new optional property: <code>backgroundColor</code> which is a Canvas fill style that is set behind all Text in the Text object. It allows you to set a background color without having to use an additional Graphics object.</li>
<li>The Physics Manager now has a new <code>reset</code> method which will reset the active physics systems. This is called automatically on a State swap (thanks @englercj #1691)</li>
<li>When a State is started and linked to Phaser it has a new property created on it: <code>key</code>, which is the string identifier used by the State.</li>
<li>When the Game first boots it will now call <code>window.focus()</code>. This allows keyboard events to work properly in IE when the game is running inside an iframe. You can stop this from happening by setting <code>window.PhaserGlobal.stopFocus = true</code> (thanks @webholics #1681)</li>
<li>When an Animation completes playback and isn't set to loop it would change the <code>currentFrame</code> property to be the first frame in the set after the <code>onComplete</code> callback had fired. This meant if you set a Sprite to a new frame within an Animation onComplete callback then your change would have been overwritten by the animation itself. This is now no longer the case.</li>
<li>When an Emitter is destroyed via Emitter.destroy it now removes itself from the Phaser Particle Manager, freeing it up for garbage collection and stopping it from being processed.</li>
<li>SoundManager.unlock checks for audio <code>start</code> support and falls back to <code>noteOn</code> if not found.</li>
<li>Sprite.frame and AnimationManager.frame wouldn't return the correct index if a sprite sheet was being used unless it had first been set via the setter.</li>
<li>Error in diffX and diffY calculation in Tilemap.paste (thanks @amelia410 #1446)</li>
<li>Fixed issue in PIXI.canUseNewCanvasBlendModes which would create false positives in browsers that supported <code>multiply</code> in Canvas path/fill ops, but not for <code>drawImage</code> (Samsung S5 for example). Now uses more accurate magenta / yellow mix test.</li>
<li>Fixed FrameData.getFrame index out of bound error (thanks @jromer94 #1581 #1547)</li>
<li>In P2.Body calling adjust mass would desync the debug graphics from the real position of the body (thanks @tomlarkworthy #1549)</li>
<li>Fix CORS loading of BitmapFonts with IE9 (thanks @jeppester #1565)</li>
<li>TileSprites were not detecting Pointer up events correctly because of a branching condition (thanks @integricho #1580 #1551)</li>
<li>TileSprites weren't destroying WebGL textures, leading to eventual out of memory errors (thanks @chacal #1563)</li>
<li>P2.Body.clearCollision default values were incorrectly set to <code>false</code> if no parameters were provided, even though the docs said they were <code>true</code> (thanks @brianbunch #1597)</li>
<li>BitmapText.font wouldn't update an internal Pixi property (fontName) causing the text to fail to change font (thanks @starnut #1602)</li>
<li>Fixed issue in PIXI.Text where it was using the wrong string for descender text measurements.</li>
<li>Sprite.loadTexture and Image.loadTexture now no longer call <code>updateTexture</code> if the texture given is a RenderTexture. This fixes issues with RetroFonts in IE11 WebGL as well as other RenderTexture related IE11 problems (#1310 #1381 #1523)</li>
<li>You can now tint animated Sprites in Canvas mode. Or change the texture atlas frame of a tinted Sprite or Image. Please note that this is pretty expensive (depending in the browser), as the tint is re-applied every time the <em>frame changes</em>. The Pixi tint cache has also been removed to allow for subtle tint color shifts and to avoid blowing up memory. So use this feature sparingly! But at least it does now work (#1070)</li>
<li>ArcadePhysics.moveToPointer no longer goes crazy if the maxTime parameter is given and the Sprite is positioned in a larger game world (thanks @AnderbergE #1472)</li>
<li>Sound.loop even when set for WebAudio wouldn't use the AudioContext loop property because Sound.start was being invoked with an offset and duration. Now if <code>loop</code> is true and no marker is being used it will use the native Web Audio loop support (#1431)</li>
<li>Timer.update was calling the TimerEvent callback even if <code>TimerEvent.pendingDelete</code> was already set to <code>true</code>, causing timer events to stack-up in cases where a new TimerEvent was generated in the callback (thanks @clowerweb #838)</li>
<li>Pointer.stop would call <code>event.preventDefault</code> if <code>Pointer._stateReset</code> was <code>true</code>, which is always <code>true</code> after a State has changed and before Pointer.start has been called. However this broken interacting with DOM elements in the case where the State changes and you immediately try to use the DOM element without first having clicked on the Phaser game. An additional guard was added so <code>preventDefault</code> will now only be called if both <code>_stateReste</code> and <code>Pointer.withinGame</code> are true (thanks @satan6 #1509)</li>
<li>Group.forEach (and many other Group methods) now uses the <code>children.length</code> value directly instead of caching it, which both helps performance and stops the loop from breaking should you remove a Group child in the invoked callback.</li>
<li>Phaser.Ellipse.contains is now working again (thanks @spayton #1524)</li>
<li>PIXI.WebGLRenderer.destroy has been fixed to decrement the <code>glContextId</code> and remove it from the PIXI.instances global. <code>Game.destroy</code> now hooks into this. This now means that you can now delete and create your Phaser game over and over without it crashing WebGL after the 4th attempt (#1260)</li>
<li>World.setBounds if called after you had already started P2 Physics would incorrectly create a new collision group for the wall objects. P2.World now remembers the settings you provide for each wall and the collision group, and re-applies these settings should the world dimensions ever change (thanks @nextht #1455)</li>
<li>InputHandler was using the wrong property in <code>checkBoundsSprite</code> when fixedToCamera (thanks @yig #1613)</li>
<li>Tween.to now correctly accepts arrays are destination values, which makes the Tween interpolate through each value specified in the array using the defined Tween.interpolation method (see new example, thanks @FridayMarch26th #1619)</li>
<li>Tween.interpolationFunction was using the incorrect context to invoke the function. This is now defined in <code>TweenData.interpolationContext</code> and defaults to <code>Phaser.Math</code>. If you provide your own interpolation function then please adjust the context accordingly (thanks @FridayMarch26th #1618)</li>
<li>Graphics.drawEllipse method was missing (thanks @jackrugile #1574)</li>
<li>A TweenData wouldn't take into account the <code>repeatDelay</code> property when repeating the tween, but now does. A TweenData also has a new property <code>yoyoDelay</code> which controls the delay before the yoyo will start, allowing you to set both independently (thanks @DreadKnight #1469)</li>
<li>Animation.update skips ahead frames when the system is lagging, however it failed to set the animation to the final frame in the sequence if the animation skipped ahead too far (thanks @richpixel #1628)</li>
<li>Loader.preloadSprite had an extra guard added to ensure it didn't try to updateCrop a non-existent sprite (thanks @noidexe #1636)</li>
<li>The <code>TilemapParser</code> has had its row / column calculations updated to account for margins and and spacing on all sides of the tileset (thanks @zekoff #1642)</li>
<li>Any Tile set with alpha !== 1 would cause the whole layer to render incorrectly (thanks @nkholski #1666)</li>
<li>P2 Debug Body class: The shape check in draw() needed to check for Convex last, since other shapes (like Rectangle) inherit from Convex (thanks @englercj #1674)</li>
<li>P2 Debug Body class: The updateSpriteTransform() function needed to be called from the ctor. Otherwise bodies with no sprite (so no postUpdate call) would never be moved to draw in the correct position (thanks @englercj #1674)</li>
<li>Animations are now guarded allowing Sprites with animations to be destroyed from within onUpdate, onLoop or onComplete events (thanks @pnstickne #1685 #1679)</li>
<li>Text.lineSpacing can now accept negative values without cutting the bottom of the Text object off. The value can never be less than the height of a single line of text (thanks @anthonysapp #1690)</li>
<li>Text.lineSpacing is no longer applied to the first line of Text, which prevents text from being cut off further down the Text object.</li>
<li>If you paused a Sound object that is using audio markers and then resumed it, it wouldn't correctly calculate the resume duration - causing the sound to sometimes play into the marker that followed it (thanks @AnderbergE #1669)</li>
<li>Animation.play wouldn't correctly set the play state on the Game Objects AnimationManager causing the animation to fail to start (calling AnimationManager.play did work however), now they're both consistently working.</li>
<li>Graphics.drawArc would fail to draw any subsequent arcs if you set <code>beginFill</code> on it after drawing the first arc.</li>
<li>Graphics.drawArc would only move to the center position of the first arc created and ignore any subsequent arcs.</li>
<li>Graphics.drawArc now correctly renders multiple arcs across both WebGL and Canvas. You no longer need to specifically call moveTo to move into the correct place to draw the arc.</li>
<li>Graphics.drawArc now bails out if the startAngle = the endAngle and/or the sweep is invalid <em>before</em> adjusting any points.</li>
<li>Graphics.drawArc now correctly handles the fill on the CanvasRenderer if the arc is a subsequent arc and no line style is set.</li>
<p>For changes in previous releases please see the extensive <ahref="https://github.com/photonstorm/phaser/blob/master/CHANGELOG.md">Version History</a>.</p>
<h2>Contributing</h2><p>Please read the <ahref="https://github.com/photonstorm/phaser/blob/master/CONTRIBUTING.md">Contributors Guide</a> for full details on helping with Phaser, but the main points are:</p>
<li><p>Before submitting a Pull Request run your code through <ahref="http://www.jshint.com/">JSHint</a> using our <ahref="https://github.com/photonstorm/phaser/blob/master/.jshintrc">config</a>.</p>
<p>Written something cool that shows Phaser in use? Please tell us about it in our <ahref="http://www.html5gamedevs.com/forum/14-phaser/">forum</a> or email: support@phaser.io</p>
