XMAP WORKSHOP

User guide

XCOM Map Workshop is a map editor for XCOM: Enemy Within. It opens one of the game's maps in your browser, lets you rearrange it, and builds the result into a new map the game plays like its own.

Preview release 0.6.0 · for Long War Rebalance and plain Enemy Within

What it does

The editor runs only on your computer. It reads your own game install and contains nothing from the game; nothing goes into the game until you play or install a map.

Getting started

What you need

Everything else comes with the editor. It needs no internet connection and no Unreal tools.

Installing and starting

  1. Run XCOM-Map-Workshop-<version>-Setup.exe. The installer isn't signed yet: if Windows says "Windows protected your PC", choose More info, then Run anyway.
  2. Follow its pages. The one that matters is Your XCOM: Enemy Within game: the game folder, the one that holds XEW, usually ...\steamapps\common\XCom-Enemy-Unknown. Setup fills it in when it finds the game in Steam, and says whether it is Long War Rebalance or plain Enemy Within.
  3. Start XCOM Map Workshop from the Start menu or the desktop shortcut. A small console window opens, then the editor in your browser at http://127.0.0.1:8768/.
  4. Keep the console window open while you work. Closing it stops the editor.

From the zip instead: unpack it anywhere and run XCOM Map Workshop.cmd. The first start asks for the game folder in the browser.

The first time you open a map, the editor reads it from the game, which takes about half a minute. After that it opens at once.

Where to go from here: make your first variant, the first of the typical tasks below, takes a few minutes. The sections after the tasks explain every control, part by part: the window, pieces, the map, and projects, building and playing.

Typical tasks

The quickest way in: each task is a few steps, with a link to the section that explains the rest.

Make your first variant, start to finish

  1. Press M and open a map. Urban Bar is a good first one: builds of it have been played.
  2. Choose a floor number in the bottom bar's Floors to look inside a building.
  3. Click a piece, press G, and drag an arrow to move it.
  4. Press Ctrl+S and give the project a name.
  5. Press Ctrl+B, leave Bake the lighting off, and choose Build. It takes a few seconds.
  6. Close XCOM if it is running, and choose Play in game in the build window (or later Play in the header, then Play last build).
  7. If XCOM's launcher opens, pick Enemy Within. The battle on your map starts by itself, with a test squad.
  8. When you are done, close XCOM: the editor then takes your map back out of the game by itself. Game maps… (the arrow beside Play), Undo everything does it at once, if you ever need to.

Add cover to an open area

  1. Find a piece that gives the cover you want and select it: a dumpster, a planter, a car.
  2. Ctrl+C, then Ctrl+V. The copy follows the cursor.
  3. Press R to turn it, then click where it should stand. Shift+click places several.
  4. Check the tile grid: the filled tiles are the ones the piece occupies. Blue tiles mean it floats.

If the map has no such piece standing where you can click it, use Add (P) and pick it from the list. Keep new cover off the squad's landing area: the game may drop a soldier on it.

Rearrange a room

  1. Cut down to the room's floor with Floors.
  2. Set Snap to 96 to keep pieces on whole tiles, or 24 for finer steps.
  3. Move pieces with G and turn them with R. For an exact place, type the position or the yaw in the piece panel.
  4. To line several up, select them, pick the one to line up with last, and use Align.
  5. Delete what is in the way with Del.

Open or close a route

  • Open a wall: select the wall section and delete it. Pictures and shelves hanging on it stay unless you delete them too.
  • Add a door: copy an existing door. Its leaf and frame come together, and it lands on whole tiles in quarter turns. A door needs an opening: delete the wall section where it goes, or copy a wall section that already has a doorway.
  • Add a way up: copy a ladder to where its foot and its top both meet floor. The Build warns of a ladder that isn't expected to climb, and builds it all the same.
  • Block a route: copy a wall section, a van or a fence into the gap.

After a change like this, a quick build and a look in the game is the way to know how the game paths around it.

Work on an upper floor

  1. Choose the floor's number in Floors. The floors above are cut away.
  2. To extend the floor itself, open Add, choose Kind: Floors, and pick a floor piece.
  3. With Level snap on, the piece goes to the height of the floor chosen in Floors, however high the cursor is. Click to place it.
  4. Put props on it as on any floor.

A copied storey floor can be walked on only where a soldier has room to stand: not under a duct or a low ceiling.

Make one cover piece out of two

  1. Place the pieces together: two crates stacked, two consoles side by side.
  2. Select both and press Ctrl+G to group them.
  3. Tick Break together in the game in the piece panel.
  4. Copy the group wherever you need it: each copy is a group of its own with the same option.

Change the lighting

  1. Press Shift+L for the Lights view, and click a marker.
  2. Move it like a piece, or change its colour, brightness and radius in the light panel or with the white handles.
  3. Press O to see that light alone. Press it again to go back.
  4. For a new light, press P, choose Kind: Lights, and place a Point Light or a Spot Light.
  5. Build with Bake the lighting ticked. Light edits show properly only in a baked build.

Set a fire, or quiet a sound

  1. Press P, choose All maps, and Kind: Effects: Fire. Point at an entry to see it burn.
  2. Click one, then click where it should burn: a wrecked car, a doorway.
  3. Drag the handle beside its marker to make it larger or smaller.
  4. For a sound that doesn't belong, press Shift+X, click its speaker, and press Play in its panel to be sure. Then delete it, or drag its spheres in to make it reach less far.

A quick build makes them. More: Effects and sounds.

Add cover where there is nothing to copy

  1. Press P, choose Kind: Invisible, and pick Cover block.
  2. Click the tile it starts on, then set its Width, Length, Height and Cover in the piece panel.
  3. If it stands over something that can be destroyed (a car, a crate), select the block and that piece, press Ctrl+G, and tick Break together in the game. The block then goes with the piece and leaves no invisible wall.

More: Cover blocks and invisible floors.

Take a building from one map to another

  1. Open the map that has the building (M).
  2. Hover the Normal view button and tick Lights and Floor boxes, so its lamps and its building are taken too.
  3. Press T and draw a box round the building. Check the white outlines, then choose Select.
  4. Choose Save as prefab… in the piece panel and give it a name. The window says what goes in.
  5. Open your own map or project. Press P, choose Prefabs, and click the prefab.
  6. Turn it with R and click where it should stand. It arrives as one group, with its floor boxes.
  7. Build with Bake the lighting ticked, so it is lit for where it stands.

For a single piece, a lamp post or a wall, use the piece list's All maps instead. More: Prefabs, Pieces from other maps.

Build a house of your own

  1. Rest the pointer on Add in the tool strip and choose Room with a roof.
  2. Press on the ground at one corner of the house, drag to the opposite corner, and let go. You get four walls with a doorway in the side nearest you, a roof, and the building that lets the game open it up.
  3. Click the room. In the panel's Room section, Choose… a look for its walls and one for its roof.
  4. For windows, Ungroup the room, click a wall, choose Add gap, and drag the gap's middle handle up.
  5. Put a door in the doorway from the piece list (P), and furniture inside.
  6. Choose floor 1 in the bottom bar's Floors: the roof should go.

More: Walls, rooms, floors, roofs and ground you draw.

Raise the ground, or add a rock

  1. Rest the pointer on Add and choose Block. Drag out its rectangle, then drag the handle on its top to set its height.
  2. For a way up, choose Ramp and drag from the low end toward the block. Its panel says whether its slope still gives cover.
  3. For cover, choose Rock and drag a rectangle. Click a blue point and drag its arrows to shape the rock; Another rock tries a different one.
  4. Give each a look with Choose… in its panel.

More: Ground: patch, block, ramp and rock.

Make a house you put together open up in the game

  1. Select the house's walls, floors and roof (Box select is the quick way).
  2. Press Shift+B for the Buildings view, and choose Boxes around the pieces selected. A box is made for each floor.
  3. Click each box and check it in the panel: the same Building for all, Floor 1 for the ground floor, 2 for the next.
  4. Drag a box's top so the roof, or the next storey's floor, starts above it, and start each storey's box at a yellow line.
  5. Leave the view (Shift+B) and choose floor 1 in the bottom bar's Floors: the roof should go and the walls drop.

More: Buildings.

Move where the squad lands

  1. Press Shift+Z for the Landing zones view, and click the zone.
  2. Drag its arrows to move it by whole tiles. [ and ] turn it a quarter turn.
  3. Read the panel: it says when a soldier tile is outside the grid, over no floor, or has a piece on it.
  4. For a second landing, press Ctrl+D and move the copy. Under Used by, say which game lands there.
  5. Save, then choose Land here to play the build with the squad landing at that zone.

More: Landing zones.

Move where the aliens start

  1. Press Shift+U for the Spawns view, and click a pod (an orange ring) or a Meld point (a green dot).
  2. Drag its arrows to move it by whole tiles and levels.
  3. Read the panel: what uses the point, and what the game does with it on your install.
  4. For one more, press Ctrl+D and drag the copy, or choose Spawn points in the Add panel (P) and click a tile.
  5. To keep aliens off an area, place a No-spawn volume from the same list and drag its white handles to size it.
  6. Save and play. Under Long War Rebalance the pods and the Meld go where its rules put them when it finds room; your places play on plain Enemy Within and where it doesn't.

More: Spawn points.

Make the map larger

  1. Choose Map grid in the tool strip. The play area shows with a handle on its far sides and its top.
  2. Drag the red or the blue handle outwards by whole tiles, or the green one up by whole levels.
  3. Leave Lay the map's ground over the new area ticked where it is offered. Elsewhere, lay floor pieces over the new area yourself (P, Kind: Floors).
  4. Choose Done, then fill the new area with pieces and prefabs.

More: Map grid.

