HaxeFlixel / HaxeFlixel/flixel
FlxG.overlap doesn't handle FlxBasics that are not FlxObjects or FlxGroups
Open
Nobody has claimed this yet.
Bug
Collisions
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
Error : Null Object Reference
Called from flixel.system.FlxQuadTree::add flixel/system/FlxQuadTree.hx line 429
It should ignore these objects
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at flixel/system/FlxQuadTree.hx line 429, where the Null Object Reference occurs during FlxG.overlap. Trace how FlxBasics that are neither FlxObjects nor FlxGroups reach this point. Done means those objects are ignored without an error during overlap handling.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100