Editing Maps

The map editor is where you build every location in your game — towns, dungeons, forests, deserts, and more. It's a visual map painter with an isometric perspective, similar to RPG Maker but for MMO-scale worlds.

Creating a Map#

The app opens in Maps by default. To add a map, use Create first map, the + button at the bottom of the left map browser, or right-click empty space in the map tree and choose New Root Map. Then configure the zone properties:

Editing Layers#

Editing is organized into layer tabs, so you switch what you're working on rather than flipping a global mode:

Pick the active layer from the tabs in the toolbar; each layer has its own visibility toggle.

Painting Tools#

Rectangle and Circle with a multi-tile object lay whole copies edge to edge from the shape's top-left — a 5×4 rectangle of a 2×2 rock holds four rocks — and only where a copy fits completely inside the shape and the map. One-tile objects still fill every tile. Flood Fill places one-tile objects only.

Rectangle and Circle with a Random placement pool (Objects panel → Random placement) place one random pick from the pool at a time, the same as the Pencil — never the whole pool laid out as one picture. One-tile picks scatter one per tile. A bigger pick goes down only where it fits completely inside the shape without covering another pick; a tile where nothing in the pool fits stays as it was.

Brush Options#

• Brush size — adjustable from 1 to 8 tiles
• Autotile mode — the editor automatically picks the correct edge/border tile variant so biome transitions look natural
• Elevation painting — set terrain height to create cliffs and valleys
• Shift + paint — locks autotile to the exact source tile (no neighbor auto-connect rewrite). Useful for placing water, walls, or fences that should ignore surrounding terrain.

Right-Click Tools#

Right-click is reserved for quick-capture operations on the map:

Captured selections paste with the full stack intact. The cursor shows a ghost preview of what will be stamped.

Tileset & Object Palettes#

The palette on the right shows tiles organized by biome and objects organized by category. In both panels a dropdown at the top picks the category — it lists every biome or category with its count (and, for biomes, its colour), filters by name once there are more than eight, and takes arrow keys and Enter. Everything below the dropdown is the category you picked, so the panel is tiles and objects rather than a stack of headers.

Searching the tile palette is the exception: matches can come from any biome, so results stay grouped under their biome names until you clear the search.

Both panels support marquee drag-select:

• Drag across multiple tiles to build a pattern brush that stamps the exact shape you selected, even across different tileset sheets
• Drag across multiple objects to build a multi-object brush that places all of them as a group
• Click empty space in the palette to clear the current brush/selection
• Selected cards are highlighted with a bright cyan border
• In Edit mode the same drag does something else — dragging a tile you have ticked rearranges the palette instead of building a brush. Press Done and a drag is a pattern brush again. See Organizing Your Maps

Pattern brushes show a ghost preview at the cursor so you can see the full footprint before stamping.

Placing Objects Bigger Than One Tile#

The tile you click is where the object's feet go: the bottom-center of its footprint (in isometric, its front corner). The footprint spreads up and out from there — a 3×2 barrow covers the clicked tile, one tile either side, and the row above. The ghost, the placed art, the orange selection box and the X / O passage marks all cover exactly those cells, and the game blocks exactly those cells — so if you can see a prop, you can't walk through it, and the ground beside it stays open.

Radial Context Menu (Event Mode, Touch-Friendly)#

When you're in Event Mode, long-press (touch) or right-click a tile to open a radial context menu with the event actions laid out around the cursor. It makes tablet editing practical and keeps desktop hands close to the cursor.

• On empty tiles the menu offers creation shortcuts: Core Event, Portal, NPC, Spawn, Monster, Chest, Sign, Trigger, Light, Resource.
• On an existing event, the menu switches to edit actions: Edit, Select, Rename, Copy, Delete (or a trimmed set for placed items: Edit / Select / Delete).
• Double-click an empty tile to create a default event, or an existing event to open its editor directly — no menu required. Clicking anywhere on an event's sprite counts, not just the tile under its feet.
• Picking a creation shortcut places the event and opens its editor, so you can choose the NPC, loot table or destination straight away instead of hunting for the marker you just dropped.

Spray Brush & Shift Modifiers#

Shift combines with most painting tools to change how the brush behaves:

• Shift + paint (Pencil / Rectangle / Circle) — spray mode. Tiles are placed with a feathered random pattern inside the brush footprint, perfect for scattering grass tufts, pebbles, or decals.
• Shift + Eyedropper / Right-click — capture a single tile stack (ignoring the marquee behaviour).
• Shift + stamp (after a pattern capture) — preserve the exact autotile bitmasks from the source region so water/wall/path patterns stamp verbatim instead of recalculating edges against their new neighbours.

Free-Position Object Placement#

Objects can be placed either on the tile grid or at a sub-tile pixel offset:

• Grid mode (default) — objects snap to the tile they're dropped on.
• Free mode — objects keep a per-instance offsetPxX / offsetPxY in pixels, letting you nudge a barrel a few pixels off-center or overlap two objects precisely. Toggle Free mode in the Objects palette, or hold Shift while placing to flip the current mode for that single stamp.
• Paint mode on the Pencil switches between pencil (one tile per click) and brush (continuous paint while dragging).

Built-In Terrain & Autotiles#

The tile palette ships with a full painted autotile library — grounds, water, overlays and a complete building set — so you can lay out a world before importing any art of your own. Every block is original engine art.

Where to find them: open the Tileset palette and pick a category from the dropdown at the top of the panel — Grassland (the biome-neutral set), each biome in turn — Desert, Snow, Volcanic, Swamp — and Overlays, which holds every L2 decal and fence in one place. The dropdown lists every biome with its colour and tile count, and grows a filter box once a project has more than eight of them.

Painting with them#

1. Click a tile in the palette, then paint. Autotiles connect to their own neighbours

   automatically — corners, edges and inner corners are chosen for you.

2. Walls, cliffs and trunks are wall-type tiles and sit with the rest of their biome's tiles,

   below the floors. They connect on their four sides only, which is what gives a building a clean corner.

3. Build a wall or cliff as two pieces: paint the top (a wall top or plateau) on the row you

   want the surface, and the matching face (a wall, cliff or trunk) on the row directly below. That pairing is what makes it read as height rather than a flat slab.

4. Overlays go on layer L2. Select the overlay layer before painting them, or they'll replace

   the ground you already laid instead of sitting on it.

5. Shift + paint locks the autotile shape, so a tile keeps the exact edge you picked instead of

   re-connecting to its neighbours — useful for a one-tile fence post or an isolated rock.

Gotchas#

• Walls, cliffs and trunks are not walkable. Players collide with them, which is intended — if

  you want a decorative wall players can cross, clear Walkable on that tileset.

• A biome only appears in the palette dropdown once it exists. The library installs the Desert,

  Snow, Volcanic and Swamp biomes for you; a tile filed under a biome you later delete disappears from the palette with it.

• Publish before checking in game. New tiles render in the editor immediately, but the running

  game only picks them up after a publish.

• The library installs on a new project automatically. On an existing project, re-run the seed to

  pick it up — nothing you have already painted is disturbed.

Built-In Objects#

The Objects palette ships with several hundred ready-made objects across six built-in categories — trees, rocks, plants, props, lights, buildings, furniture, and ground decals — so you can build a world before importing any art of your own:

The pixel-art categories share one visual style, so you can mix Fantasy Props, Epic Structures and Interiors freely on the same map.

• They are real game objects. Each one has its own sprite, footprint, and passage rules, so anything you place shows up in your running game after a publish — not just in the editor.
• Lit objects glow. Campfires, torches, braziers, lanterns, glowing mushrooms, and crystals come with pre-authored light emission that works with the day/night cycle.
• Passage is pre-set. Trees and boulders block movement; flowers, decals, and small props are walkable. You can still override passage per placement with the palette's quick edit modes below.
• Big pieces claim the space they cover. An Epic Structure's footprint is its real collision area, so a 4×8 castle keep blocks all 32 tiles under it. Leave room before you stamp one.
• Swap in your own art any time. These are ordinary object definitions — open one in the object editor and point it at your own media to reskin every placed copy at once.

Gotcha: on a project created before the sprite pack existed, the built-in objects appear in the editor but not in-game. Re-run the database seed (source installs: pnpm --filter @ed5-mmo-studio/db db:seed:demo-objects) and publish to install the sprites. The same run also renames the two legacy palette categories — Demo Objects becomes Painted Props, Demo Objects 2 becomes Pixel Props — leaving any object you filed under a category of your own where you put it.

Quick Property Edit Modes (Objects Palette)#

The Objects palette has special edit modes that let you fix object metadata without opening the object definition:

Multi-tile group objects show a purple ring in the palette. Left-click selects the whole group; right-click opens a drag-selector so you can pick specific cells of the multi-tile footprint as your brush.

Passage mode only takes 1×1 objects. For a multi-cell object or a sheet group, open it in the object editor instead: the Passage Grid there shows the whole footprint, each click cycles that one cell, and Save writes every member.

What the three passage states mean#

O means "you can stand on this." It brings its own footing, so an O cell laid over impassable terrain makes that tile walkable — that is exactly how you build a bridge across a river or a staircase up a cliff: paint the water or rock as usual, then place the planks or steps on the object layer above it.

☆ means "the ground decides." A star never decides passage; it defers to whatever is underneath, so lily pads and overhanging branches stay pretty without turning a lake into a walkway. Every new object starts as ☆, and so does everything the RPG Tools importer creates (its painted Path layer is the collision there). Pick O only when the object really carries footing.

A tree that should stop you needs X on its trunk cells and ☆ on the leaves. Marking a whole tree ☆ makes it fully walk-through by design.

☆ does not draw the object above the player. That is the separate Draw-on-top flag — the palette's Above mode, or the checkbox in the object editor. The tileset importer sets both when you pick ☆ there; the object editor and the palette cycle set passage only. A canopy you walk under wants ☆ and Draw-on-top; a rug wants ☆ alone.

One exception keeps imported worlds honest: where a map tile is authored as blocked on all four sides, that verdict wins over an object's O, so a single stray O can never open a cliff face in a bulk import.

Show passability#

Turn on Show passability in the map toolbar to see what the game will do, tile by tile, with terrain and objects combined the way the server combines them:

Gotchas:

• The view is the server's rule, not the raw symbols. To see what one object is authored as, open it in the object editor.
• Blockers that are not authored on the map — harvest nodes, chests, live props — are not shown.
• A multi-tile group (purple ring in the palette — a tree cut from a sheet cell by cell) blocks as one object: every tile's own X counts. Before October 2026 only its top-left tile did, so a group's trunk often let players through. Tiles you stamped one by one with the drag-selector still count only for themselves.
• Objects made before September 2026 on a hand-built project kept their O. If a decoration opens ground it should not, cycle it to ☆; the passability view shows exactly where.
• A red X with nothing drawn on it is damage an older version of the editor saved. Use Repair — see Repair damaged objects below.
• Hosted and managed worlds pick up changed passage after a publish.

Repair damaged objects#

Two faults in older versions of the editor saved tiles that block with nothing drawn on them:

• Objects that lost their picture. Painting at the left or top edge of a map with Infinite on made the map grow, and every object on it stopped drawing.
• Leftover pieces. Erasing a large object with a small eraser, dragging while you placed one, or dropping one half off the edge of the map took its picture and kept some of its tiles.

When you open a map that holds either one — or tick Impassable in the eye menu — a notice appears at the top of the map, for example 30 objects can be restored, 6 leftover tiles can be removed, with a Repair button.

1. Open the map. If the notice does not show, open the eye menu and tick Impassable.
2. Read the counts, then click Repair.
3. Look the map over. Ctrl+Z undoes the whole repair in one step.
4. Save the map, then Publish. Until you do, the game is unchanged.

Gotchas:

• Repair never runs by itself. × hides the notice until you tick Impassable again.
• It is not offered while the map is view-only.
• If your map grew in steps that were not a multiple of 64 tiles, the restored objects were missing from the game too — after you publish they appear there again.
• A restored object is an ordinary object: move or erase it as usual.
• On a streaming map, open the parent to check the whole world. With a child map open by itself, Repair leaves alone any object that reaches in from the map beside it.

Objects on streaming maps#

A streaming map is a parent map with child maps joined to it. Open the parent and you edit all of them as one map; open a child and you edit that map by itself. An object you place either way shows in both, and in the game.

Worlds saved by an older editor. Objects placed in the joined view on any map but the top-left one were saved in a way the game could not place: they showed in the editor, but in the game many were not drawn and did not block. The editor finds them when you open the parent map:

1. Open the parent map. A message says how many it read again, for example 12 objects on this map were saved by an older editor in a way the game could not place, and the map shows as unsaved.
2. Look the map over. Objects you placed with a child map open by itself now show in the joined view too.
3. Save the map, then Publish. Until you do, the game is unchanged.

Gotchas:

• This is not a repair and deletes nothing. Ctrl+Z puts the objects back the way they were stored.
• It waits for the object list to load and is skipped while the map is view-only.
• An object the editor cannot read either way is left as it is. If it is damage, the Repair notice offers to fix it. The AI Copilot can run the same repair: ask it to repair the objects on this map — it shows the plan (what moves, what is removed) first, and Undo puts the whole map back.
• Running your own exported server? A server older than 0.6.5 reads these objects the other way round. Re-export it before you save a streaming map with this editor. Hosted games need nothing.
• An object erased on a child map opened by itself no longer comes back when you open the parent.
• Ground belongs to the map that holds it. Maps are stored in 64×64-tile blocks, so a map whose width or height is not a multiple of 64 stores a strip past its own edge. A child map to the left of or above the parent used to lay that strip over the parent's ground in the joined view — blank where the child had nothing — and saving then kept the parent half empty. The joined view and the game now take every tile only from the map it belongs to. If an older editor already saved a blank parent, open the parent map by itself to check its ground; repaint it there if it is gone. The game server needs this update too (hosted games have it); an older server can still show an old copy of a neighbour's ground along a map edge.

Shadow Groups#

A prop stamped tile-by-tile from a marquee is not one object — every tile is its own placement — so each tile casts its own shadow. On a 4x4 tree that is sixteen overlapping shadows, and it looks wrong.

You fix it once, on the prop, not once per placement. In the Objects palette, click the property-mode button until it reads Shadow group, then drag across the parts that belong to the same prop. They become one shadow group, and every stamp of that prop from then on casts a single shadow.

Two identical trees standing side by side still cast two shadows: each part remembers its slot inside the prop, so the engine can tell one planted tree from the next even when they touch.

You don't have to group the base. A shadow starts where the prop meets the ground, so a group reaches down on its own: from its lowest row it takes in the tiles directly below that belong to the same prop and aren't already grouped.

• Group just the canopy of a 1x2 tree → it takes in the trunk → one shadow, from the trunk
• Group three of four rows of a 2x4 tree → it takes in the last row → one shadow, from the base
• Art that genuinely floats — a hanging sign with nothing beneath it — has nothing to take in. Set that part's Shadow mode to None in the object editor instead; muting any part of a group mutes the whole prop

A group casts one soft contact shadow across its whole footprint rather than a projected silhouette, because a group's art is spread over several separate tiles and there is no single silhouette to stretch.

Grouping affects shadows only — never walkability, passage or draw order.

Copy, Paste, and the Pattern Brush#

• Right-drag on the map creates a marquee that copies the complete tile stack — both floor sublayers plus all four object sublayers — into a Pattern Brush. The cursor shows the pattern's ghost so you can see what will stamp.
• Shift + Right-click captures a single-tile stack the same way.
• Multi-tile objects stamp back whole. A 2×2 rock inside the marquee stamps as one 2×2 rock that blocks its own 2×2, not four overlapping rocks. An object that only partly sits inside the marquee is left out of the pattern, as Copy leaves it out — widen the marquee to take all of it. (Before October 2026 every captured tile of an object stamped a whole copy, which blocked well past what you saw.)
• Ctrl+C / Ctrl+X / Ctrl+V copy, cut and paste the active selection — a tile region, a single event, or a group of events (see below).
• Click empty space in the tileset/object palette to clear the current pattern and return to the default brush.

Selection, Clipboard and Layer Locks#

Copy, cut and paste an area#

1. Pick the Select tool (S) in Map mode and drag a box over the area.
2. Press Ctrl+C to copy it, or Ctrl+X to cut it (the area is cleared as one undo step).
3. Press Ctrl+V. A ghost of the copied area follows your cursor, centred on it — blue for floor, amber for objects, purple for events and placed items.
4. Click to place it. Shift+click places it and keeps the ghost so you can stamp it again. Esc, a right-click or the banner's Cancel button put it away.

Ctrl+D (duplicate) picks up a copy of the selection as a ghost without touching your clipboard. Delete clears everything in the box on every unlocked layer.

The clipboard survives switching maps and reloading the editor, so you can copy a house on one map and paste it on another in the same project.

While the ghost is showing, Shift+H / Shift+V flip it and Shift+R rotates it; the Stamps button saves an area to reuse later. See Stamps, Flip & Rotate, Gameplay Overlays.

Every paste, cut, delete and group move is one undo step.

Select several events or placed items#

In Event mode with the Select tool:

Lock a layer#