Make a new map on an old map's light and landing

  1. Open the map, click Map in the header and choose Clear map….
  2. Click Clear map. The ground grid shows the empty ground.
  3. Turn on Map grid on the left rail and drag the play area's handles to the size you want, in tiles and levels.
  4. Lay floors first (P, Kind: Floors, or the Build menu's ground and floors, drawn to size), at least under the landing zones' soldier tiles, then walls, cover and prefabs.
  5. The clear leaves one landing zone. Click it to move or turn it with its gizmo, and copy it for more. Lay floor under its six tiles.
  6. On plain Enemy Within, place pods and Meld points on your floors: the Add panel's Spawn points. Long War Rebalance places its own. Move or delete the map's no-spawn volumes in the Spawns view (Shift+U) where they no longer fit your map.
  7. Save, then pick a zone and click Land here to try it in the game.

Try it in the game, then finish it

  1. While the layout is changing, build with Bake the lighting off. Each build takes seconds, and cover, pathing and line of sight are already right.
  2. Close XCOM, choose Play in the header, then Build and play.
  3. Pick Enemy Within if XCOM's launcher asks. The game goes straight into a battle on your map: the Skyranger lands and the test squad steps out. There is no campaign to start, and no save to load: a tactical save from before a change ignores the new pieces' cover, so always play it this way.
  4. When the layout is right, build once more with Bake the lighting on, and play that.
  5. The map leaves the game when XCOM closes. Game maps… (the arrow beside Play), Undo everything takes out everything the editor ever put in: the game's config files end exactly as they were.

What the test battle is, and what it changes in the game: Play.

Pass your maps on as a map pack

  1. Give each map a picture if you like: Map, Map picture…, then Take from the view.
  2. Open Manage projects… from the Project menu and tick the projects.
  3. Choose Build there if any needs a full build, and wait for the queue.
  4. For each ticked project choose Additional or Replace.
  5. Under Pack, leave New pack and type the pack's name (and yours under By).
  6. Choose Export map pack. The zip is in the builds folder's Map packs: send that.

Players of Long War Rebalance 3 copy the pack's folder into their game; anyone else runs its Install.cmd. More: Map packs.

Share a project or a build

  • A project is one file: <editor folder>\projects\<name>.json. Send it. To open one sent to you, put it in that folder and choose Open… in the Project menu. It opens on the same version of the map only; on another it says so. A project saved in a newer version of the editor needs that version or a later one.
  • Several maps at once: the project manager's Export map pack zips their builds as a pack, with scripts that install them, and with Include editor project files ticked, their projects too.
  • A build is its folder in <editor folder>\builds\ (zip it to send it). Its README.txt says what each file is and lists the config lines the game needs.
  • Installing a build by hand: copy its CookedPCConsole files into the game's XEW\XComGame\CookedPCConsole, and add the config lines from its README. As built, the variant is out of the mission rotation; putting it in is your choice.

Undo a mistake

  • Ctrl+Z undoes the last step, Ctrl+Y redoes it.
  • Reset piece sends the selected pieces home. Reset all does it for the whole map, as one step you can undo.
  • Close project shows the untouched map; your saved project is still there to open.
  • If a save went wrong, the revision before it is kept beside the project, in the projects folder's .workshop folder.

The window

What is on the screen: the header and its menus, the tool strip, the view, and the windows that choose what you see.

The 3D view fills the window. Everything else floats over it, and most of it appears only when it is needed: the piece panel with a selection, the undo buttons once something has changed.

The editor's window with the Bar open, its ground floor cut open, and a pool table selected
The Bar with a project open, cut down to its ground floor, a pool table selected with the Move tool. Click a picture to enlarge it.
  1. Header: the project and the map with their menus, and on the right what has changed, undo, Build, Play, Settings and the view's menus. More
  2. Tool strip: select, move, rotate, add and draw, the views (buildings, lights, landing zones, effects, spawn points), and how pieces snap. More
  3. The view: the map. The coloured arrows on the selected piece are the Move tool's handles. More
  4. Piece panel: what is selected, with Copy, Delete and its exact position. More
  5. Bottom bar: frame the view, play area or everything, and which floor to cut down to. More
  6. Tile readout: how many tiles the selected piece covers, and its level. More
The left of the header: Project and Map
  1. Project shows the open project's name (a dot after it means unsaved changes) and opens the Project menu: save, open, close, the recent projects and the project manager.
  2. Map shows the base map and opens the Map menu: change the map (M), its missions, its picture, its grid, and Clear map.

On a map that serves more than one mission, a Mission picker shows to the right of Map. It chooses which mission's extra objects are shown (see what a mission adds) and which mission Play plays. With a project open it lists the project's missions, the kinds the project adds marked (added).

The right of the header: the edit count, Undo, Redo, Reset all, Build, Play with its arrow, Settings, Import notes, View options and help
  1. What has changed: how many pieces are moved, added and deleted, how many lights, buildings, and effects or sounds are edited, a resized grid and changed landing zones, and whether that is saved: "not saved" with no project, then "unsaved" or "saved".
  2. Undo (Ctrl+Z).
  3. Redo (Ctrl+Y).
  4. Reset all puts the whole map back to the original: added pieces go, deleted ones return, moved ones go home, groups end, your buildings go and the map's own are restored, effects and sounds go back as the map has them, and the grid, the landing zones and a clear are undone. It is one undo step, so Undo brings your edits back.
  5. Build (Ctrl+B) makes the project's variant. It is greyed until the edits are saved as a project. More
  6. Play starts XCOM in a battle on the project's build, or with no project open, on the original map. More
  7. The arrow joined to Play opens the Game menu: the test squad, the game's map records, and the installs the editor works with.
  8. Settings (the gear): the game install the editor reads and its checks, and the cache. More
  9. Import notes: what the editor couldn't read exactly from the map (a material drawn in an approximate colour, say), with their count. They are about the picture, not about your edits.
  10. View options: lighting, light markers, tile grid and more. More
  11. Controls and shortcuts: a short list of every key, the editor's version, and a link to this guide.

Items 3 to 6 show once something has changed. While the project manager's build queue runs, a chip beside the count follows it (Building 2 of 5, Queue stopped, 5 built, 1 failed); a click on it opens the manager.

MenuOpened byWhat it holds
ProjectThe Project buttonSave, Save as…, Open…, Close project, the recent projects, and Manage projects….
MapThe Map buttonChange map…, Missions…, Map picture…, Map grid, and Clear map….
GameThe arrow joined to PlayTest squad setup…, Game maps…, and the Installs.
SettingsThe gearGame install and checks…, and Cache everything….

The Map menu

The Map menu, its five items numbered
  1. Change map… (M) opens the map browser.
  2. Missions… chooses the missions the project is for. More
  3. Map picture… sets the picture the game shows for the map on its mission screens. More
  4. Map grid shows the play area's handles, as the tool strip's button does. More
  5. Clear map… takes every piece off the map. More

Items 2 to 5 are the map's own. In the prefab builder, where there is only the map to change, the button opens the map browser at once.

Tool strip

The tool strip, its eighteen buttons numbered
  1. Select (V): click pieces without any handles in the way.
  2. Move (G): arrows on the selection. Drag an arrow to move along it, or a small square between two arrows to slide across a plane.
  3. Rotate (R): rings on the selection. Drag a ring to turn about its axis.
  4. Box select (T): draw a box around many pieces to select them all at once. More
  5. Add (P) opens the piece list, to place more of any piece the map has, a piece of another map, or a new light. Hover it for the Build menu: walls, rooms, floors, roofs and ground drawn by dragging.
  6. Normal view (Shift+N): pieces are selected. It is one of six views, with the next five; one is on at a time. Hover it for its four switches, Lights, Floor boxes, Effects and sounds, and Spawn points and objectives.
  7. Buildings view (Shift+B), where a building's floor boxes are drawn and fitted. While it is on, only boxes can be selected. More
  8. Lights view (Shift+L) shows the map's lights as markers you can select and edit. While it is on, only lights can be selected. More
  9. Landing zones view (Shift+Z): only landing zones are selected, drawn over everything. More
  10. Effects view (Shift+X): the map's effects, sounds and lens flares as markers drawn over everything. While it is on, only they are selected. More
  11. Spawns view (Shift+U): the map's spawn points and the mission's objectives as markers drawn over everything: where the aliens' pods start, the Meld, the drop-in points. While it is on, only they are selected. More
  12. Map grid: the play area's handles, to make the map's tile grid larger. More
  13. Axes (X): the handles follow the world's axes, or the piece's own (useful for a piece that stands at an angle).
  14. Pivot (C): where the handles sit, and what the selection turns about. At first, the piece's own origin, usually one of its corners, so a turned piece swings round that corner. Lit, the middle of the selection, so a piece turns in place. With snap at 96, the middle keeps to the nearest tile centre or corner, so pieces on the tiles stay on them (a piece one tile by two still moves half a tile when turned). A typed turn in the piece panel turns about the same point.
  15. Snap cycles through three settings; the button's corner shows which. Off; 24, steps of 24 units and 15°; 96, whole tiles (96 across, 64 up) and quarter turns, counted from where the piece stood. The corner shows R when the selection is a piece that only moves on the grid.
  16. Level snap (L, on at first): floor pieces keep to whole levels when placed and when moved up or down. More
  17. Linked pieces (on at first): moving a piece also moves what was placed with it. Turn it off to move one piece of a set. A car's parts, a van's, and a door with its frame always move together.
  18. Frame the selection (F, or double-click a piece): the camera goes to it.

A lit button with an outline is on. Hover any button for a reminder of what it does.

The views, and the Normal view's switches

The Normal view button with its flyout: Lights, Floor boxes, Effects and sounds, and Spawn points and objectives

Buttons 6 to 11 choose what a click selects: pieces in the Normal view, only floor boxes in the Buildings view, only lights in the Lights view, only landing zones in the Landing zones view, only effects, sounds and lens flares in the Effects view, only spawn points and objectives in the Spawns view. Pressing the view that is on, or Shift+N, goes back to the normal view.

Hover the Normal view button for four switches. They let the normal view show and select more than pieces, so a house can be handled with its lamps, its building and its smoke in one go:

  • Lights: the lights are drawn and can be clicked, moved, copied and deleted with pieces. A light's colour, radius and cones are still set in the Lights view.
  • Floor boxes: your buildings' boxes are drawn, and a building is selected whole, by a click on a box's edge.
  • Effects and sounds: their markers are drawn, and they are clicked, moved, copied, deleted and grouped with pieces. Their values are still set in the Effects view.
  • Spawn points and objectives: the Spawns view's markers are drawn too. A click on one picks it ahead of the piece behind it, to move and edit as in that view.

All four are off whenever a map opens.

The view and the camera

ToDo this
OrbitDrag with the left button. With Keys move along the view ticked, the drag looks round instead: the camera stays where it is and only turns and tilts
PanDrag with the right button, or hold W A S D or the arrow keys (Shift moves faster)
Move along the viewTick Keys move along the view in View options: then W and S (Up and Down) move forward and back the way the camera faces, climbing or descending with its tilt, and A and D (Left and Right) sideways
TurnHold Q or E to turn the view left or right (Shift: faster). The camera circles the point it looks at, or with Keys move along the view, turns where it stands
Change the camera's speedThe three sliders under Camera in View options: moving, turning with the keys, and turning with a drag
ZoomScroll
Go to a pieceDouble-click it, or select it and press F
See the whole map againFrame in the bottom bar
SelectClick a piece. Ctrl or Shift+click adds one to the selection, or takes it out
Clear the selectionEsc

Bottom bar and floors

The bottom bar: Frame, Scene and Floors
  1. Frame fits the whole view in the window: the play area in Interior, everything in Full.
  2. Scene: Interior shows the area the game plays on; Full adds the backdrop around it (distant buildings, the street beyond the edge). Interior draws a piece that reaches into the area whole, a car across the edge included, unless it stretches more than four tiles past it.
  3. Floors: All shows buildings whole, roofs closed. A number cuts every building down to that floor, so you can see and edit inside. It is also the Floor picker: with a floor chosen, a floor piece you place goes to that floor's height.
The Bar with all floors: its roof closed
Floors: All
The Bar cut down to floor 1: its ground floor open
Floors: 1

Each part of the bar shows only on maps where it applies: a map with no buildings has no Floors.

View options

The View options menu, its sixteen items numbered
  1. Lighting: Neutral is plain, even light, best for editing. Map uses the map's own lights, as edited; No area is the same without the glow of lit surfaces. Both are approximations of the game's lighting.
  2. Brightness of the view.
  3. Keys move along the view: W A S D and the arrow keys move the camera forward, back and sideways the way it faces, instead of panning across the map, and dragging looks round from where the camera stands instead of orbiting. More
  4. Move speed: how fast W A S D and the arrow keys move the camera, from a fifth of the usual speed to three times it (Shift still triples it).
  5. Key turn speed: how fast Q and E turn the camera.
  6. Drag turn speed: how fast a drag orbits, or looks round with Keys move along the view. The three speeds are kept on this computer; double-click a slider to put it back to ×1.
  7. Area lights: also show the lights that stand for glowing surfaces. View only.
  8. Outline the pieces a light reaches: for the selected light, in teal the pieces it is baked into, in orange the ones it reaches after your change.
  9. Sun, moon and sky: lists the lights that have no place. View only.
  10. Play area (B): faint amber walls round the area the game plays on, its level volume: units can't leave it.
  11. Tile grid around the selection.
  12. Floor tiles: where the game has floor, coloured by the piece that carries each tile. Hover a tile to name its piece; click to select it.
  13. Effects as they look: each effect drawn where it stands, moving. Untick it for a busy map on a slow computer; the markers and the editing stay. More
  14. Wireframe.
  15. Hide patch helpers: untick to see Long War Rebalance's invisible cover and blockers, as a wireframe. Shown only on maps that have them.
  16. Performance stats: a line of counts (pieces, triangles, draw calls).

Above Play area, on a whole map: Ground grid and Landing zones (more).

Map browser

Change map… in the header's Map menu (or M) lists every map your install plays, in sections by mission type. A map that serves several types is listed under each.

The map browser, with its search, mission chips and list of maps
  1. Search by the map's name, its package or a mission.
  2. Prepared only hides maps the editor hasn't read yet.
  3. Mission types: click one to show only its section.
  4. A map: its name, its package (the file's name in the game), and the missions it serves.
  5. Its state: Checked in game (the editor's work on this map has been checked in the game), Ready (already read: opens at once) or First open ≈ 30 s (the editor reads it from the game when you open it).
  6. How many maps match, and how many are ready.
  7. Open (or double-click a map, or Enter).

Pieces

Selecting pieces, changing them, adding more, drawing your own, and saving sets of them as prefabs.

Piece panel

The panel on the right appears when something is selected.

The piece panel for a copied claw machine, its parts numbered
  1. What it is: the piece's name, its kind and its map, then chips with what you should know about it (listed below).
  2. The buttons, each named when the pointer rests on it: Copy (Ctrl+C; Ctrl+V then shows the copy at the cursor and a click places it), Delete (Del), Select all of a kind with its count, and Reset piece, which puts the selected pieces back where the map has them. At the right, Save as prefab… saves what is selected as a prefab.
  3. Flags: what the game does with the piece (walking, cover, sight, floor, the mouse), to change. Folded, its line says whether they are as the map has them.
  4. Place: its position in game units. Type a value and press Enter.
  5. Its rotation in degrees: pitch, yaw (the turn about the vertical) and roll.
  6. Source unfolds the piece's records: its actor and mesh, whether it can be destroyed and its health, which building floor it belongs to, and what moves with it.
  7. Copy full paths copies the actor, mesh and material paths, for a bug report or for your own notes.

The chips

ChipWhat it means
Moves with 2 other piecesLinked pieces: they were placed together and move together (a car's body and glass).
Added copyA piece you added. Source names the piece it copies.
Recipe snapIt moves only by whole tiles and quarter turns. Why
Group of 2It is in a group.
Glows · 3 lightsA glowing piece: its glow lights the map, and moves, copies and goes with it.
Carries an effectA particle effect stands on it, such as a Skyranger's lights or a claw machine's, or the effects a prefab of the map placed round it (an alien vapour pod's smoke). The editor and the Build move, copy and delete them with the piece. A click on the chip opens the Effects view on them.
Mission loot · Not lootA collectible such as a UFO power core. A copy breaks like the original, but the game doesn't count it as loot.
Mission scriptThe map's mission script uses this piece. Moved or deleted, the script still acts on the original, not on the copy: the Build warns.
Landing zoneOne of the pieces Long War spawns the dropship's landing from. Moved or deleted, the landing breaks: the Build warns. A copy is an ordinary piece.
A package's nameThe piece comes from a mission or from Long War Rebalance's patch, not from the map. It can be looked at, not edited.
FlagsOne of its flags is off, or you changed one.

Flags

The Flags section says what the game does with the piece, and lets you change it: a wall that units walk and see through, a sign the mouse never picks, a fence that gives no cover. It is folded until you click its name; its line says as the map has them, or how many you changed.

The Flags group for the Bar's six dumpsters, Blocks sight turned off for all of them
  1. The Flags chip: one of the piece's flags is off, or changed by you.
  2. Select all of a kind picked every dumpster of the map: six.
  3. The five flags, each with its state for the pieces picked (here 6 pieces). A flag marked ⓘ has something that limits it: point at it and the line under the rows says what.
  4. A flag you changed has a dot after its state: Blocks sight turned off for all six, so units see over them.
  5. Reset flags puts the map's back.
FlagWhen it is on
Blocks walkingUnits can't walk through the piece: the game's pathing counts it. A piece lower than 60 over the bottom of its level (a hedge, a kerb) stops no one even so: the row and the Build say so.
Gives coverA unit beside it can take cover behind it.
Blocks sightUnits can't see through it.
FloorUnits can stand on it. Off, the game finds no floor on it: they walk under or through it.
Mouse picks itThe cursor stops on it, as on a roof. Off, it looks through to what is behind: handy for a canopy or a sign over a street.

Select all of a kind

The Select all button, beside Copy and Delete (four squares and a count; its tooltip names the kind, as in Select all TV_BarRow), selects every piece drawn with the same mesh as the picked one, so you can change all of a kind at once, their flags for one. Shift+click adds them to the selection. With a box drawn, it takes only those whose middle is inside the box. Hidden and deleted pieces, a mission's or Long War Rebalance's pieces, cover blocks, lights and floor boxes are left out. Selecting changes nothing in the project and is not an undo step. A picked effect or sound has a Select all of its own: Effects and sounds.

Box select

To select many pieces at once, a whole house for one, draw a box around them.

A select box drawn over part of the Bar's car park, the pieces inside it outlined in white
A select box: the pieces outlined in white are the ones it would take.
  1. Box select in the tool strip (T) arms the tool: the cursor becomes a cross. Press on the ground at one corner of what you want, and drag to the opposite corner.
  2. The box. It starts a little under the ground you drew on and reaches up to the top of the map's grid. The pieces it would take are outlined in white, and follow as you change it.
  3. A white dot on each of its six sides: drag one to stretch that side. Pull the top down to take one storey only.
  4. The dot in the middle: drag it to move the box over the ground.
  5. The bar says how many pieces are inside. Select (Enter) makes them the selection. Add to selection (Shift+Enter) keeps what was selected as well. Draw again starts a new box, and Cancel (Esc) puts it away.

Groups and Align

With two or more pieces selected, the piece panel gains two sections.

The group section of the piece panel, for a group of two kegs
  1. The group. Group (Ctrl+G) joins the selected pieces. A group selects and moves as one: picking any of its pieces picks them all. It shows in gold.
  2. Ungroup (Ctrl+Shift+G) ends the group: its pieces are separate again. To move one piece of a group on its own, ungroup, move it, and group them again.
  3. Break together in the game: when one of the group's breakable pieces is damaged or destroyed, the others are too. Use it for a cover piece made of two, so it can't be left half standing. A cover block in the group goes when one of those pieces is destroyed. Grouping is the editor's alone; this option is what reaches the game.

Add to group shows beside Group when one whole group and pieces (or lights, or buildings) that are in no group are selected. It puts them into that group, which keeps its options, where Group would make a new group round them all. It is one undo step.

Groups inside groups

A group can hold other groups. Group a table and its chairs, group a counter and its stools, then group the two as a room: each stays a group of its own inside the room.

Lights and buildings in a group

A group can also hold lights and buildings (yours or the map's), so a house keeps its lamps and its floor boxes when it is moved or copied.

The Align section of the piece panel
  1. Target: the piece or group the others line up with. It is the last one you picked unless you choose another here. A white box marks it in the view.
  2. Axes and edge: tick any of X, Y (across the floor) and Z (up), choose what lines up (centres, low edges or high edges), then Align. The others move; nothing turns. It is one undo step.
  3. What will happen, in words: shown by the section's ⓘ.

Add: the piece list

Add (P, or a click on its button) opens Add a piece. Under This map it lists one entry for each distinct piece the map has placed. It lists the original map, so a piece you deleted still has its entry. All maps lists the pieces of the game's other maps, and Prefabs the sets of pieces you have saved. The list holds the game's pieces; walls, floors and ground of your own size come from the Build menu, which shows when the pointer rests on the Add button.

The piece list open beside the tool strip
  1. Filter by name, kind or material.
  2. Kind uses the same categories in This map, All maps and the prefab builder. Floors finds flat pieces that carry saved floor tiles. Lights has point and spot lights. Invisible has cover blocks and invisible floors. Spawn points has a new pod and a new Meld point (on a map with them) and a new no-spawn volume.
  3. Where: the play area or the backdrop, on maps that have a backdrop.
  4. Sort: A to Z, largest first, or most used.
  5. An entry: its picture, name, kind, and size in game units (width × depth × height); on the right, how many the map has. An entry is everything a copy would take along: a van is one entry of several parts.
  6. How many pieces and lights the list holds.
  7. Close (or P again).
  8. All maps: pieces from the game's other maps.

To place one: click an entry. A see-through preview follows the cursor. R turns it a quarter turn (Shift+R the other way). Click in the view to place it; Shift+click places it and keeps going. Esc stops. The new piece is selected, ready to move or turn.

A new pod, Meld point or no-spawn volume: choose it under Kind: Spawn points, then click the tile it is to stand on. The Spawns view comes on. A new point is a copy of the map's first plain pod or first Meld point, with its values, on that tile, as high above its floor as the original stands above its own; this works after a clear too, which deletes the map's own. A new no-spawn volume is the size of the map's first one (3 by 3 tiles and four levels high on a map with none), over whole tiles round the click, its bottom on the level of the floor there. Esc stops.

Pieces from other maps

All maps lists the pieces of every map in the game install, so a lamp post from the Police Station or a wall from an alien ship can stand in the map you are editing. The first time, the editor reads the game's maps (Read the game's maps: about half a minute, once; nothing in the game is changed). After that each piece is read from the game the first time you use it; Cache everything…, under Settings, reads them all at once instead.

The piece list showing the pieces of all maps
  1. All maps, beside This map. The editor remembers which one you used last.
  2. Filter by name, kind, material or the name of a map.
  3. Kind, map and sort: the middle menu keeps only the pieces placed in one map. Sort A to Z, largest first, most used, in most maps, or recently used.
  4. Can be placed keeps the pieces the Build can bring into another map today: scenery, props that break, walls and floors that break, doors, cars, vans, ladders, collectibles and bodies. A car, a van or a door with its frame is one entry and is placed as one; a van brings the room inside its box. Untick it to see the rest, greyed, each saying why not: mostly helpers that are hidden in their own maps. Not in this map leaves out what this map has itself. Favourites shows only the starred pieces.
  5. An entry: its picture, name, kind, size, and the map it comes from (or in how many maps it stands). Here marks a piece this map has too.
  6. The star makes it a favourite. Favourites and recently used pieces are kept with your settings, for every map and project.
  7. How many pieces match.

Placing one works as from This map: click it, then click in the view. The piece panel shows the map it is from. A piece that keeps to the tiles (a wall, a door) snaps to this map's tiles as it stood on its own map's. A ladder needs floor at its foot and at its top, as a copy of one of the map's own does; put it on an outer wall with nothing standing at its foot. The Build copies the piece into your map with the meshes, materials and textures it needs, so the built map grows a little (the entry's tooltip says by how much at most).

Lighting. Built with Bake the lighting, a piece from another map is lit for where it stands, and the pieces around it take its shadow. Built without, it keeps the light it had in its home map, so it can look too dark or too bright where you put it.

Effects, sounds and lens flares of the other maps are listed here too, under their own kinds in the Kind menu: Effects from other maps.

Walls, rooms, floors, roofs and ground you draw

The game's pieces come in the sizes its maps happen to have. The Build menu makes pieces to your own size: a wall of any length, a room, a storey floor, a roof, and ground. Each is drawn by dragging over the tiles, sized afterwards by its handles, and given the look of any of the game's walls, floors or ground.

The Add button with its Build menu: Wall, Room, Room with a roof, Floor, Roof, and under Ground: Patch, Block, Ramp and Rock
  1. Rest the pointer on the Add button. The menu shows after a moment. (A click on Add opens the piece list instead.)
  2. Pick a tool. Its button stays lit while it draws, and a hint at the top of the view says what to do.
  3. Press on the ground at one corner, drag to the other, let go. A wall is dragged from one end to the other along a tile line.
  4. The tool stops after one piece. Hold Shift to keep drawing; Esc stops.
ToolWhat it draws
WallOne wall along a tile line, two storeys tall at first.
RoomFour joined walls round the rectangle you drag, with a doorway in the side nearest you.
Room with a roofThe same with a roof on its walls and a building round it, so the roof is cut away when the cursor is inside.
FloorA storey floor, a storey over the floor you press on. Units walk on it.
RoofA roof on the tops of the made walls round it, or two storeys over the ground where there are none.
PatchFlat ground level with the ground it lies on: it covers holes and paints the ground.
BlockRaised ground. Units walk on it.
RampA slope rising toward where the drag ends.
RockA rock in the rectangle: it stands in the way and gives cover by its height.

A wall

A drawn wall in the Bar's inside wall look, with a window and a doorway, picked with its handles and its Wall section; beside it a plain room with a roof
A drawn wall given a look and two gaps, picked. The grey box beside it is a room with a roof as it is drawn: plain.
  1. Add: rest the pointer on it for the Build menu.
  2. An end's white handle lengthens or shortens the wall by whole tiles. Its gaps stay where they are, and one the wall no longer holds goes.
  3. The top's handle adds or takes storeys, as far as it is dragged.
  4. A gap's blue handles: its middle moves it along the wall and up or down, and its sides, top and bottom size it.
  5. A room with a roof, drawn in one drag and still plain.
  6. Look: Choose… opens the look picker; Plain goes back to no look.
  7. The gaps, one line each: its size, a warning mark where it plays oddly (point at it to read why), and × to remove it.
  8. Add gap cuts a gap shaped as the game's doorways in the free tile nearest the middle. Flip sides swaps the wall's two faces. Reshuffle gives it another break pattern: it looks the same until it breaks.
  9. Break and Repair: the wall built already damaged. More

A room

A room is four walls drawn in one drag, joined at their corners, with one doorway. It arrives as one locked group: a click on any of it picks the room, and it moves, turns and copies whole.

Floors and roofs

Ground: patch, block, ramp and rock

A block, a ramp and a rock drawn on the Bar's car park, all plain; the rock is picked, with blue points on its corners, its white handles and its Ground section
A block, a ramp up to it, and a rock, the rock picked.
  1. A block: raised ground, walked on.
  2. A ramp: it rises toward where its drag ended. Its panel gives its slope in degrees and what that means in play.
  3. The picked rock, with a blue point on each of its corners.
  4. A white handle: those on the sides size the shape by whole tiles, the one on top raises or lowers it (a patch has none on top).
  5. Look: any of the game's ground and rock materials. In the look picker each card shows this shape made in it.
  6. Another rock gives a different rock in the same footprint and height; Reset points puts its corners back. A ramp has Turn here: a quarter turn on its footprint.

Looks: the look picker

A look is the appearance of one of the game's own walls, floors, roofs or ground materials. A made piece given a look is made again in it where it stands; the Build brings what the look needs from its home map.

The look picker listing wall looks: a find box, filters, and cards each with a picture of a wall made in that look
The look picker, opened from a wall's Choose….
  1. Find a look by its name, its setting or a map.
  2. Setting: only the looks of one setting (a bar's interior, a UFO's walls).
  3. Favourites only, and beside it Full only, which hides the looks tagged Simpler.
  4. Pick from the view (I): then click a piece in the view to take its look. To its left, the size of the pictures.
  5. A card: a sample made in the look (a wall three tiles long, a floor three by three, or the ground shape being changed), its name, its setting and the map it comes from. Click it to choose it.
  6. The star keeps a favourite: starred looks come first.

Damage: Break and Repair

A piece can be built already broken, as the game's maps keep ruined walls. The Break row is in the Wall and Floor sections of made pieces, and in a Damage section on the map's own fracturing pieces: its walls, storey floors and roof slabs, where they stand, moved, or copied.

Cover blocks and invisible floors

Two pieces the game never draws, both under Kind: Invisible in the piece list. A cover block adds cover and blocks movement where the map has nothing to do it, as Long War's own map patches do (or, with Cover set to None, only blocks movement). An invisible floor is something to stand on where the map has no floor. Both work on plain Enemy Within too.

A high cover block, a low one and an invisible floor on the Bar's car park, the high block selected with its handles and its panel
A high cover block (orange), a low one (blue) and an invisible floor (green), as the editor draws them.
  1. A high cover block: full cover for a unit beside it, and it blocks sight.
  2. A low cover block: half cover, and units see over it.
  3. An invisible floor: a thin plate with its top at the height you place it at.
  4. Its handles: drag a white dot to move that face (four sides, the top and the bottom) and size the block.
  5. Cover: high, low, or none (a blocker), and under it what the block does to line of sight: a high block stops it as a wall does (a unit beside it can still lean round its ends), units see over low cover and through a blocker.
  6. Its size and what it will do where it stands, in words.

To place a cover block: press P, choose Kind: Invisible, pick Cover block and click its first tile; with tile snap on it stays on the tiles. It starts as one tile of high cover, one tile tall. Size it with its handles and set its cover in the piece panel. Turn it with R; with snap off, the turn handles can also tip it onto its side.

To size a block: select it and drag one of its white dots. Each moves one face along the block's own axes: its four sides, its top and its bottom. The snap setting on the rail sets the steps:

A drag on a low side (−X, −Y) moves the block's corner, so the far side stays where it is. Esc during the drag puts it back, and each drag is one undo step. A block can be 8 units to 16 tiles across, and its bottom can leave the floor.

A block smaller than a tile does what the game's tile rules make of it. The panel says which, for where it stands:

To stop units walking somewhere without giving cover: place a cover block and set its Cover to None. It becomes a blocker (drawn purple): units can't walk into its tiles or stand on it, units beside it get no cover from it, and units see past it. It sizes, turns and breaks with a piece as any cover block.

To place an invisible floor: pick Invisible floor in the same list. Size it with its four side handles, as a block, and set its height with the Z field. It carries the tiles whose centres it covers, since the game looks for a tile's floor at its centre; the piece panel counts them.

Prefabs

A prefab is a set of pieces saved to be placed again as one thing: a barricade, a market stall, or a whole building with its lights. Prefabs are kept in a library of their own, apart from maps and projects, so one can be placed in any map and passed on as a file. They are listed under Prefabs in the piece list.

The piece list showing the prefab library
  1. Prefabs, beside This map and All maps.
  2. Filter by name, or by the name of a map its pieces come from.
  3. New opens an empty prefab builder.
  4. Save selection… saves what is selected in the view as a new prefab.
  5. Import… adds a prefab file someone passed on.
  6. A prefab: its picture, name, what it holds and the tiles it covers. Click it to place it.
  7. Edit, Rename, Duplicate, Export and Delete.
  8. How many prefabs the library holds. Hover it to see the folder they are kept in.

To save one: select what should be in it, then press Save as prefab… at the top of the piece panel (or Save selection… here) and give it a name. Box select takes a whole building at once; with the Normal button's switches on it takes the lights and the building's floor boxes too. The window says what goes in, and lists anything that can't. While it saves, a bar counts the pieces copied to the library (the first save of a map's pieces takes a while).

To place one: click it in the list, then click in the view. R turns it a quarter turn before you click; Shift+click places it and keeps going. It arrives as one group, named after the prefab in the piece panel: it selects, moves, copies and deletes as one. Ungroup it to change single pieces; the groups it had inside stay groups. Placing is one undo step.

Passing one on. Export saves the prefab as a small .json file. It holds the names of the pieces, where they stand and any saved recipe keys. The recipient needs game maps with those pieces. Import… adds such a file to your library. If the library already has that prefab, the editor asks: Replace it saves the file over yours, Keep both adds it beside yours with "(imported)" after its name. Delete moves a prefab's file to the library's .workshop\deleted folder instead of erasing it.

The prefab builder

New in the Prefabs tab opens an empty workspace in the main editor. A row's Edit opens that prefab for editing, including imported prefabs and ones saved from a map selection. The map browser (M) also has a Prefabs group.

Add pieces from All maps, or place another prefab and use Ungroup to edit its pieces. Choose Lights for point and spot lights, or Invisible for cover blocks and invisible floors. The Buildings, Lights and Effects views, box select, nested groups, copy, paste and undo work as in a map, and a prefab's effects are drawn as they look. The ground grid grows with your work; it is a drawing guide and is never saved. Negative X and Y are fine.

In the builder the header's Project button reads Prefab, and its menu is the prefab's. Prefab → Save (Ctrl+S) saves everything, including lights and floor boxes hidden by the current view. Floor boxes alone can be saved. The first save asks for a name; later saves write the next revision. Save as… makes another prefab, or explicitly replaces a different one after confirmation, leaving the original unchanged. To update the one being edited, use Save.

The footprint and height appear at the bottom. Height 0 is the drawn grid. A map holds at most 256 by 256 tiles, and a tile grid 0 to 1,920 units high (30 levels), with up to 192 units sticking out under or over it: a hull or crater under the ground, a roof, floor boxes, lights. Out of the grid there are no tiles, so nothing there can be stood on or give cover; the readout says when something sticks out. Light influence radii do not count. The usual cursor storeys are guides; floor boxes can have other heights. A prefab larger than a map holds is saved and placed all the same, with a warning on the readout and on its card. Nothing is lifted automatically. A selection saved from a map keeps its height: the map's grid bottom becomes 0. A prefab placed where it reaches outside the map's grid is placed, with a notice saying how far it reaches out.

Under the readout, a Problems chip says what Test in game would say of the prefab as it stands, without building it: how many pieces would be left out and how many warnings there are. Click it for the list; a row selects its piece. It is checked when you open and save the prefab, and Check again brings it up to date after an edit.

The test stage's ground is hidden: it is still there to stand on, so what reaches under it shows, and the game draws its own tile grid under the cursor. A noon sky surrounds the stage, above and below. A test battle has no aliens.

Doors, ladders, cars, vans and fracturing pieces are meant to stand whole tiles and levels from where their originals stand. When one is off that grid, a warning over the size names it; it still builds and tests, but what the map saved for its tiles no longer fits exactly. Show selects it; Align to grid moves the whole prefab, lights and floor boxes too, the smallest distance that puts every such piece on the grid, in one undo step. Move it by whole levels afterwards to set its height: it stays aligned.

When you open a prefab with missing pieces, the builder looks for the same recipes in your local map catalogue and warns about pieces it still can't load. Matches keep their positions and links. You can undo the recovery or save the prefab with its new sources. Unresolved records stay in the document. After scanning or rescanning All maps, use Prefab → Find missing pieces to try again. Unsaved changes to an already saved prefab are kept for recovery and offered when you reopen it. Opening a map, project or prefab asks Save, Discard or Cancel first if there are changes. A failed or cancelled save keeps the current workspace open.

Glowing props, such as neon signs and lamps, carry their matched area lights when you move or copy them in a prefab. Quick builds keep those lights live, and baking adds their glow to nearby static surfaces.

Testing a prefab in game

In the builder, Test in game… stands in the header where Play does in a map. Its dialog shows the prefab's dimensions and the game install that will open. Build and test uses the current contents, including unsaved edits or a prefab you haven't named. Bake the lighting is off by default, for a quicker check of appearance, movement, cover or cutaway; the stage has a neutral fill light either way. Tick it to see the prefab's shadows and the glow of its lights on nearby surfaces. Its effects and sounds play in the test, each read from the map it was saved from.

Test in game dialog with Bake the lighting and Enable saving unchecked and a Build and test button

The battle starts on the blank stage with the prefab placed beside the squad. If the entire footprint leaves no room for the squad, or the editor can't resolve all the pieces, the progress window shows the problem. You can cancel preparation or building there. If you reload before the build launches, reopen the test and choose Launch test when it is ready. Close XCOM when you finish to restore the test install.

The map

What belongs to the map as a whole: its lights and effects, its buildings, its size, where the squad and the aliens start, the missions it serves and the picture the game shows for it.

Lights

The map's placed lights can be edited as pieces are. The Lights view in the tool strip (Shift+L) shows them as markers: a bulb for a point light, a cone for a spot light, each in its light's colour. Grey markers are view only, hollow ones are switched off. While the view is on only lights can be selected, so a piece is never moved by accident; a light that is in a group moves on its own here. To handle lights together with pieces, use the Normal view's Lights switch instead.

A spot light selected in the Bar, with its cone drawn, its handles and the light panel
A spot light selected: its cones drawn in the view, and the light panel on the right.
  1. Lights view turns the view on and off. Click a marker to select its light. Move, turn, copy and delete it as you would a piece.
  2. Radius handle: drag the white dot to change how far the light reaches.
  3. Outer cone handle (spot lights): drag the dot on the left of the rim. Nothing is lit outside this cone.
  4. Inner cone handle: the smaller dot on the right. Inside this cone the light is at full brightness.
  5. Colour: the picker, or red, green and blue from 0 to 255.
  6. Brightness (0 to 100) and Radius in game units.
  7. Falloff (how fast it fades towards its radius: higher stays bright for longer, then drops) and, for a spot light, the inner and outer cones in degrees.
  8. On: unticked, the light stays in the map but lights nothing.
  9. What it lights: how many pieces the light is baked into, or reaches now that you changed it. A baked build relights those.
  10. Solo (O) dims the map and lights it with the selected lights alone, to see what they do.

Effects and sounds

A map's effects are its particle systems: fires, smoke, steam, dripping water, blowing trash, moths round a lamp, a Skyranger's lights. Its sounds are the ambient sounds placed in it: a car's idle engine, a humming machine, wind. Its lens flares are the glints round some lamps. The Effects view in the tool strip (Shift+X) shows all three as markers drawn over everything, and they are edited there as pieces are. While the view is on only they can be selected, so a piece is never moved by accident; to handle them together with pieces, use the Normal view's Effects and sounds switch.

The Effects view on the Bar's car park: a taxi's idle sound picked with its two spheres, the markers of effects, sounds and a lens flare around it, and the sound's panel
A car's idle sound picked: the spheres show where it is heard. Every spark is an effect.
  1. Effects view turns the view on and off. Click a marker to select what it stands for.
  2. An effect is a spark (here a body's webbing).
  3. A sound is a speaker.
  4. A lens flare is a star (here on a street lamp).
  5. The outer sphere's handle: drag it to set how far away the sound fades out to nothing.
  6. The inner sphere's handle: within this sphere it is heard at full volume.
  7. Wave preview: Play plays each of the sound's waves, one at a time.
  8. Plays from the start: unticked, the sound stays in the map but is silent until the map's script starts it.
  9. Its reach in words, as the two handles set it.
  10. Volume and Pitch: the game picks each between its least and its most.
The Effects view button with its flyout: Effects, Sounds and Lens flares

Hover the Effects view button for a switch for each kind: untick Effects, Sounds or Lens flares to hide its markers while you work on the others.

An effect's values

An alien vapour pod's smoke picked on the Bar, drawn as it looks, with its size handle and its panel's values
One of an alien vapour pod's smoke emitters picked: its green smoke drawn as it looks, its box, and its values in the panel.
  1. The picked effect: its marker and its box, drawn round the smoke.
  2. The size handle: drag it to make the effect larger or smaller, from 1/64 to 64 times its size in the map. The box and the drawing follow.
  3. Its chips, here Placed by a prefab.
  4. About: what it plays (its particle system and emitters), how it starts, its size and its box. Folded, the line says the first of these.
  5. Select all of its particle system: 21 of these on the Bar.
  6. Starts with the mission: unticked, the effect is in the map but switched off until the map's script turns it on.
  7. Its size against the map's, as the handle sets it.
  8. A particle parameter: a number, with a slider guided by the particle system's own range.
  9. A colour parameter: the colour, and its strength beside it. The maps' own often go past 1.

Effects a piece carries

An effect that stands on a piece, such as a claw machine's lights or an alien vapour pod's smoke, is carried by it: the piece's panel has a Carries an effect chip. Moved, copied or deleted, the piece takes its effects along, each keeping its place and turn on the piece; a copy's are drawn greyed. Move the effect by itself and it is its own from then on. A carried effect's panel has Keep where it is, which leaves it where the map has it while the piece moves, and Follow, which lets it follow again.

Lens flares

A lens flare moves, turns, copies, deletes and groups as an effect does, and box select and Select all take it. It has no values: its look and colour stay as the map has them. One that rides on a dropship stays view only.

Effects from other maps

The piece list's All maps lists the other maps' effects, sounds and lens flares beside their pieces. The Kind menu has Effects (with its kinds: Fire, Smoke and steam, Water, Light beams and glows, Nature, Alien, Wreckage and trash), Sounds (Machines, Engines, Nature and weather, Alien, Music and voices) and Lens flares. An effect placed the same way in several maps is one entry.

The piece list's All maps showing the fires, each row with a picture of the fire, and the first fire playing in a pane beside the list
All maps with its Kind on the fires, the pointer on the first one.
  1. Kind: here Effects: Fire.
  2. Its picture: the effect as it looks. A sound shows its speaker.
  3. An entry: its name, kind and particle system, what its emitters draw, and in how many maps it stands. Starts off marks one that waits for its map's script.
  4. The pointer on an entry plays it in a pane beside the list, turning slowly over a square one tile across, for size.
  5. What it is: where it is placed, the map it is brought from, and how much it adds to the map.

Effects as they look

Every effect is drawn where it stands, moving, from its particle system's own textures, colours, sizes and timing, in every view: a fire flickers, steam rises, moths circle. It is a likeness, not the game's picture: scrolling and rippling textures, lit particles, swirls and bounces, and one emitter setting off another are left out, and the panel says what a picked effect's drawing leaves out. The game is the judge of how an effect looks.

Buildings

To the game, a building is not its walls and roof. It is a set of invisible boxes laid over them, one or more for each floor. The boxes tell the game which pieces belong to which floor, and that is what lets you see inside:

The game's own maps have these boxes already. A piece you bring from another map comes without its building, and a house you put together from walls and a roof never had one. The Buildings view is where you give it one.

Without boxes

Pieces with no building around them are loose scenery. They stand, give cover, block sight and break as always, and soldiers walk in and climb as on any floor. What is missing is everything above: the roof never hides, an upper floor and its furniture stay drawn while you look at the ground floor, the walls stay at full height, and moving the cursor inside opens nothing up. A closed building without boxes can be played, but blind: the fight inside happens under a roof you can't see through. Fences, walls and ruins with no roof need no boxes.

The Buildings view

Buildings in the tool strip, between Add and Lights (Shift+B), turns the view on and off. While it is on, only boxes can be selected: a click on a wall picks the box around it, never the wall, so nothing of the building is moved by accident. Every building's boxes show in their floor's colour, the map's own as yours (The map's own buildings); only the few that stay as the map has them are grey.

Drawing a box

The Buildings view on the Bar's car park, a new box being dragged out over the tiles
A new box being drawn: the mouse button is still held.
  1. Buildings in the tool strip turns the view on. The panel on the right appears, and pieces can no longer be selected.
  2. New box (N) arms the tool: the cursor becomes a cross.
  3. Press where one corner of the floor is…
  4. …and drag to the opposite corner. The box follows by whole tiles and stays see-through, so you can see what it takes in.
  5. The line at the top says its size in tiles and the height it starts at. Esc cancels.

Let go and the box is made, one storey (192 units) high, and selected. It starts at the level under the cursor: on the ground here, on a floor if you start the drag on one. With a floor chosen in the Floors buttons it starts at that floor's height. It joins the building of the box you selected last; with none, it starts a new building.

Fitting a box and making the next floor

A building of two boxes, the upper one selected with its handles, the gizmo and the panel
A building of two floors: the ground floor's box in blue, the second floor's in orange and selected.
  1. The top's handle: drag a white dot to stretch that face. The top and the bottom go to levels.
  2. A side's handle: a side goes to the tile lines. Hold Alt for steps of 8 units. Each dot stands off its face on a thin line, clear of the arrows.
  3. The Move tool's arrows move the whole box, by whole tiles and levels. A box is never turned.
  4. Bottom and Top: the heights the box runs between. They can be typed.
  5. Building and Floor: which building the box is a part of, and which of its floors (1 is the ground floor). New building in the list starts another.
  6. Name and Kind are the building's: a name for you, and whether it is a plain building or a UFO. What Kind changes
  7. What it takes in: how many pieces stand in the box, and how many of them cut down. Anything the Build would refuse is said here too.
  8. Copy and Delete (Ctrl+C, Del).
  9. A yellow line: where one of the cursor's floors starts over the box, with that floor's number and height. A storey's box should start at one. The cursor's floors

To add a floor above, select a box, copy it and paste (Ctrl+C, Ctrl+V): the copy lands on top of the original as the next floor of the same building, as in the picture. Then drag its top to where the roof ends. Move it from there if it belongs elsewhere.

With the view off, the Floors buttons cut your building down as they do the map's own, so you can check it: choose floor 1 and the roof should go and the walls drop.

Kind: Building or UFO

Leave Kind at Building for anything that is not the mission's alien ship: a house, a shed, a shop, and also a ship-shaped structure you only want as scenery.

What you see is the same for both kinds. A UFO's hull hides its roof and upper decks and cuts its walls down exactly as a house does, with the same boxes and the same rule.

UFO sets one mark on the building, the one the game's own crashed and landed ships carry. The only part of the game that reads it is the placing of the aliens at the start of a battle:

So choose UFO only for the building that is the alien ship of a UFO mission, where the aliens should gather in and around it. On any other building the mark does no good, and it may put a mission's aliens around the wrong building.

A UFO building is also what lets Missions… give the map a crashed or landed UFO mission: under Long War Rebalance, the commander's pod is put in it. A UFO prefab brings the ship's own pieces with it; a building you draw yourself is only the boxes.

Where a floor's box goes

Each floor's box starts at that storey's walking level and runs up to where the next storey's walking level begins. The boxes stack: the top of one is the bottom of the next. The reason is the game's rule for which floor a piece belongs to: a piece counts for a floor when it touches that floor's box and its bottom is more than 20 units under the box's top.

Part of the boxWhere to put it, and why
BottomAt the walking level of the storey. The floor you stand on, and everything standing on it, is then in that storey's box.
TopJust under whatever should hide: the roof, or the next storey's floor. That piece must start no lower than 20 units under the box's top, or it also counts for the floor below and stays drawn when you look inside.
SidesOn the lines the walls stand on, so the walls are inside.
The top storeyIt needs a box too, tall enough to take in the roof. A roof with no box around it never hides.

The cursor's floors: the yellow lines

The game keeps a second set of invisible boxes, apart from any building: the map's cursor volumes. They say which floor a height is to the cursor, and so where the mouse wheel stops as you go up and down. Your floor boxes decide what is hidden; the cursor volumes decide where the cursor goes. The two have to agree, or the wheel and the cutaway fall out of step.

How the cursor's floors work in a battle: each cursor volume carries a floor number. Rolling the mouse wheel moves the cursor to the next number up or down among the volumes over where it stands, and a click on a deck counts as the floor of the volume that height falls in. A place with no cursor volume over it has a single floor.

In the Buildings view, each of your boxes has a yellow line round it at every height where a cursor floor starts over it. On the selected box each line carries the cursor floor's number and its height (2 · 192).

A map opened before this was added prepares again the first time it is opened: the cursor volumes are read with the rest of the map.

A building with its pieces: Floor boxes in the normal view

In the Buildings view only boxes can be selected. To handle a building together with its pieces, hover the Normal view button in the tool strip and tick Floor boxes: your buildings' boxes are then drawn in the normal view as well. It is off whenever a map opens.

The map's own buildings

The map's own buildings are edited exactly as yours are. Their boxes show in their floors' colours; in the Buildings view each box can be moved, stretched, copied, pasted (a copy on top adds a floor) and deleted, and a box can be added to them; in the normal view, with Floor boxes on, a building is picked whole with its pieces, to move, turn, copy or delete, and it can be in a group.

Several boxes, or one big box

A floor that is not a rectangle (an L, a T, a house with a porch) is made of several boxes with the same Building and Floor. One larger box around the whole of it also builds, but the space it takes in beside the building counts as the building too:

So keep each box to the walls. A box that sticks out by part of a tile where nothing stands does no harm, and the ground floor is the forgiving one: it is never hidden, so extra pieces listed there change nothing you see. The panel's count of pieces in the box is a quick check: if it jumps when you stretch a side, the box has taken in something that is not the building's.

An example: a hut whose walls run from the ground to 256 and whose roof starts at 240. Floor 1's box from 0 to 176, floor 2's from 176 to 384. The walls reach into both, so they cut down; the roof starts well above 156 (20 under floor 1's top), so it is floor 2's alone and hides.

Map grid

The map's tile grid is the box the game plays in: the play area. Map grid on the left rail (or in the Map menu) shows the play area with a handle on each side that can move. Drag a handle to resize the grid. Click the button again, or press Esc, to put the handles away.

Map grid on the Bar: the play area's box with its red, blue and green handles, and the panel
  1. Map grid on the tool strip.
  2. The red handle moves the far X side, by whole tiles.
  3. The blue handle moves the far Y side, by whole tiles.
  4. The green handle raises the top, by whole levels.
  5. The size, against the map's own.
  6. Lay the map's ground over the new area, shown on maps whose ground is laid as planes.
  7. The map's own size puts it back; Done puts the handles away.

Clear map and landing zones

Clear map… in the Map menu takes every piece off the map, the ground too, so that you can build a new map with pieces and prefabs on an old map's light and landing. It is meant for an unchanged map, but it works on any.

The Clear map window on the Bar, with its counts and the tick to keep the scenery outside the play area

The ground grid

A faint grid on the ground's plane (the height the landing zones stand at), drawn only where there is no floor. On a map as it is you see it only over holes. On a cleared map it covers everything until you lay floors, which hide it where they lie. A piece placed over nothing lands on it. It is a View option, Ground grid, on at first.

Landing zones

Each landing zone is where the squad may land: the drop zone's frame, the evac zone, the six soldier tiles, an arrow the way the squad faces, and its number. The game picks one of a map's zones. They are drawn on every map (View options, Landing zones).

The Landing zones view on the Bar: its zone picked, with its gizmo and its panel
  1. Landing zones view on the tool strip (Shift+Z).
  2. The zone's number. Click it, or the zone, to pick the zone.
  3. The gizmo on the picked zone: arrows to move it, R for its ring.
  4. Kind: normal, or inside.
  5. Used by: Long War, plain EW, or both.
  6. Copy and Delete.
  7. Land here: play the build with the squad landing at this zone.

Until you change one, the zones are the map's original ones. The first change makes them the project's.

Spawn points: where the aliens start

The Spawns view (Shift+U, or its button on the tool strip) shows where the game puts things when a battle starts and while it goes on: the places the alien pods deploy at, where the Meld canisters can stand, the drop-in points where reinforcements come in, the soldiers' and other points, and the objectives of the mission the header shows (the bomb and its power nodes, capture points, radar arrays). They are markers drawn over everything, each in a halo of its colour. While the view is on, only they are selected.

The Spawns view on the Bar's ground floor: a pod picked with its arrows and its panel, another pod and Meld points around it
  1. Spawns view on the tool strip (Shift+U).
  2. The picked pod with its arrows: drag them to move it by whole tiles and levels.
  3. A pod (an orange ring): a place the game can deploy a group of aliens at.
  4. A Meld point (a green dot): a place a Meld canister can stand.
  5. About: its values, what uses it (the map's script, a wave, or nothing found), what the game does with it, and whether it stands where the map has it. A click on About folds it.
  6. Copy (Ctrl+D) and Delete (Delete).
  7. Its values: a pod's Commander's place, Secondary and Use; a Meld point has its difficulty, the turn it is destroyed on and its spawn group.
The Spawns view button with its flyout: a switch for each kind of point, Deleted points, and Scripted drop-ins land where placed

Hover the Spawns view button for a switch for each kind: pods, Meld, drop-in points, soldier and start points, objectives, other points and no-spawn volumes (the covert operative's, the VIP's and loot places, and the volumes), and patrol nodes, off at first. A map's starts for multiplayer teams are never shown: a single-player battle doesn't use them.

Deleted points, off at first, draws the map's points your project deletes, pale, so you can pick one and restore it. Under the switches is Scripted drop-ins land where placed (below).

The Normal view's Spawn points and objectives draws the same markers beside the pieces.

No-spawn volumes

A no-spawn volume is a box the game places no alien or civilian in when it looks for a free spot: the aliens of a pod deploying round its place, a unit dropped in, a civilian. Maps put them round parked cars and other props. The view draws each as a grey box round its marker.

A no-spawn volume picked in the Spawns view, round a van in the Bar's street: its box, its white handles, its arrows and its panel
  1. The picked volume's box.
  2. A side's white handle: drag it to move that side to the tile lines and levels (Alt for steps of 8). Each side has one, the top and bottom too.
  3. Its arrows move the whole box by whole tiles and levels.
  4. What it is: its size, and what the game does with it.
  5. Copy (Ctrl+D) and Delete (Delete).
  6. Keeps aliens out and Keeps civilians out: untick one to let them in.

The Build moves and stretches the map's own volume in place, and makes a new one from one of the map's volumes. A new one comes from the Add panel's Spawn points on any map.

What the game does with them

Missions

Missions… in the Map menu lists the base map's missions and the kinds a map can be given by its record alone: an abduction, a terror site, a bomb mission (Long War only) and a crashed or landed UFO (once a UFO prefab, or a building of kind UFO, stands on the map, with the UFO's type to choose). Tick the ones the project is for: the Build writes a map record for each, and the header's Mission picker and the play window list them. Each line says what that kind needs. A map that isn't cleared starts with all of its base map's missions; a cleared map is asked when it is cleared.

The Missions window on the Bar: Abduction ticked, Terror ticked as an added kind, and the other kinds with what they need
  1. The base map's missions: the Bar has an abduction.
  2. A kind added by its record, here a terror site, with what that kind needs under it.
  3. OK needs one ticked; the change is one undo step.

Map picture

Map picture… in the Map menu gives the project a picture of its own for the game's mission screens. Long War Rebalance 3 shows a map's own picture; plain Enemy Within and earlier Long War versions don't look for one. The picture is kept with a saved project, so save the project first.

The Map picture window: an image taken from the view with its frame, and under it the picture as the game will show it
  1. The image, and the frame the picture is cut from, twice as wide as it is high. Drag the frame to move it; drag a corner or turn the wheel to resize it. The arrow keys and + and - do the same.
  2. Choose image… takes a file (.png, .jpg, .bmp or .webp). A file can be dropped on the window too.
  3. Take from the view uses the 3D view as it is now, without the editor's helpers: no grid, handles, markers, cover blocks or invisible floors.
  4. The result, as the game will show it: 512 by 256, in the game's own compression.
  5. Remove picture takes the project's own picture away.
  6. Use this picture keeps the cropped picture, and only that, with the project.

Projects, building and playing

Saving your edits as a project, building it into a map, playing that in the game, and passing maps on to other players.

Project menu

A project is your set of edits on one base map. Until you save one, edits are a trial that a reload loses (the browser asks first).

The Project menu, its items numbered
  1. The open project: its name, revision, when it was saved, the name its map builds as in the game (fixed when the project was first saved), and its last build.
  2. Save (Ctrl+S) saves the next revision. With no project open, it asks for a name.
  3. Save as… saves what is on screen under a name: a new project, with a map name of its own, or in place of another, which keeps its map name. More
  4. Open… (Ctrl+O) opens a saved project, switching map if it is of another.
  5. Close project goes back to the original map.
  6. Recent: the last three projects. Click one to open it.
  7. Manage projects… lists every project with its last build, to build several one after another, install them in the game for campaigns or export them as a map pack. More

Building and playing are on the header itself (Build, Play), and the map's own items are in the Map menu.

Save as… and Open…

Save as… and Open… open a list of your projects with each one's map, revision and when it was saved. Click a column head to sort. Type a name, or pick one; Enter or a double-click chooses. Saving under another project's name asks before replacing it. Show switches between this map's projects and all of them.

Under the name, Save shows what the project builds as: the name its map has in the game and its package (CommercialRestaurantFix.upk, which holds its baked lighting too). A new project's is its name as one word, accents taken off, at most 24 characters (so the files that go with it fit the game's limit), numbered (_2, _3…) when another project, a build or a map of the game already has it; the window says why. It is fixed once the project is saved, so a build always replaces its own files: to build under another name, use Save as… with a new name, which makes a new project. Projects saved with an earlier version keep the names they had.

Save project: the projects listed, a new name typed, and under it what the project builds as
  1. Your projects, this map's or all of them.
  2. The name to save under.
  3. Show: this map's projects, or all.
  4. Builds as: the map's name in the game for that name.

Build

Build, at the right of the header (Ctrl+B), saves the project if it has changes, then makes its variant: the map with your edits made in it, in the editor folder's builds\<variant name>\. A build replaces the project's last one, and installs nothing. The button is greyed until the edits are saved as a project.

The Build panel with its one choice, Bake the lighting
  1. Bake the lighting, off each time the panel opens.
    • Off (a quick build): seconds. Cover, pathing and line of sight in the game are right; the lighting around your changes isn't: copies are lit as their originals were, and moved or deleted pieces leave their shadows behind.
    • On (a baked build): a minute or two for a small edit, less when the project is built again. The editor relights the map around your changes.
  2. Cancel (Esc) builds nothing. On its left, about how long the build will take, from the project's last build of that kind.
  3. Build (Enter). Opened from Play, this button reads Build and play, with Play last build beside it when the last build is of what is on screen.

While it builds, a window covers the editor and takes no clicks: the steps with their times, a bar for the step running, and the time so far. Show the log unfolds the build's own output, and Cancel the build stops it, leaving the last good build as it was. When it ends, the window shows the build's folder or why it failed, and Save a bug report. Click the folder's path to open it in Windows Explorer, or Copy the folder path. Once built, Play in game installs the build and starts XCOM in a battle on it, as the header's Play does.

What a build holds. The map, with its baked lighting inside it, its mission records and its map picture if the project has one, and a README that lists the config lines the game needs.

Warnings don't stop a build. They say what may behave oddly in the game: a piece off its grid, a ladder that isn't expected to climb, a floor box that starts away from the cursor's floors, a landing zone over no floor, fewer places for the aliens' pods than the map had. The map is built all the same, and the build window lists them.

If the project holds an edit that can't be built at all, the build stops at once and says which piece and why. Undo that edit, or fix it as the message says, and build again.

Play

Play, at the right of the header, starts XCOM straight in a battle on the open map, with the test squad: no campaign to start, and no save to load. The editor calls this Play in game.

The play window for a project: the enemies, the squad's line, Bake the lighting, Enable saving, and Build and play
  1. Squad: the test squad in a line. Click it to open Test squad setup over the window; saving there brings you back.
  2. Bake the lighting, as in Build: leave it off while the layout is changing.
  3. Enable saving: a battle you can save and load. More
  4. Build and play builds the project, installs the build in the game under its own name and starts XCOM. Play last build shows beside it when the last build is of what is on screen. On the left, about how long the build takes.

Enable saving

A test battle starts by itself and can't be saved. Tick Enable saving to save and load in it. The tick is in the play window, in a prefab's Build and test, and in the tab on a finished build's Play in game button (its words show when you point at it).

What a test battle is, and what it changes

What the test battle is. A plain battle on the map, started the way the game's own developers started one: the map's usual landing and aliens of the game's choosing, with the test squad (six squaddies until you set it up). It is right for cover, pathing, line of sight, destruction and lighting. It is not a campaign mission: your soldiers, the mission's story and its rewards are not in it.

What Play in game changes. It copies the build's files into the game and adds one line to DefaultMaps.ini: a record for your variant under its own name, kept out of the rotation, so no campaign ever draws it (with Long War, it also adds landing-zone lines). No line the game had is changed, and it keeps a backup of every file it changes in <game folder>\XCOM Map Workshop\. While you play, the game rewrites one of its own settings files (XComContent.ini) with the test squad in it: the editor keeps the file aside first and puts it back when the game closes, so leave the editor open until then. If it was closed, the file goes back the next time the editor starts.

Through Steam. The editor asks Steam to start the game on the map, so nothing needs setting up in Steam. The game folder the editor plays in must be the one Steam runs.

To compare with the original: close the project and choose Play. The same map plays as the game has it, and nothing is installed for its first mission. Another of its missions gets a copy of that mission's record ahead of the map's own while the game runs, taken out when it closes (Basic Training, the tutorial's map, gets a copy of its map record, since the game keeps its own switched off; Game maps' Undo everything takes it out).

The Game menu

The arrow joined to Play opens the Game menu: what a play lands with, and what the editor has done in the game.

The Game menu under Play's arrow: Test squad setup, Game maps, the squad's line and the Installs
  1. Test squad setup…: the squad every play lands with. Under the items, a line says which (Squad: Test squad · 6 units).
  2. Game maps… shows the game's map records and what the editor changed of them, and undoes it.
  3. Installs: the game folder the editor reads, the one it plays in, how the game is started there, and what the editor has installed in it.

Test squad setup

Test squad setup… in the Game menu sets up the one squad every Play in game lands with, for maps, projects, Land here and prefab tests alike. The menu and the play window show it in a line (Squad: Test squad · 6 units); a click on that line in the play window opens the setup over it, and saving there brings you back to the play window. Until you save one, the squad is six squaddies, the ones Play in game always landed with; the panel names their gear as the install does (under Long War Rebalance a shotgun and Gauss weapons, a recoilless launcher, grenades and a medikit).

Test squad setup: the default six on the left, the first soldier's kind, names, class, armour, weapons and items on the right
The default squad, its first soldier open.
  1. The units in the order they land. Click one to set it up on the right.
  2. Add, Copy, Remove and the arrows that move a unit.
  3. Kind: soldier, MEC trooper or SHIV.
  4. Names, class, rank, look and country.
  5. Armour, and under it what it gives.
  6. Sidearm, weapons and items in order; perks and base stats follow below.
  7. Show every item widens the lists.
  8. Export…, Import… and Reset to default.
  9. Save (Ctrl+S); Cancel leaves the saved squad as it was.

The lists are those of the install Play in game uses, read from the game's own data, so a modded install offers its own items under its own names. Each change is checked at once. Errors (red) stop a play: an armour with no body, a MEC without its gun, a name the game can't take. Warnings (amber) say what the game will do with something odd, and never stop it: a SHIV's second gun stays behind, Long War Rebalance gives a MEC no grenades, and it lets one SHIV act each turn (its Robot Overlords option lifts that; the editor leaves the game's options alone). Under Long War Rebalance a battle scanner or smoke grenade gets its charges the way a campaign soldier's does. On plain Enemy Within, and Long War without Rebalance, the squad holds soldiers only, six at most.

Save (Ctrl+S) keeps the squad; the next play lands with it. Cancel (Esc) leaves the saved squad as it was. Reset to default brings back the six squaddies, and Import… reads a shared squad file; both change only what the window shows until you save. Export… saves the squad to a .xcomsquad.json file to share: an item or perk another install lacks is kept and shown as not on this install, and left out of the play with a note (a missing armour is an error, as the body comes from it). If the squad was saved elsewhere meanwhile (another tab), Save says so and keeps your changes: use the saved squad, or save yours over it.

Game maps

Game maps… in the Game menu opens a list of every map record in the game's DefaultMaps.ini, by map: its mission, whether missions draw it from the rotation or ask for it by name, and what the editor did to it. A record of the game's own has a tick: untick it and the game stops using it (its line is commented out), tick it to bring it back. A record a project's build replaces says by which project, and stays off while it does. The records the editor added are listed under their base map, each with Undo, which takes that build out of the game's maps and brings back the map it replaced. Undo everything takes all of the editor's back out, files included: the game's config files end exactly as they were. Type to filter, or pick under Show (changed by the editor, in rotation, asked for by name, not in use); Switch off the shown and Switch on the shown act on every record the filter shows. Group by lists the records by map or by mission, to see which maps each kind of mission draws from. All of it needs XCOM closed.

Manage projects

Manage projects…, at the foot of the Project menu, opens the project manager: every project on the left, with its base map, when it was saved, whether it has a picture of its own, a badge if it is in the game, and its last build in one word: Ready, Not baked (a quick build), Out of date (saved again since) or Not built; its tooltip says when it was built and by which editor version. Type to filter, or pick All, Ready, Needs a build or In the game; tick projects one by one, a run of them with Shift+click, or all that the filter shows (Ctrl+A). A double-click opens one. The ticked projects are listed on the right, each with how it goes into campaigns: Additional, in the rotation beside the original map, or Replace, in its place (Set all to does them all). One install or one pack can replace some maps and add others. Then Install in the game (with XCOM closed) or Export map pack, which zips them for other players: Map packs.

Additional or Replace. Replacing comments out the original map's records for the missions your map has records for, so the game no longer uses it there (for the missions your project leaves out, the original stays); for a council mission, which asks for its map by name, your map takes the original's record name, and so it does for a new campaign's first mission, which asks for Commercial Alley Redux by name. Beside the original, a map is never picked for a council mission (but a bomb mission under Long War, which makes an extra one of it). The manager warns under each ticked project, without stopping you, about a build whose lighting is not baked, a build older than its project, and what happens to its missions: the ones the game asks for by name, and under Replace the ones left to the original.

The project manager: four projects on the left, two ticked and listed on the right with the pack's fields under them, and a queue of two full builds, the second building
Two projects ticked and built as a queue: the first is built, the second building.
  1. Filter by name, map or mission.
  2. Show: All, Ready, Needs a build or In the game, each with how many.
  3. Sort: last saved, last built, name or map.
  4. A project's last build in one word, its revision and whether it is baked; while the queue runs, its place in the queue.
  5. The ticked projects, with × to take one out. A project not built yet says so.
  6. Additional or Replace: how this one goes into campaigns. Its warnings are listed under it.
  7. The queue: the project building, its step, the time so far, and about how long is left, with Stop, Resume and Clear. More
  8. Build and Install in the game, for the ticked projects.
  9. Pack: a new pack with its name and author, or one you exported before. More
  10. Include editor project files puts each map's project in the pack too.
  11. Export map pack zips the ticked projects' builds.

Building several: the queue

Build, in the project manager, builds the ticked projects one after another while you go on editing. Each is a full build, its lighting baked, as the editor's own Build makes it with Bake the lighting ticked. A project is built as it is saved when its turn comes: one saved again while it waits is built as saved last, and the open project's unsaved changes are saved first when it is ticked. Needs a build, above the list, lists the projects a full build would bring up to date (not built, not baked, built from an older revision or by another editor version), ready to tick with Ctrl+A. The manager can be closed meanwhile: a chip in the editor's header says how far the queue is, and a click on it opens the manager again.

Map packs

Export map pack, in the project manager, zips the ticked projects' builds for other players: one file, <pack> v<n>.zip, in the builds folder's Map packs. It holds the pack's folder, two scripts and a README, and needs no editor to use.

The Pack fields (item 9 of the project manager's picture):

The export warns, without stopping, of a build whose lighting is not baked or that is older than its project, two maps of the pack the game would show under one name, and a card number another pack in your install already has.

Settings

Settings, the gear at the right of the header, holds the editor's own setup.

Other windows

How pieces move and what builds

Kinds of pieces

KindExamplesHow it movesBuilds
Scenery, destructible propsTables, crates, dumpsters, windows, signsFreely, on every axisYes
Physics propsBodies, loose objectsFreelyYes
CollectiblesUFO power coresFreelyYes; a copy isn't loot
Cars and vansWith their glass, doors and light barsOn the grid (below), all parts togetherYes
Doors with a frameBuilding doorsOn the grid, leaf and frame togetherYes
Doors without a frameUFO and alien doorsOn the gridYes
LaddersOn the gridYes; it climbs where both ends meet floor, and is warned of where they don't
Fracturing piecesWalls, storey floors, roof slabs, a bar's counterOn the gridYes; a wall, floor or roof can be built broken
Walls, floors, roofs and ground you drawThe Build menu's piecesWhole tiles; sized by their handlesYes; walls, floors and roofs break as the game's do
Cover blocks, invisible floorsInvisible piecesFreely; on the tiles with tile snapYes
LightsPlaced point and spot lightsFreelyYes; baked builds only show them right
Effects, sounds, lens flaresFires, smoke, an idle engine, a lamp's glintFreely; a carried effect with its pieceYes, in a quick build too
Floor boxesBuildings, yours and the map'sWhole tiles and levels, never turned aloneYes
Landing zonesWhere the squad landsWhole tiles and levels, quarter turnsYes
Spawn pointsPods, Meld points, drop-in points, no-spawn volumesOne at a time, whole tiles and levels, quarter turns (drop-in points); a volume's sides by its handlesYes
A mission's objectsThe bomb and its power nodes, capture pointsWith their group, whole tiles and levelsYes
Patch helpersLong War Rebalance's invisible cover and blockersNot at allLeft as they are

The grid rule ("recipe snap")

The game saves some things per tile: where a ladder can be climbed, which part of a wall stands on which tile. For the Build to carry those along exactly, such a piece must end up a whole number of tiles (96 units) and storeys (64 units) from where its original stands, turned by quarter turns.

Ladders

The game makes a ladder's climb between two floors: the tile at its foot, and the tile at its top or the one below that. Select a ladder and the editor marks both ends, green where there is floor and red where there is none.

Floor pieces and Level snap

A floor piece is one the game walks on: asphalt, a sidewalk, a building's storey floor. The piece list gathers them under Kind: Floors, each with its size in tiles. With Level snap on, a floor piece you place keeps the height its kind has in the map, moved by whole levels to the floor under the cursor, so a sidewalk dropped next to another sits at the same height instead of on top of it. With a floor number chosen in the bottom bar, it goes to that floor. Moved with the handles, it steps up and down by whole levels.

What a mission adds

The game loads more than the map: each mission that uses a map adds its own objects, and Long War Rebalance adds a patch to most maps, mostly invisible cover blocks and blockers. The editor shows the patch so you can plan around it, but it isn't part of your project. So if you move a wrecked car that Long War Rebalance has put invisible cover over, the cover stays where it was. Untick Hide patch helpers in View options to see it.

A mission's own objects (the bomb and its power nodes, the data recovery's capture points, radar arrays, the operative's and the VIP's places, the waves' drop-in points) show as markers with the mission the header picks, in the Spawns view and with the Normal view's Spawn points and objectives. Click one: its panel says what it is, the group it belongs to and what lists it. With it picked, drag its arrows to move it with its group (a capture point with its volume, a power node with its button, effects and rebuild volume) by whole tiles and levels; Esc during a drag puts it back, and Ctrl+Z undoes. The Build moves them in its own copy of the mission's stream, which only that mission's record uses, so every reference the mission's script has to them still holds. It warns when an edit leaves an objective or a squad's, operative's or VIP's place with no floor, or inside a piece, mission by mission, so you can move it or drop the mission.

Slaughterhouse Redux with its council bomb's objects shown: the bomb picked with its arrows and its panel, power nodes, drop-in points and pods around it
The council bomb's objects on Slaughterhouse Redux, cut down to its ground floor, the bomb picked.
  1. Mission in the header: the mission whose objects are shown, here the council bomb.
  2. The picked object's arrows: the bomb moves with its group, by whole tiles and levels.
  3. A power node, with its button's marker (a blue gem, a thing to use) on it: they move together.
  4. A drop-in point (a red arrow), where a wave of aliens comes in.
  5. A pod (an orange ring): where a group of aliens starts.
  6. Its panel: what it is, what moves with it, and what lists it.

Copies

Keyboard and mouse

KeyDoes
V · G · RSelect · Move · Rotate
TBox select; then Enter selects what is inside, Shift+Enter adds it to the selection, Esc puts the box away
PAdd: open or close the piece list
XWorld axes or the piece's own
CPivot: the piece's own origin, or the selection's middle (a piece turns in place)
BShow or hide the play area; with a made wall, floor or roof or one of the map's fracturing pieces picked, Break on or off
LLevel snap on or off
Shift+NThe Normal view
Shift+BThe Buildings view on or off (only boxes are selected)
Shift+LThe Lights view on or off (only lights are selected)
Shift+ZThe Landing zones view on or off (only landing zones are selected)
G · R · [ ]In the Landing zones view: the picked zone's arrows · its ring · a quarter turn either way
Ctrl+D · DelIn the Landing zones view: copy the picked zone · delete it
Shift+XThe Effects view on or off (only effects, sounds and lens flares are selected)
Shift+UThe Spawns view on or off (only spawn points and objectives are selected)
[ ] · Ctrl+D · DelA picked spawn point: a quarter turn either way (a drop-in point) · copy it (a pod or a Meld point) · delete it
Shift+drag a move handleDrag a copy of the selection; the original stays
NIn the Buildings view: New box
Shift while drawingFrom the Build menu: keep drawing after each wall, floor or ground shape (Esc stops)
IWhile drawing from the Build menu, or in the look picker: take the look of a piece clicked in the view
Alt+dragIn the Buildings view: stretch a box by steps of 8 units
OSolo the selected lights
F, double-clickFrame the selection
MMap browser
W A S D, arrow keysMove the camera: across the map, or along the view with View options' Keys move along the view (Shift: faster)
Q · ETurn the camera left or right (Shift: faster)
Ctrl+C · Ctrl+X · Ctrl+VCopy · Cut · Paste (then click to place)
R · Shift+RWhile placing: turn a quarter turn, either way
Shift+clickWhile placing: place and keep placing
DelDelete the selection
Ctrl+GGroup the selection
Ctrl+Shift+GUngroup
Ctrl+Z · Ctrl+YUndo · Redo
Ctrl+S · Ctrl+OSave the project · Open a project
Ctrl+BBuild
EscCancel a drag, stop placing, close a menu, or clear the selection

The mouse: drag to orbit, right-drag to pan, scroll to zoom, click to select, Ctrl or Shift+click to add to the selection.

What it can't do yet

This is a preview. Before you plan a map around it, these are the things it does not do.

Maps and pieces

  • A new map starts from one of the game's. Clear map empties it, and you build on its light, sky and landing. The sun, the time of day and the mission stay the base map's.
  • Only the game's own models, materials and sounds. Any piece of any map in your install can be placed, and walls, floors, roofs and ground you draw take the look of the game's, but you can't import your own models, textures or sounds.
  • The game's pieces move and turn only. No resizing or reshaping, and no changing a piece's material or colour. What you draw yourself is sized by its handles. A light's colour can be changed, and an effect's size and particle settings and a sound's reach, volume and pitch: Effects and sounds.
  • No free ground sculpting. The map's ground is made of pieces: you can move, copy and delete them. New ground is patches, blocks, ramps and rocks, not a surface you push and pull.
  • Only the maps your install plays. Maps the game's files hold but its map list leaves out aren't offered.

Missions and gameplay

  • No mission scripting. What the mission's script does, its timers and triggers, and when reinforcements come stay as the base map has them. Where things are can be changed: the squad's landing zones, and the aliens' pods, the Meld and the drop-in points in the Spawns view. A drop-in point can be moved, not added.
  • Pieces the mission script uses are best left where they are. A piece marked Mission script, moved or deleted, builds, but the script goes on acting on the original; one of the landing's own pieces, moved or deleted as a piece, breaks Long War's landing. The Build warns of both. Move the landing zone instead.
  • Long War Rebalance's invisible cover and blockers can't be edited. They show for reference. A mission's own objects (a bomb, the data recovery's capture points) can be moved, but not copied or deleted: what a mission adds.
  • Under Long War, the aliens' pods and the Meld go where its rules put them whenever it finds room for them, and so do the bomb and its power nodes. Your places for them play where it doesn't, and on plain Enemy Within: what the game does with them.
  • Cover, pathing and line of sight aren't shown or set by hand. The game works them out from the pieces when the map loads. The editor's tile grid is a guide, not the game's answer.
  • No play-testing in the editor. No units, no fog of war, no destruction. You test in the game.
  • No campaign in a test battle. Play in game starts the mission you pick, with the test squad (six squaddies until you set it up) and four Sectoid pods (EXALT pods on EXALT's missions), not your campaign's soldiers. The battle starts by itself and can't be saved unless you tick Enable saving. UFOs and alien bases come without their commander.

Building

  • Some pieces are surest on the grid: ladders, doors, cars, vans, walls, storey floors and roof slabs build exactly by whole tiles and quarter turns from where their originals stand. Off that grid they build with a warning. More
  • A ladder needs floor at both ends where you put it, or the Build warns that it isn't expected to climb.
  • The Build warns far more often than it refuses. A warning means "this may behave oddly in the game", and the map is built all the same. That includes a single part of a car or a door edited on its own. Pieces of a kind the Build has not made before, and pieces of other maps the library used to hold back, are built as any other. A piece the Build can't make at all is left out and listed in the build window, and the rest is built. The prefab test does the same and waits for Launch test when it left something out.
  • Some lights are view only: the sun, moon and sky, the glow of lit surfaces, and lights the map's scripts or a breakable piece switch. New lights are point or spot lights.
  • Light edits need a baked build. A quick build makes them without their lighting.
  • One build at a time, and a baked build takes minutes.

The view

  • It is not the game's picture. Colours and lighting are approximate, most lights cast no shadows, and there is no fog, sky, decals or animation. Doors stand closed. Effects are drawn as a rough likeness, from their own textures and colours but without the game's shaders: Effects as they look.
  • No preview of the baked lighting. Only the game shows what a build's lighting looks like.

The program

  • Windows 10 or 11 only, 64-bit, for one person on one computer.
  • Developed and tested mainly with Long War Rebalance. It is meant to work with plain Enemy Within too, but that is less tested: reports from plain Enemy Within, or any setup other than Long War Rebalance, are welcome (Reporting a problem).
  • A project or prefab saved in a newer version doesn't open in an older one. A newer version opens what an older one saved, and builds you made keep playing.
  • It installs only while the game is closed. Play starts XCOM itself, through Steam.

Things to expect in the game from a variant come next: In the game: known limits.

In the game: known limits

New in this version

What has been added since version 0.4.1, each with the section that explains it: first what 0.6.0 adds, then 0.5.3, 0.5.2, 0.5.1 and 0.5.0.

New in 0.6.0What it is
Walls, rooms, floors, roofs and ground of your ownThe Build menu on the Add button: pick a tool and drag it out in the view. Walls take doorways and windows, and a rock is shaped by its points.
The look pickerA drawn piece in the look of any wall, floor, roof or ground of your game's maps, chosen from pictures or taken from a piece in the view.
Break and RepairFragments knocked out of a drawn piece, or of one of the map's own breakable pieces, so the battle starts with the damage.
Effects and soundsThe Effects view: the map's fires, smoke, sounds and lens flares moved, copied, deleted and tuned, and those of other maps added.
Spawn pointsThe Spawns view: where the aliens' pods, the Meld and the drop-ins start, moved, copied and added, with no-spawn volumes.
Map pictureThe picture the game shows for your map on its mission screens, from an image or from the view.
Map packs for Long War Rebalance 3A pack that is one folder dropped into the game, with no file of the game changed. The editor remembers your packs.
The header's menusProject and Map menus, Build and Play as buttons, the Game menu on Play's arrow, and setup under Settings. Find a piece is gone.
Add to groupThe selected pieces join a group that is already there.
New in 0.5.3What it is
Piece flagsFive flags in the piece panel: Blocks walking, Gives cover, Blocks sight, Floor and Mouse picks it. The Build writes them on the piece and works its tiles out again.
Select all of a kindEvery piece drawn with the same mesh as the picked one, or only those inside a drawn box, to change them all at once.
Test squad setupThe squad every Play in game lands with, set up from the Game menu (the arrow beside Play): under Long War Rebalance up to eight soldiers, MEC troopers and SHIVs, with their gear, perks and stats.
Build in the project managerFull builds of the ticked projects one after another while you go on editing, followed by a chip in the header.
The project managerLaid out again: your projects on the left with their last build, the ticked ones on the right, each with its own Additional or Replace. A map pack can carry the maps' editor projects.
Maps named after their projectA new project builds as its own name, shown under the name in Save and fixed once saved.
256 tiles a sideMap grid makes maps up to 256 tiles across and deep.
New in 0.5.2What it is
The mission you pickPlay in game plays the mission the header's Mission picker shows, not always an abduction.
Missions…Which of the base map's missions a project is for, and missions a map can be given by its record (abduction, terror, a council bomb, a UFO). Clear map asks what the map is for.
A mission's objectsView options' Mission objects marks what the picked mission adds. Move one with its group, and the Build warns when an edit takes the floor from under one.
Enable savingA test battle you can save and load: XCOM opens at its main menu and F5 starts the battle.
Cover blocks of any sizeSized with the dots on their faces. The panel says what the game makes of a block smaller than a tile and what it does to line of sight.
BlockersA cover block with Cover None stops units walking there without giving cover.
Camera speeds and the centre pivotSliders for moving and turning speed in View options, and a Pivot button (C) on the tool strip to move and turn about the selection's centre.
New in 0.5.1What it is
Cache everythingSettings (the gear) reads every piece of the game's maps ahead of use, and every map if you ask, with a progress bar you can cancel.
30 levelsMaps, prefabs and their test stage go up to 30 levels high, where 18 was the limit.
The builder's Problems chipWhat Test in game would say of a prefab, without building it.
More is builtA piece the Build can't make is left out and listed, and the rest of the map is built. Pieces of a kind the Build had not made before are built too. Prefabs that are too big or hold odd light values are warned of, not refused.
A faster editorA large prefab opens in about a second instead of twenty, edits and pastes with many pieces are several times quicker, and slow steps show a bar.
New in 0.5.0What it is
Pieces from other mapsThe piece list's All maps: any piece of any map in your install, placed in the map you are editing. Favourites and recently used pieces are kept.
PrefabsA set of pieces, or a whole building with its lights, saved to be placed again in any map and passed on as a file. The prefab builder makes one from nothing, and Test in game plays it on a blank stage.
BuildingsThe Buildings view: floor boxes drawn over a building so its roof hides and its walls cut down in the game. The map's own buildings can be changed the same way.
Clear mapTakes every piece off a map, to build a new one on its light and landing.
Map gridThe play area resized by handles: larger and taller on any map, and any size once it is cleared.
Landing zonesWhere the squad lands, moved, turned, added and deleted in a view of their own, for Long War and for plain Enemy Within. Land here plays a zone.
Box selectA box drawn over the ground selects everything inside it.
Four viewsNormal, Buildings, Lights and Landing zones: each selects its own kind of thing only. The Normal view can show lights and floor boxes beside the pieces.
Groups in groupsA group can hold other groups, and lights and buildings too, so a house moves with its lamps and its floor boxes.
Cover blocks that breakA cover block grouped with a breakable piece goes when the piece is destroyed.
A copy by draggingHold Shift as you take a move handle to drag a copy.
What buildsDoors without a frame build now. A ladder that isn't expected to climb is warned of and built, where it used to stop the build.

Where things are

WhatWhere
SettingsDocuments\XCOM Map Workshop\settings.json
The test squadDocuments\XCOM Map Workshop\test-squad.json (beside the settings; the squad before the last save in test-squad.prev.json)
Projects<editor folder>\projects\ (one .json file each)
PrefabsBeside the projects by default, or the folder chosen in settings.json (one .json file each)
Builds<editor folder>\builds\
Map packs<editor folder>\builds\Map packs\ (the zips); what the editor remembers of each pack in <editor folder>\projects\packs\
Map picturesWith the projects, in their .workshop folder
Opened mapsDocuments\XCOM Map Workshop\cache\ (safe to delete: maps are read again when opened)
Build logs<editor folder>\builds\.work\<variant>-<time>\logs\
What Play in game installed<game folder>\XCOM Map Workshop\ (records and backups)

The editor folder is where the editor is installed (by default %LOCALAPPDATA%\Programs\XCOM Map Workshop), or where you unpacked the zip. Upgrading keeps your projects, builds and prefabs. The editor uses Documents\XCOM Map Workshop when the install folder is read-only and keeps existing data folders there available. Use Game install and checks… (under Settings) to see which folders are in use. With the zip, unpack a new version over the old folder, or move projects, builds and prefabs into the new one.

Problems, and removing it

If something seems wrong

Reporting a problem

Reports from any setup are welcome, plain Enemy Within included. Say which version you have: it is at the bottom of the ? menu, in VERSION.txt and in each build's manifest.json. After a build, or a failed or cancelled one, Save a bug report in the build window zips the project and the build's logs into the builds folder and copies the zip's path; click the path to see the zip in Windows Explorer. Send that zip with what you did and what you saw; a screenshot helps.

Removing the editor

  1. Choose Game maps… (the arrow beside Play), Undo everything first, if you played or installed a project in the game.
  2. Uninstall XCOM Map Workshop from Windows' Settings, Apps. If you used the zip, delete its folder.
  3. Uninstalling leaves your projects, builds and prefabs in the editor folder: delete it too if you don't need them. Documents\XCOM Map Workshop keeps the settings and the opened maps.