HaxeFlixel / HaxeFlixel/flixel
Collision bug with stacked sprites
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
HaxeFlixel has a quite weird collision checks. (The main problem in function separate I think).
And it has to be fixed.
Here's a demonstration of a horrible bug with collision:
https://github.com/RedSQ/flixel-collision-issue.
Blocks are starting falling under each other. The code has nothing special.
Ideas for improvements:
Make a different collision types for collison objects, like a: FIXED, ACTIVE, LITE, PASSIVE.
It would be very comfortable to work with.
LITE entities only collide with ACTIVE or FIXED entities. FIXED entities will collide with LITE, PASSIVE and ACTIVE entities.
So, it would give a more flexible collision system.
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 with the reproduction project at https://github.com/RedSQ/flixel-collision-issue and inspect the collision separate function. Confirm the stacked-sprite failure, then determine a defined collision behavior and verify that the blocks no longer fall through each other.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100