Select a generation strategy:

Generate a SINGLE random map with Layer Elements Object LoaderLayerElementsObjectLoader
Generate a SINGLE random map with Layer Elements Composite LoaderLayerElementsCompositeLoader
Generate MULTIPLE random maps with Multiple LoaderMultipleByLoaderGenerator
Generate MULTIPLE random maps with Layer Elements Composite Loader (with associations)MultipleWithAssociationsByLoaderGenerator

Common Configuration Options?These options apply to all generator types.

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

?Size of the main path in tilesMain Path Size

?Width of the paths connecting elements in tilesPath Size

?When enabled, creates a non-walkable border around the mapBlock Map Border

?Whether the map border tiles can be walked onIs Border Walkable

?Tile index used for the map borderBorder Tile

?Default number of free tiles to leave around each elementFree Space Tiles Quantity

?Minimum free space tiles to always leave around elementsMinimum Elements Free Space Around

?Multiplies the free space quantity by the element size factorFree Space Multiplier

?Multiplier applied to the total number of free tiles on the mapFree Tiles Multiplier

?Percentage of ground tiles to replace with random variationsVariable Tiles Percentage

?Layer names that define collision areas used for path-findingCollision Layers For Paths (comma separated)

?Minimum tiles distance from the map borders where elements can be placedMinimum Distance From Borders

?Whether to generate path connections between elementsGenerate Elements Path

?Whether paths can be placed over element free space areasAllow Place Path Over Elements Free Area

?Default value for whether paths can cross element free spaceDefault Elements Allow Paths In Free Space

?Whether to prefer placing elements near the map bordersPlace Elements Closer To Borders

?Order in which elements are placed on the mapPlace Elements Order

?How to resolve an element placement rejection: move already placed elements to make space, or auto-grow the mapElements place rejection resolve method

?Whether to sort elements by size before placing themOrder Elements By Size

?Whether to randomize the quantity of each element placedRandomize Quantities

?Whether to sort element positions relative to the map centerSort Positions Relative To Map Center

?Background color for the map in hex formatMap Background Color

?Whether to put path borders in separate layers from the path itselfSplit Borders In Layers

?Whether to add decorative border tiles around pathsApply Surrounding Path Tiles

?Whether to add inner wall decorations to pathsApply Paths Inner Walls

?Key used to identify inner walls tiles in the tilesetPaths Inner Walls Tiles Key

?Whether to add outer wall decorations to pathsApply Paths Outer Walls

?Key used to identify outer walls tiles in the tilesetPaths Outer Walls Tiles Key

?Whether to remove path border tiles that overlap with elementsClean Path Border Tiles From Elements

?String to append to the name of border layers when splitSplit Borders Layer Suffix

?Whether to remove the ground layer from the final mapRemove Ground Layer

?Whether to convert path tiles to ground tiles after generationApply Ground As Path Tile Post Process

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

?Origin point for the entry positionEntry Position From

?Width of the entry point in tilesEntry Position Size

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

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

?Whether to write out cropped element files for debuggingWrite Cropped Elements Files

?Whether to remove temporary optimized map files after generationRemove Temp Files After Generation

?Whether to automatically extrude map edgesAutomatically Extrude Maps

?Generate a debug file showing the path finding gridDebug Paths Grid

?Includes the spots used in the map as terrain sets in the map tileset, so every spot can be painted as a terrain when the map is edited in the tiled map editor appInclude Spots As Terrains

NOTE: if you already uploaded all your files and never manually removed them from the "generate-data" folder, you don't need to upload them again.

Images

JSON Files

Generator data:

Generating maps, please wait...

Layer Elements Object Loader - Configuration

?Size of each tile in pixelsTile Size

?Path to the tileset image fileTile Sheet Path

?Name of the tileset image fileTile Sheet Name

?Height of the tileset image in pixelsImage Height

?Width of the tileset image in pixelsImage Width

?Total number of tiles in the tilesetTile Count

