cloud oak
Hi everyone,
I'm working on implementing Y-sorting in C++ for rendering a 2D game map. I need some guidance regarding the structure of my Tile class and how to manage rendering different objects like the player, tiles, and monsters in the correct order.
Here’s what I have so far:
I was planning to add a bool ySortable member to the Tile class to indicate whether a tile should be Y-sorted.
In the map rendering function, I would collect all such tiles in an array, sort them by their Y coordinate, and then render them.
However, I'm running into a design issue:
If I define the array as holding Tile objects, I won't be able to include the player, monsters, or other game entities that also need to be Y-sorted.
This is making me unsure about the best class design or data structure to allow consistent Y-sorting across different object types.
Soo
What kind of class hierarchy or structure should I use so that I can Y-sort tiles, the player, and other entities together in one array? Should I go for a common base class with a virtual getY() and render() method, or is there a better design approach?
real pine
brazen spear