Off By One in JSON Export?

[3v1L]

Tile codes are being stored using different representations in different parts of my JSON export file. For example, if the tile map grid shows that there is tile 140 at some index, the tile metadata is stored as 139 elsewhere in the JSON object. Let me elaborate…

I have created a map and edited certain tiles in the Collision Editor to have collision rectangles. After I export to a JSON file, I find my layers and map array in jsonObject.layers[0].data, where at the tile index there is the number representing my tile. In my case it displays 140, representing the 140th tile in my sheet.

When I look at the tile information in jsonObject.tilesets[0] though, the objectgroup info for the tile in question is stored under index 139, which is one off.

I was hesitant to post this under the bug tag because I realize it might actually be a feature, or perhaps it is because it is representing the “index” of an array, but as it appears to me this structure is closer to a JS object rather than an array anyway. At any rate I thought I’d ask the opinion of the community. If it is a bug then let’s fix it!

Thanks

[3v1L]

Duplicate - I found my answer in another post. Nothing to see here!

[bjorn (Thorbjørn Lindeijer)]

Just for future reference in case people stumble upon this thread, I assume the post you found is the following one:

Array files are one number off from tile set

Hi there I’ve been playing around with the map editor as it’s easier than my regular tilemap editor plus I can print out the integer arrays. The problem is that when ever a export my map as a text file like .json the integers are always 1 off. For instance tile number 0 shows up as 1 and 1 shows up as 2 and so on. It’s weird because in the app and clicking on tile properties it tells you that tile number 0 should be labeled tile 0. Is there a way to fix it so it shows tile numbers in the ord…