HaxeFlixel / HaxeFlixel/flixel
Consider replacing HaxeFlixel’s built-in collision/physics system with a Phaser Arcade–based alternative for better performance and compatibility
Open
Nobody has claimed this yet.
Collisions
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
The built-in collision and physics system in HaxeFlixel has some issues and its performance is not very good. The simple physics system adapted by jeremyfa from Phaser’s Arcade Physics should be more performant and offer better compatibility. Is it possible to replace HaxeFlixel’s built-in 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 by reviewing HaxeFlixel’s built-in collision and physics system, then compare it with the linked jeremyfa/arcade project. Determine the replacement scope, performance and compatibility criteria, and how existing behavior would be validated before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100