Skip to content
Play Online

Map editor and community maps

Open Editor in the global navigation to make a map. Library → Maps holds your standalone maps, with New Map and Import on the right. A map exports as a .steel-tide-map file and can be played in Conquest, Frontline or a multiplayer lobby, or submitted to the public community registry.

Every map is played as painted. The game does not generate new terrain, carve passages or tidy the coast when a match starts.

Creating and opening maps

Choose New Map, then a size preset or exact width and height, and the terrain to fill it with. Each side can be 16–512 tiles; rectangular maps are supported. In the library, click a card to select it, then use its three-dot menu's Edit action; double-clicking the card or pressing Enter opens it directly. The same menu offers Delete, with confirmation.

Maps save locally as you edit and when you leave. Library returns from the canvas to your maps. Export map in the document bar or Export under the panel's Settings (Share → Export on a touch screen) writes a portable copy. If storage cannot save a draft, the editor reports the failure; export a copy to keep your work.

Painting

With a mouse, the bar above the canvas shows the map's name and size, and a floating panel holds the Terrain, Props, Buildings, Units and Settings tabs; drag it by its heading to move it. A floating drawing toolbar runs along the foot, and a minimap sits at bottom-left on larger screens. Click or drag the minimap to move the camera. On a touch screen, Share and Map settings stand beside the minimap instead. The document bar provides Undo, Redo, Export map and Test scenario.

  • Terrain includes grass, sand, snow, ice, road, bridge, city, rubble, mud, marsh, lava, fords, shallow and deep water, forest, mountain and four cliff faces. Select a swatch, then paint. Terrain controls where vehicles, ships and buildings can go; see Terrain for the full table.
  • Drawing tools are the hand for panning (H), brush (B), filled rectangle (R), filled circle (O) and eraser (X). Drag rectangles between corners and circles from centre to edge; both preview before release and each makes one undo step. The chevron beside the brush selects one of three sizes. The eraser removes placed units, buildings, props, deposits, spawns or terrain overlays; paint another terrain to replace the ground itself.
  • Props include power pylons, water towers, palms, tents, hangars, bunkers and sunken freighters. A ghost previews each placement. Props obstruct movement.
  • Deposits and spawns also live in Props. A deposit marks ore for an extractor. A spawn marks a faction's opening headquarters, with its 4×3 footprint shown. The number of spawns limits how many factions the map can seat.
  • Buildings and units place starting forces for the faction selected above the palette. Add spawns first so there is a faction to choose. T cycles a unit's facing in eighth-turn steps. These forces are used in Conquest and Frontline.

Paint Bridge across water for vehicles to cross above ships. Adjacent rows, corners and junctions join into a deck; gaps and holes stay open. Its direction follows approach roads, then the span's long axis. A straight Road across water can look like a bridge, including a broken span if it stops short, but still blocks ships. Use the Bridge swatch when both kinds of traffic need passage.

The wheel zooms, and right-drag or holding Space while dragging pans; WASD or the arrow keys also move the camera. On a phone, two fingers pan and pinch to zoom, or the hand tool pans with one finger. Ctrl+Z undoes, Ctrl+Shift+Z redoes, and Ctrl+S saves immediately; use ⌘ on macOS. [ and ] change brush size.

Map settings and resizing

Settings (Map settings on a touch screen) holds the name, description, translations and dimensions. Write a line or two about the battlefield in the description; players read it beside the map. Under Translations, add names and descriptions for the game's other languages.

When active content supplies terrain appearances, the settings also let you choose an appearance for each supported terrain. Original restores the game's usual art. These choices change the appearance, not movement or building rules.

Resize map accepts the same presets, exact dimensions and fill choice as a new map. Existing tiles stay in place. Expanding fills new space; shrinking crops the right and bottom edges and removes objects outside the new bounds. Removing a spawn also removes its starting forces. Resizing can be undone.

Grid (G) shows tile boundaries. High ground (L) shades the elevation formed by cliffs. Tidy shorelines adds sand beside water and shallows beside land, and runs only when you press it.

The settings readout flags missing or obstructed spawns, unsuitable ground for props or forces, forces without a spawn, and broken cliff arrangements. It does not check connectivity: a spawn or deposit behind a mountain wall remains unreachable. Test the routes in a match.

Importing

Return to Library → Maps → Import. Choose Select file for a .steel-tide-map or map .json file, or Import Rusted Warfare map for a .tmx file. You can also drop a file onto either choice. Imported maps appear in the library; open one to edit it.

Rusted Warfare import converts terrain, resource points and supported starting forces. Custom terrain is approximated; custom artwork, unsupported layers and units, neutral forces, mission scripts, events and team settings are omitted. The conversion notes report what needs attention. Some headquarters positions may be inferred, so check spawns and starting forces before playing.

Playing it

Use Test scenario in the document bar to launch a snapshot of the current map; Stop test returns to editing. To play with your own match settings, select the saved map under My in Conquest or Frontline. In a multiplayer lobby the host selects it from My, and guests receive the map and see its thumbnail. Seats are capped to the painted spawns. Frontline lays its sectors over any map from its spawns and ore.

My reads standalone maps from the Editor library. Incomplete drafts or maps that need inactive mod definitions remain in the Editor until they can be loaded. Export map or the editor's Export makes a file that another player can import into their own library.

Publishing

The registry is the public repository steel-tide/maps: one file per map under maps/, and the game lists what is there under the maps' Community tab, the most-taken first, with the author's name in every card's popover. You can submit a new map directly from the editor without a GitHub account. The map, your author name and contact email become public in the review request when you submit; a reviewer approves it before it appears in Community maps.

  1. Give the map a name of its own and a description, and paint at least two spawns. The editor's Publish action (under Settings, or Share → Publish on a touch screen) runs the registry's own check first and says what is missing.
  2. Check the confirmation summary: the map name, description, dimensions, player slots, deposits, props and placed forces, and enter a valid contact email. Your commander name is used for author credit automatically. Each submission costs 200 merit. By pressing Submit for review, you confirm the map is your work and agree to share it under CC-BY-4.0. The game creates the review request with a map preview and your public contact email. The email is kept out of the map file. Failed requests do not spend merit, and retrying the same submission does not charge again.
  3. The editor confirms your submission and offers View submission to follow its review. Once approved and merged, the index is rebuilt and the map is under Community for everyone.

The check asks for a name that is not Untitled, a description, two spawns, a file under 512 KB, and a name no other map in the registry has. If the service cannot be reached, your draft stays saved and you can retry. A name already published or reserved by a submission requires another name for a new map. Updates to published maps still go through a maintainer or a normal GitHub pull request replacing the file: a display name does not prove ownership, and the download count carries over when the path stays the same. A map is published under CC-BY-4.0 and belongs to its author.

The whole flow is written out for coding agents too: the registry ships a tools/check.mjs that prints every error the game would, and node tools/build-index.mjs shows what the map's entry in the index will be.

Last edited