The "objects" approach
Last updated
Last updated
For this, the simple part is the name conventions, since you need to create a new Tiled-Map per element on the map the naming is almost the same in every file. The tool later will pick up each of these to generate the random map and merge the required data from each element.
As you can see in the screenshot above, each element for the map is a different file and the conventions are the described ones.
Also, you can note the "path" layer consist in a single tile below the house door. That tile will be use to join the current element with the main path on the generated map.
All these assets are available as well in the examples folder (in the packages and GitHub):
https://github.com/damian-pastorini/tile-map-generator/tree/master/examples/layer-elements-object
The next step is to generate the script, which is the most "complex" part for this approach.
The problem here is that we need to define everything manually on the script:
You need to require each map file.
Then specify every element quantity.
Then define every single tile index for every randomize part: pathTile, groundTile, randomGroundTiles, surroundingTiles and corners.
In the examples, the groundTile will be the grass, the pathTile will be the full floor tile, the surroundingTiles are the ones used to wrap the path, and the corners are for the crossing paths.
One IMPORTANT note here is: you need to +1 to the tile index display in the Tiled app, in the following screenshot the correct tile index for the marked tile is not 282 but 283, this is because how the layers are later build
Here's the example script for the map randomizer:
By running this script with:
You will get as many map variations you want.
