Reldens - Tile Map Generator

Since this is the same Tile Map Generator used for Reldens, you can check the official documentation on how each of the options below works.

What would you like to do?

Generate a SINGLE random map using single elements JSON files (LayerElementsObjectLoader)

In the examples above, all the tileset JSON files use the same tileset image (this is because we used the already optimized version of the tileset).
Case disclaimer: In theory, it should also work if each element has its own image, but this still needs to be tested.
For now, you can use the composite option to use multiple tileset images, and those will be merged by the generator that uses the Tile Map Optimizer.

Generator Data example:
map-data.json

Expected JSON files examples:
house-001.json
house-002.json
tree.json

Expected Images files examples:
tilesheet.png

Configuration Options

Tile Size: ?Size of each tile in pixels

Tile Sheet Path: ?Path to the tileset image file

Tile Sheet Name: ?Name of the tileset image file

Image Height: ?Height of the tileset image in pixels

Image Width: ?Width of the tileset image in pixels

Tile Count: ?Total number of tiles in the tileset

Columns: ?Number of columns in the tileset

Margin: ?Margin in pixels of the tileset image

Spacing: ?Spacing between tiles in pixels

Ground Tile: ?Tile index to use for the ground

Path Tile: ?Tile index to use for paths between elements

Random Ground Tiles (comma separated): ?Tile indexes to use for random ground variations

Elements Quantity (JSON): ?Number of each element type to place on the map {"house1": 3, "house2": 2, "tree": 6}

Elements Free Space Around (JSON): ?Amount of free space to leave around specific elements {}

Elements Allow Paths In Free Space (JSON): ?Whether paths can cross through the free space around specific elements {}

Map Centered Elements (JSON): ?Elements to place at the center of the map with priority values {}

Surrounding Tiles (JSON): ?Tile IDs to use for path borders in different positions {"-1,-1": 127, "-1,0": 124, "-1,1": 130, "0,-1": 126, "0,1": 129, "1,-1": 132, "1,0": 131, "1,1": 133}

Corners (JSON): ?Tile IDs to use for corner tiles {"-1,-1": 285, "-1,1": 284, "1,-1": 283, "1,1": 282}

Layer Elements Files (JSON): ?Define the element JSON files to use for each element type {"house1": "house-001.json", "house2": "house-002.json", "tree": "tree.json"}

Borders Tiles (JSON): ?Tile IDs to use for each border direction (top, right, bottom, left) {"top": 0, "right": 0, "bottom": 0, "left": 0}

Border Corners Tiles (JSON): ?Tile IDs to use for border corners {"top-left": 0, "top-right": 0, "bottom-left": 0, "bottom-right": 0}

Ground Spots (JSON): ?Define special areas with different ground tiles {}

Map Size (JSON): ?Define fixed width and height for the map {"mapWidth": 0, "mapHeight": 0}
Generate a SINGLE random map using a single JSON file that will contain all the elements with the information set on the map file properties (LayerElementsCompositeLoader)

In this case, as you can see, we have a single tile map JSON file which contains several tilesets with different images.
All the original contents are 16x16 pixels, so you can see we set "factor: 2" in the sample params to run the optimizer and get tiles of 32x32 pixels in the result.

Generator Data example:
map-composite-data.json

Expected JSON files examples:
reldens-town-composite.json

Expected Images files examples:
outside.png
terrain.png
house.png
doors.png
water.png
inside.png

Configuration Options

Composite Elements File: ?JSON file containing all map elements definitions
Generate MULTIPLE random maps using a JSON file for the options and another for the elements (MultipleByLoaderGenerator)

In this case we have the same structure as in the SINGLE import, but we include multiple map names in the provided data and use a different loader to create multiple maps at once.

Generator Data example:
map-composite-data-with-names.json

Expected JSON files examples:
reldens-town-composite.json

Expected Images files examples:
outside.png
terrain.png
house.png
doors.png
water.png
inside.png

Configuration Options

Map Names (comma separated): ?Names of the maps to generate

Composite Elements File: ?JSON file containing all map elements definitions
Generate MULTIPLE random maps with a JSON file for the options and another for the elements and with sub-maps (MultipleWithAssociationsByLoaderGenerator)

In this case we have the same structure as in the SINGLE import, but we include multiple maps information and the association options in the provided data, but use a different loader to create multiple associated maps at once.

Generator Data example:
map-composite-data-with-associations.json

Expected JSON files examples:
reldens-town-composite-with-associations.json
house-composite.json

Expected Images files examples:
outside.png
terrain.png
house.png
doors.png
water.png
inside.png

Configuration Options

Composite Elements File: ?JSON file containing all map elements definitions

Maps Information (JSON): ?Information about maps to generate [{"mapName": "town-001", "mapTitle": "Town 1"}, {"mapName": "town-002", "mapTitle": "Town 2"}, {"mapName": "town-003", "mapTitle": "Town 3"}, {"mapName": "town-004", "mapTitle": "Town 4"}]

Associations Properties (JSON): ?Properties for map associations {"generateElementsPath": false, "blockMapBorder": true, "freeSpaceTilesQuantity": 0, "variableTilesPercentage": 0, "placeElementsOrder": "inOrder", "orderElementsBySize": false, "randomizeQuantities": true, "applySurroundingPathTiles": false, "automaticallyExtrudeMaps": true}

Entry Position: ?Position for map entries (e.g., "top-middle")

Entry Position From: ?Origin point for entry position

Entry Position Size: ?Width of entry point in tiles

Common Configuration Options

Factor: ?Multiplier used to scale the map and elements (2 means elements will be 2x larger)

Main Path Size: ?Size of the main path in tiles

Path Size: ?Width of the paths connecting elements in tiles

Block Map Border: ?When enabled, creates a non-walkable border around the map

Is Border Walkable: ?When enabled, the border tiles can be walked on

Border Tile: ?Tile index to use for map borders (if not specified in bordersTiles)

Free Space Tiles Quantity: ?Number of empty tiles to leave around elements

Min Free Space Around Elements: ?Minimum free space to leave around all elements

Free Space Multiplier: ?Multiplier for the free space around elements

Free Tiles Multiplier: ?Multiplier for the free tiles between elements

Variable Tiles Percentage: ?Percentage of ground tiles that will be replaced with random variations

Collision Layers For Paths: ?Layer names to check for collisions when generating paths

Min Distance From Borders: ?Minimum distance in tiles that elements must be from map borders

Generate Elements Path: ?Whether to generate paths connecting all elements on the map

Allow Path Over Elements Free Area: ?Whether paths can be placed in the free space around elements

Default Allow Paths In Free Space: ?Default setting for whether elements allow paths in their free space

Place Elements Closer To Borders: ?Elements will be placed closer to map borders when enabled

Place Elements Order: ?How to place elements - randomly or in a specific order

Order Elements By Size: ?Whether to place larger elements first

Randomize Quantities: ?Whether to randomize the order of element placement

Sort Positions Relative To Map Center: ?Whether to sort element positions by distance from map center

Map Background Color: ?Background color for the map in hex format (e.g., #000000)

Split Borders In Layers: ?Whether to put path borders in separate layers from the path itself

Apply Surrounding Path Tiles: ?Whether to add decorative border tiles around paths

Apply Paths Inner Walls: ?Whether to add inner wall decorations to paths

Paths Inner Walls Tiles Key: ?Key used to identify inner walls tiles in the tileset

Apply Paths Outer Walls: ?Whether to add outer wall decorations to paths

Paths Outer Walls Tiles Key: ?Key used to identify outer walls tiles in the tileset

Clean Path Border Tiles From Elements: ?Whether to remove path border tiles that would overlap with elements

Split Borders Layer Suffix: ?String to append to the name of border layers (when split)

Remove Ground Layer: ?Whether to remove the ground layer from the final map

Apply Ground As Path Tile Post Process: ?Whether to convert path tiles to ground tiles after generation

Entry Position: ?Position for map entries (e.g., "top-middle", "down-left")

Entry Position From: ?Origin point for the entry position

Entry Position Size: ?Width of the entry point in tiles

Auto Merge Layers By Keys: ?Layer keys to automatically merge (comma separated)

Map Compression Level: ?Compression level for the generated map file (0-9)

Write Cropped Elements Files: ?Whether to write out cropped element files for debugging

Remove Temp Files After Generation: ?Whether to remove temporary optimized map files

Automatically Extrude Maps: ?Whether to automatically extrude map edges

Debug Paths Grid: ?Generate a debug file showing the path finding grid

IMPORTANT: All uploaded files are deleted from the server every hour.

Note: Because of this hourly cleanup, you can submit the form again within the same hour without re‑uploading your files.
If you want to use the sample generator data, you still need to download the example files for each case and attach them in the form below.
After the hour resets, you'll need to upload the files again.

Images

JSON Files

Generator data: