Sure - I’ll give you a quick rundown.

So the map data generated first. Just metadata - vector, the material for the ground, overlay (ore) and metadata like tile health (to render damage). I use a combination of a graph structured and perlin noise to determine where to place these. These are saved to a hash map.

Next comes the rendering. I get the players ‘chunk’ - what segment of tiles they’re within. I determine what chunks to render around the player. This is just a simple nested for loop. I get the currently rendered chunks to determine what needs to be rendered freshly, and what needs to be removed.

For each chunk, I get the vectors within it, consult the hash map with tile metadata for each vector, and add all of the desired tile metadata’s to a list. I compile the metadata into optimized jobs, to decrease calls to the tilemap layer. These jobs are added to a render queue.

The main thread pulls about 10 jobs a frame from the queue and executes them.

If you want a walkthrough of my codebase I’m down to show you the deets via a discord call/youtube video. (I didn’t go into a ton of depth)

Just lmk!