Created
May 14, 2021 00:29
-
-
Save KinoAR/79ea14a75bec8f84db4931e2a1b5648e to your computer and use it in GitHub Desktop.
The fix for your collision detection problems in Flixel.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
* From The Flixel Documentation | |
* The dimensions of the game world, used by the quad tree for collisions and overlap checks. | |
* Use .set() instead of creating a new object! | |
* ------ | |
* By updating the value of this element, we can fix our collision detection once again. | |
* Best to call this in your update function. | |
*/ | |
FlxG.worldBounds.set(); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment