Game Map Chunks

[Shawn]

I assume X & Y for the positions, then Z for the 'type' of tile?

I'm thinking of using a similar method for my next project.

That's just it though. There is already a value stored at X,Y in the array. That value would be the tile type. So, set value at 1,1 to tile value 3 (or whatever). If tile value = 3, create grass

Unless I'm just totally misunderstanding the Z index, you would only need that if you want to store multiple values for a particular index. Like if you're creating more than one thing at 0,0. Otherwise you'd have to use separate arrays for different object placements.

[Konidias]

Well if all you want to store is the tile type, then yes it's fine to just use x,y... but I typically use z because it allows me to store more data at that x,y position... such as information for the tile. Say for the rock tile you want to be able to hit it with a hammer, and each time you hit it, a value goes up and the rock is damaged. So if you had that stored at x,y,1 then you could load that value in and display the proper damaged version of the rock and keep track of its damage.

I was just thinking ahead, but yeah you're right, if all you are storing is different tiles at the x,y position, then you can save yourself some array space and just use x,y.

[Panchos]

Very helpful example thanks

[Shawn]

You are correct Konidias. When I was working with this sort of thing I was making simplistic maps. If you think you may be adding more advanced features it's probably safer to use the Z index just in case. Then you won't have to redo everything later.

[rocketappliances]

Konidias I can't seem to access your example can you make another like or send it over to me somehow. This thing sounds like something I need bad for my game

[stuartmaughan]

Heya Konidias, would it be possible to re-upload this? I am very interested as to how this would work but cannot seem to access it :c
Cheers!