?Number of columns in the tilesetColumns

?Margin in pixels of the tileset imageMargin

?Spacing between tiles in pixelsSpacing

?Tile index to use for the groundGround Tile

?Tile index to use for paths between elementsPath Tile

?Tile indexes to use for random ground variationsRandom Ground Tiles (JSON array)

?Number of each element type to place on the mapElements Quantity (JSON)

?Amount of free space to leave around specific elementsElements Free Space Around (JSON)

?Whether paths can cross through the free space around specific elementsElements Allow Paths In Free Space (JSON)

?Elements to place at the center of the map with priority valuesMap Centered Elements (JSON)

?Tile IDs to use for path borders in different positionsSurrounding Tiles (JSON)

?Tile IDs to use for corner tilesCorners (JSON)

?Define the element JSON files to use for each element typeLayer Elements Files (JSON)

?Tile IDs to use for each border directionBorders Tiles (JSON)

?Tile IDs to use for border cornersBorder Corners Tiles (JSON)

?Define special areas with different ground tilesGround Spots (JSON)

?Define fixed width and height for the mapMap Size (JSON)

Layer Elements Composite Loader - Configuration

?JSON file containing all map elements definitionsComposite Elements File

Multiple Loader - Configuration

?Names of the maps to generateMap Names (comma separated)

?JSON file containing all map elements definitionsComposite Elements File

Layer Elements Composite Loader with Associations - Configuration

?JSON file containing all map elements definitionsComposite Elements File

?Information about each map to generate (mapName and mapTitle)Maps Information (JSON)

?Properties for sub-map generation when using associationsAssociations Properties (JSON)

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

?Origin point for the entry positionEntry Position From

?Width of the entry point in tilesEntry Position Size

LayerElementsObjectLoader

Generates a single random map using individual element JSON files. Each element (house, tree, etc.) is defined in its own JSON file specifying the tile layers and their contents.

Best for: projects where each element type has its own separate tile definitions file.

Generator Data example:
map-data.json

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

Expected Images:
tilesheet.png

All JSON files in the examples use the same tileset image. In theory it works with individual images per element but this still needs testing - use the composite option for multiple tileset images.

LayerElementsCompositeLoader

Generates a single random map using a composite JSON file that bundles all element definitions and multiple tileset images together. The generator merges tilesets automatically using the Tile Map Optimizer.

Best for: projects using the Reldens tileset analyzer output, or when all elements share a single optimized tileset.

Generator Data example:
map-composite-data.json

Expected JSON files:
reldens-town-composite.json

Expected Images:
outside.png
terrain.png
house.png

Single tile map JSON with multiple tilesets and images. Original contents are 16x16 - set "factor: 2" to run the optimizer and get 32x32 tiles.

MultipleByLoaderGenerator

Generates multiple independent random maps from a single composite file. Each map is generated separately using the same element definitions but different random layouts.

Best for: generating a set of unique maps (e.g., multiple town maps) in a single operation.

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

Expected JSON files:
reldens-town-composite.json

Same composite structure as SINGLE but with multiple map names - uses a different loader to create all maps at once.

MultipleWithAssociationsByLoaderGenerator

Generates multiple maps with defined associations between them - for example, a town map and its connected house interiors. Sub-maps (interiors) are generated with their own configuration and linked to entries in the main map.

Best for: Reldens game worlds where players can enter buildings or transition between connected areas.

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

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

Multiple maps with association options - uses a different loader to create all associated maps at once.

Confirm

Are you sure? This will replace all your current generator data.

Maps Wizard

Select a generation strategy:

Common Configuration Options?These options apply to all generator types.

Layer Elements Object Loader - Configuration

Layer Elements Composite Loader - Configuration

Multiple Loader - Configuration

Layer Elements Composite Loader with Associations - Configuration

LayerElementsObjectLoader

LayerElementsCompositeLoader

MultipleByLoaderGenerator

MultipleWithAssociationsByLoaderGenerator

Confirm