mingli1/questmark

LibGDX 2D RPG

questmark's Issues

Collision "stickiness" with naive movement system

Patch collision detection for the naive movement system special case.

Player cannot move orthogonal to the colliding entity.

Improve collision detection

Allow sliding between two collision boxes if pinned

Entity superclass and JSON Manager

Need data transfer from json files into generic Ashley entities' components.

• Create an abstract superclass that extends off Ashley's Entity class that holds abstract methods for data transferring.
• Create a json manager class that parses .json files and outputs the data into Entity classes.

The builder pattern would probably be extremely useful here 🤔

Implement quadtree for collision detection

Our current implementation of collision detection is O(n * m) time where n = #entity bounding boxes and m = #RectangleMapObject bounding boxes. To improve this, we could store RectangleMapObject bounding boxes in a quadtree grid for O(log m) lookup to compare to entity bounding boxes. Doing so would improve runtime to O(n log m).

Add GLProfiler

Figure out how to implement GLProfiler to debug render calls and reduce OpenGL texture bindings.

Migrate to Kotlin

Convert most or all of the current Java code to Kotlin and maybe use Kotlin LibKTX in place of standard Java LibGDX.

Movement system improvements

• Re-implement the movement systems for entities to use target positions instead of frequencies,
• Store initial positions for an enemy so it returns to that location if the player outruns the enemy.
• Pathfinding for returning to source location should use A* search
• Currently the entity continues with its path when stopped by another entity, but have to account for collision with walls causing entities to become stuck in its movement pattern

Fix QuadTree

QuadTree seems to retrieve incorrect bounding boxes at times...