Lock a layer you've finished so a stray stroke can't touch it: click the lock button next to the layer tabs (it locks the active layer), or the lock icon beside each layer in the Layer visibility (eye) menu. A locked tab shows a small lock.

Gotchas

• Locks are yours and per map: they're kept in this browser, never saved into the map, and collaborators don't see them.
• The paste ghost and group selection are mouse and pen gestures; on a touch screen use the Events panel's checkboxes for bulk edits.
• No feature flag — these are editor tools and change nothing in the game itself.

Undo / Redo#

Undo/redo is backed by a background web worker that stores XOR-compressed diffs of each stroke, so even huge fill operations can be reversed cheaply.

• Ctrl+Z undoes, Ctrl+Y (or Ctrl+Shift+Z) redoes.
• The history keeps up to 80 strokes. Each continuous drag counts as a single stroke, so dragging a long path uses only one slot.
• Redo is cleared as soon as you make a new edit, as expected.

View Mode, Parallax, and Day/Night Preview#

• View mode toggle — switch between Isometric and Top-down rendering of the same map data. Useful for quickly laying out a town's footprint top-down before polishing it isometrically.
• Parallax background — attach a parallax image to the zone that scrolls behind the map as the player moves; configure its scroll speed per axis.
• Day/Night preview — preview the zone at any time-of-day without waiting for the in-game clock. Toggle the preview and drag the time slider to check how lighting, shadows, and ambient tint affect your art.
• Spawn points — every map can carry any number of cyan SPAWN markers. Right-click a tile and choose Set Starting Location to make it the primary marker (labelled SPAWN) and this map the world's starting map: new characters land there. Choose Add Spawn Point to add another marker (SPAWN 2, SPAWN 3, …), and right-click a marker to Remove Spawn Point. Markers move the moment you set them. To reposition one, switch to Event mode with the Select tool and drag it to a new tile — exactly like moving an event. If an event sits on a marker's tile, the click picks the event; drag the marker from a tile that has none, or use the right-click menu. Saves happen in the background and an error toast puts the markers back if one fails.
• Where a player respawns — after a death the player comes back at the nearest spawn point on the map they died in. A map with no spawn points sends them to the nearest spawn point on any neighbouring map on the overworld board (they change maps), and if no map has one, to the world's starting location. Dungeon instances and arenas keep their own rules (checkpoints, entrance, team spawns). A Location with Acts as a spawn point on (Database → Locations) counts as a spawn point at every marker where it is placed, so a wayshrine or a camp can be somewhere to come back to without a SPAWN marker of its own.

Renderers & Performance#

The zone editor draws the map with the GPU renderer by default — a PixiJS 8 / WebGL renderer that bakes blended-terrain chunks, keeps only what's near your viewport resident, and stays smooth on large worlds and on phones and tablets. Editor gizmos (selection, building tools, markers) draw on a crisp overlay above it.

The GPU renderer now draws everything the editor shows, including the two things it used to hand back to the CPU:

Both renderers show the same picture. The GPU renderer is the reference; the compatibility renderer is kept deliberately as the fallback and is not going away.

Switching renderers#

If your device's WebGL is slow or broken, switch to the compatibility renderer (Canvas2D) with the GPU renderer toggle under Settings → Editor (open Settings from the database menu) — it's a per-user preference stored in your browser, and flipping it live-swaps the renderer with no reload. If the GPU renderer can't start at all, the editor falls back to the compatibility renderer automatically and tells you.

Neither URL parameter changes your saved setting; close the tab and your preference is back.

The autotile debug compass#

Press Shift+D over the map to inspect why an autotile picked the sprite it did. Each floor tile gets a dark wash, four dots, and a number:

Press Shift+D again to turn it off. It's a debug view, not part of your map — it never saves and players never see it.

Zoom, fit and the status bar#

Safety nets while you edit#

Gotchas

• Drafts live in this browser only — they don't follow you to another computer. Drafts older than 14 days, or for a map that has since been resized, are not offered.
• Undoing Set Starting Location restores this map's markers but does not switch the world's starting map back — set it again on the other map.
• A multi-tile object only partly inside your selection, or one that would land past the map edge, is skipped; the paste message names what was left out.
• In the desktop app, when the game server stops, the toolbar says Server stopped followed by the reason, with a Restart button.

Very large imported libraries (for example 30k+ RPG Maker MZ decorations) use row virtualization in the object panel to keep scrolling and panel-switching responsive.