usually that is 3 bytes per pixel for RGB, and there are 48x48 pixel per tile. If you use a background picture for a map instead of tiles, then you need to store every single pixel independently. that are two bytes per layer of tiles to store that number (plus some overhead for storing the tileset itself, but that does not count on larger maps)

What you don't take into account is how the map is stored while in use.Ī tile on a regular map is stored as a single number for 48x48 pixel. The main drawback is that autotiles do take some effort to set up, and you don't get autoshadows (I personally prefer to do them manually anyway, but some people do find those useful).Ĭlick to expand.no, there are other drawbacks. And ofc you get all the other Tiled features like unlimited layers, offset layers, object tiles that ignore the grid if you need something in a very specific spot etc. You can have your tilesets as large as you want, and the UI is customisable enough to make use of it - you can dedicate half the screen to the map and half to the tilesets, or even have the map on one monitor and the tileset on the other. I'm personally using Tiled for this, which works really nicely. On a more serious note, one (and I guess the only) solution to using more tiles than fit in those few tilesets you can use per map is to do the mapping in an external program, export the map as an image and use that in RPGM. *Quickly shoves the 3072x4560 dungeon tileset into a closet* Click to expand.Right, that would be ridiculous, who would ever want that?

Rpg maker mv post apocalyptic tileset