Skip to content

Releases

XCOM Map Workshop 0.6.0 (preview)

Choose a tag to compare

@ruskyandrei ruskyandrei released this 19 Nov 18:53

An early preview: see the README for what you need and the user guide (in the release, and online at https://ruskyandrei.github.io/xcom-map-workshop/) for how it works.

Download XCOM-Map-Workshop-0.6.0-Setup.exe (recommended) or the zip. Windows SmartScreen may say "Windows protected your PC" because the installer isn't signed: choose More info, then Run anyway.

Upgrading from 0.5.3: install over it. Your projects, prefabs, builds and the maps you installed in the game are kept.

  • Each map is read from the game again the first time you open it (about half a minute), because the editor now reads the map's effects, sounds and spawn points. Cache everything… (now under Settings, the gear) with Every map, ready to open does them all at once.
  • A project saved in 0.6.0 can't be opened in 0.5.3, and neither can a prefab that holds effects, sounds or drawn pieces. If you pass one on, or a map pack with its project files, the other person needs 0.6.0 too.
  • The header changed (below): Build and Play are buttons now, and several items moved out of the Project menu.

New features

  • Draw your own walls, rooms, floors, roofs and ground. Hover Add on the tool strip for the new Build menu, pick a tool and drag it out in the view.
    • Walls and rooms: a wall of any length and height, with doorways and windows you add and drag by their handles. Room draws four joined walls with a doorway; Room with a roof adds the roof and a building around it, so the roof is cut away when the cursor is inside.
    • Floors and roofs of any size, a storey over where you press. They break in the game a piece at a time, as the game's own do.
    • Ground: a flat Patch to cover holes and paint the ground, a raised Block, a Ramp, and a Rock shaped by dragging its blue points.
    • Looks: a drawn piece starts plain. Choose… in the piece panel (or I) opens the look picker, with the look of every wall, floor, roof and ground of your game's maps; the eyedropper takes a look from a piece in the view.
    • Break and Repair: knock fragments out of a drawn wall, floor or roof, or out of one of the map's own breakable pieces, so the map starts the battle with the damage.
  • Effects and sounds: the new Effects view (Shift+X) shows the map's fires, smoke, steam, ambient sounds and lens flares. Move, copy and delete them, change an effect's size and particle settings and a sound's reach, volume and pitch, and add any effect or sound from the game's other maps. Effects are drawn in the view as a likeness of what the game shows. Prefabs keep theirs.
  • Spawn points: the new Spawns view (Shift+U) shows where the aliens' pods start, the Meld, the drop-in points and the mission's objectives. Move and copy pods and Meld points, move drop-in points, add new pods, Meld points and no-spawn volumes from the Add panel, and move an added bomb mission's objects. Under Long War, Scripted drop-ins land where placed keeps the mission's reinforcements at their own points.
  • Map picture… (Map menu): the picture the game shows for your map on its mission screens. Choose an image and frame it, or use Take from the view; the Build writes it into the map. Long War Rebalance 3 shows a map's own picture.
  • Map packs for Long War Rebalance 3: Export map pack in the project manager makes a drop-in pack: one folder copied into the game's CookedPCConsole, read by LWR 3.00.00 beta 15 or later, with no file of the game changed; delete the folder and it is gone. The pack's Install.cmd and Uninstall.cmd do the copying, and install the classic way on other installs. The editor remembers your packs, so exporting one again makes its next version.
  • Add to group puts the selected pieces into a group that is already there.

Changes

  • The header is sorted out. The Project menu held fifteen items; now:
    • Project: Save, Save as…, Open… (was Load…), Close project, your recent projects and Manage projects….
    • Map is a menu: Change map… (M), Missions…, Map picture…, Map grid and Clear map….
    • Build and Play are buttons at the right of the header. The arrow joined to Play has Test squad setup…, Game maps… and the installs the editor works with.
    • Settings (the gear): Game install and checks… and Cache everything….
    • Find a piece is gone, and Ctrl+F is your browser's own again.
  • The piece panel is tidier: icon buttons under the name, the piece's own settings first, and Group, Align, Flags, Place and Source each folding to one line. A section's ⓘ shows its how-to text.
  • A baked build keeps its lighting inside the map file. No .tfc file is built, installed or packed with it.
  • Clear map also deletes the map's pods, Meld points, drop-in points and ambient sounds, and counts them in its window. The Skyranger and its landing stay.
  • The user guide is in a new order: getting started and typical tasks first, then the reference in four parts.

Bugs fixed

  • A project on the small scout's farm map failed to build or play ("no DefaultMaps.ini record for CsmallScout_Farm"): the map's file and the game's records spell its name in different case.
  • A data recovery or covert extraction played with a SHIV first in the test squad never left its loading screen. The squad's first soldier or MEC trooper now goes to the front, and the play's notes say so.

Known limits

  • A roof or floor you break with Break takes no more damage in battle, as the game keeps its own broken ones, unless you tick Breaks further in battle on it.
  • The look picker draws its pictures the first time you open it, which takes a few minutes; after that they are kept.
  • A drop-in map pack needs Long War Rebalance 3.00.00 beta 15 or later. On older versions and on plain Enemy Within, a pack installs the classic way, by Install.cmd.
  • Tested mainly with Long War Rebalance through Steam. Plain Enemy Within is meant to work but is less tested. Reports from it, or from any other setup, are welcome: use Save a bug report in the Build window.

Checksums (SHA-256)

78b39cd9035973d9130e3a01a7d335d168fc84654a391638c1002f5028276e67  XCOM-Map-Workshop-0.6.0-Setup.exe
ce9baa24f5d3414056846cc1de5bc01240de12849f49d6f5162e548753318b96  XCOM-Map-Workshop-0.6.0.zip

XCOM Map Workshop 0.5.3 (preview)

Choose a tag to compare

@ruskyandrei ruskyandrei released this 17 Nov 12:32

An early preview: see the README for what you need and the user guide (in the release, and online at https://ruskyandrei.github.io/xcom-map-workshop/) for how it works.

Download XCOM-Map-Workshop-0.5.3-Setup.exe (recommended) or the zip. Windows SmartScreen may say "Windows protected your PC" because the installer isn't signed: choose More info, then Run anyway.

Upgrading from 0.5.2: install over it. Your projects, prefabs, builds and the maps you installed in the game are kept.

  • Each map is read from the game again the first time you open it (about half a minute), because the editor now reads each piece's flags and the map's tile grid from the game's own record. Cache everything… with Every map, ready to open does them all at once. Pieces from other maps are read again too, the first time each is used.
  • A project or prefab saved in 0.5.3 can't be opened in 0.5.2. If you pass one on, or a map pack with its project files, the other person needs 0.5.3 too.
  • Projects saved before keep the map names they had. Only new projects are named after the project (below).

New features

  • Piece flags: the piece panel's new Flags group turns on or off five things the game reads on a piece: Blocks walking, Gives cover, Blocks sight, Floor and Mouse picks it. A wall units walk and see through, a sign the mouse never picks, a fence that gives no cover.
    • A click changes every piece you picked, in one undo step; copies, pasted pieces and prefabs keep the flags, and Reset flags puts the map's back. A Flags chip marks a piece with one off or changed.
    • The Build writes them on the piece and works its tiles out again. A project with only flags builds without relighting.
  • Select all of a kind, beside Copy and Delete, selects every piece drawn with the same mesh, or only those inside a drawn box, so you can change them all at once.
  • Your own test squad: Settings (the gear in the header), then Test squad setup…, chooses the squad every Play in game lands with, for maps, projects, Land here and prefab tests.
    • Under Long War Rebalance: one to eight soldiers, MEC troopers and SHIVs, each with class, rank, armour, weapons, items, perks and stats from your install's own lists. On plain Enemy Within and Long War without Rebalance: soldiers only, six at most.
    • Each change is checked at once: errors stop a play, warnings say what the game will do. Export… and Import… share a squad as a file. Until you save one, it is the six squaddies as before.
  • Build in the project manager builds the ticked projects one after another, each a full build with its lighting baked, while you go on editing. A chip in the header shows how far it is, with Stop, Resume and Clear. If the editor closes mid-queue, the queue is kept, stopped, until you resume it.
  • The project manager, laid out again: your projects on the left, each with its last build in one word (Ready, Not baked, Out of date, Not built) and filters with counts; the ticked ones on the right, each with its own Additional or Replace and its warnings under it.
    • Export map pack (was Zip as a map pack) can Include editor project files, so whoever gets the pack can open and change the maps.
  • Maps named after their project: a new project builds as its own name, one word of up to 24 characters, shown under the name in Save and fixed once saved. Its baked lighting goes in <Map>_Lighting.tfc. A build or an install never replaces another project's files.
  • Maps up to 256 tiles a side in Map grid (128 before).

Changes

  • Each map's tile grid comes from the game's own record. The Battleship, Deluge and Furies have one for the first time, so edits that need it (moving a van, a building's floors, Map grid) build there, and the Battleship has its 15 levels.
  • The user guide is online at https://ruskyandrei.github.io/xcom-map-workshop/, as well as in the release. The online one can be ahead of the last release.

Bugs fixed

  • A project on Roadhouse that moved a van failed to build ("has no tile grid, which a van needs").
  • A map pack or install replacing Commercial Alley Redux left a new campaign unable to start its first mission. Your map now keeps the record name the first mission asks for. A map installed or packed this way with 0.5.2 needs installing or exporting again.
  • Replace took the original map away from missions your map isn't for. Now the original keeps the missions your project leaves out, and the warnings under Replace name them.
  • Map grid snapped back when dragged larger on a map already over 128 tiles a side, such as the Temple Ship.
  • An invisible floor placed with the snap off or fine could stand above or below the ground where the ground isn't flat.

Known limits

  • Blocks walking on a low piece (under 60 units over the bottom of its level, such as a hedge or a kerb) stops no one: the panel and the Build say so. A door with Blocks walking or Blocks sight off is walked or seen through even when shut.
  • A test battle is not a campaign mission: your test squad, four pods of Sectoids or EXALT, and no mission commander.
  • A new map starts from one of the game's, and only the game's own pieces can be used. Clear map empties it, but the sun, the time of day and the base missions stay the base map's. You can't import your own models, textures or sounds.
  • Tested mainly with Long War Rebalance through Steam. Plain Enemy Within is meant to work but is less tested. Reports from it, or from any other setup, are welcome: use Save a bug report in the Build window.

Checksums (SHA-256)

b56bab56ce1f78f59b07ee410a63e7f24c1349fb6121f8537dd949b0ef116f39  XCOM-Map-Workshop-0.5.3-Setup.exe
5307b161f950be7e65d3dbc5dda462ab087c194b7f03851b887abfd8781e6c35  XCOM-Map-Workshop-0.5.3.zip

XCOM Map Workshop 0.5.2 (preview)

Choose a tag to compare

@ruskyandrei ruskyandrei released this 15 Nov 18:52

An early preview: see the README for what you need and the user guide (in the release) for how it works.

Download XCOM-Map-Workshop-0.5.2-Setup.exe (recommended) or the zip. Windows SmartScreen may say "Windows protected your PC" because the installer isn't signed: choose More info, then Run anyway.

Upgrading from 0.5.1: install over it. Your projects, prefabs, builds and the maps you installed in the game are kept.

  • Each map is read from the game again the first time you open it (about half a minute), because the editor now reads each mission's objects. Cache everything… with Every map, ready to open does them all at once.
  • A project or prefab with cover blocks, saved in 0.5.2, can't be opened in 0.5.1: blocks are now stored by their size in units. If you pass one on, the other person needs 0.5.2 too.

New features

  • Play in game plays the mission you pick, not always an abduction: the header's Mission picker, or the play window's Mission select, chooses it. Under the choice a line says how far that kind is known to work played this way.
    • Played and working under Long War Rebalance: abduction, council bomb, council rescue, terror site, crashed UFO, base defence, the alien base and data recovery.
    • The enemies are four pods of Sectoids (five on a terror site). EXALT's missions get four pods of EXALT operatives, each with a heavy or a sniper.
  • Missions… (Project menu) chooses which of the base map's missions your project is for, and can give a map more through its record: an abduction, a terror site, a council bomb (Long War) or a crashed or landed UFO (on a map with a UFO building). Clear map then asks What is this map for?
  • A mission's objects in the view: View options' Mission objects marks what the picked mission adds: drop-in points, pods, your soldiers' points, the operative, VIPs, capture points, radar arrays, the bomb and its power nodes. A click says what each is and what it moves with.
    • Move one with its group by its arrows, in whole tiles and levels. The Build moves it in a copy of that mission's files.
    • The Build warns when an edit takes the floor from under a mission's objects, and the Build window lists them by mission.
  • Enable saving: tick it in the play window, in Build and test, or in the tab on a finished build's Play in game. XCOM then opens at its main menu, F5 there starts the battle, and you can save and load in it. It is always on for EXALT's missions under Long War, which saves and reloads them as they start.
  • Cover blocks of any size: drag the white dots on a block's faces. The steps follow the snap setting (off, 24 units, whole tiles), and the top and bottom move too. The panel says what the game makes of a block smaller than a tile, and what the block does to line of sight. A thin block on a tile's edge acts as an invisible wall (played).
  • Blockers: a cover block with Cover: None (blocks walking) stops units walking there without giving cover. It is drawn purple.
  • Camera speeds: View options' Camera section has sliders for Move speed, Key turn speed and Drag turn speed. They are remembered, and a double-click puts one back.
  • Pivot (tool strip, C): move and turn about the selection's centre instead of each piece's own origin.

Changes

  • The prefab builder's Test in game has Bake the lighting off by default, like the map's Build.
  • A build keeps the names the game looks for in its missions: a bomb mission's record keeps _Bomb, so Long War still sends its reinforcements as for a bomb, and the Temple Ship's keeps TempleShip. A map the game knows by its whole name gets a note.
  • Text in the page no longer gets selected when you drag. Piece details, logs and messages still can be.
  • The editor now says the original map for the map from the game's files with none of your edits.

Bugs fixed

  • Deluge (Progeny 2) couldn't be opened ("Could not open scene: Invalid array length"): one of its lights reaches millions of units out.
  • Street Hurricane Terror's dropship landed in the middle of the map. The game's own intro gives it no place; a build now lands it at the map's grounded Skyranger. The original map, played as the game has it, keeps the fault.
  • A terror play hung at the loading screen. The civilians now get their looks.
  • Shift didn't speed up a camera move already under way.

Known limits

  • Not played in the game yet: missions added through Missions…, moved mission objects, the other mission kinds (landed UFO, council assault and extraction, covert extraction, the EXALT raid, the final and story missions), and some of 0.5.1's additions (maps and prefabs over 18 levels, builds with pieces left out). They build without errors; please report how they play, with Save a bug report from the Build window.
  • A test battle is not a campaign mission: a fixed squad of six, Sectoid or EXALT pods, and no mission commander.
  • A new map starts from one of the game's, and only the game's own pieces can be used. Clear map empties it, but the sun, the time of day and the base missions stay the base map's. You can't import your own models, textures or sounds.
  • Tried with Long War Rebalance through Steam. Plain Enemy Within is a best guess, and other Long War versions and game folders outside Steam haven't been tried.

Checksums (SHA-256)

418855ed414d7c1a057a0aeefd1a73d1d9b25e6674fd46ce1083217bcbf55dce  XCOM-Map-Workshop-0.5.2-Setup.exe
98df06875776d78fe65e6989a9bc27d0e5561b6e9b9f76bb8d2c11e8b4b41ee8  XCOM-Map-Workshop-0.5.2.zip

XCOM Map Workshop 0.5.1 (preview)

Choose a tag to compare

@ruskyandrei ruskyandrei released this 14 Nov 14:08

An early preview: see the README for what you need and the user guide (in the release) for how it works.

Download XCOM-Map-Workshop-0.5.1-Setup.exe (recommended) or the zip. Windows SmartScreen may say "Windows protected your PC" because the installer isn't signed: choose More info, then Run anyway.

Upgrading from 0.5.0: install over it. Your projects, prefabs, builds and the maps you installed in the game are kept, and no map has to be read from the game again.

  • A prefab or project taller than 18 levels, or a building with more than 8 floors, can't be opened in 0.5.0. If you pass one on, the other person needs 0.5.1 too.

New features

  • Cache everything… (Project menu) reads every piece of the game's maps into the editor's cache now, so placing a piece of another map or opening a prefab never waits for it. Tick Every map, ready to open to prepare every map as well.
    • The window says how many there are, about how long it takes and how much disk space it needs (here about 10 minutes and 6.4 GB for the pieces of 116 maps), with the drive's free space.
    • It runs in the background with a progress bar: keep working, close the window and open it again later. Cancel stops it at any moment, what was read so far stays, and Carry on picks up from there.
  • 30 levels. Maps (Map grid), prefabs and the prefab test's stage go up to 30 levels high (1,920 units), where 18 was the limit. The cursor gets up to ten storeys and a building up to ten floors. Over 18 levels, the height of the game's tallest maps, the editor says "not played".
  • The prefab builder's Problems chip, under the size line: what Test in game would say of the prefab as it stands, without building it (how many pieces would be left out, how many warnings). A row selects and frames its piece. It is checked when you open and save the prefab, and by Check again.

Changes

  • More is built. Where the Build or the prefab test used to stop, it now builds what it can and says what it couldn't:
    • A piece the Build can't make is left out, and the rest of the map is built. The Build window lists the pieces left out, and a row selects its piece. A project whose every edit is left out says so.
    • Pieces the editor hadn't let through are built with a warning: pieces of a kind the Build hasn't made before (marked Untried), a single part of a car or a door edited on its own, a tinted copy (built without its tint), and pieces of other maps the library used to hold back. If one of them makes the Build fail, they are taken out, the rest is built, and the window names them.
    • Light values out of range are built at the nearest value in range, with a warning. A piece edited whose glow can't follow it is built, with a warning, and the glow stays where it was.
  • The prefab test follows the Build's rules.
    • A piece off the grid is a warning, not an error, and a rotation rounded to what the game stores no longer stops it.
    • A piece whose source can't be found or read is left out and named, and the test waits for Launch test so you can decide.
    • When the map a prefab's pieces came from has changed since the prefab was made (a game update, another install), its pieces are looked up by what they are, with a warning.
    • The stage is as tall as the prefab needs, 18 to 30 levels.
  • Prefabs from elsewhere open more often:
    • a prefab larger than a map holds is saved and placed, with a warning;
    • one placed where it reaches out of the map's grid is placed, with a notice;
    • a field this editor doesn't know is kept, and named on the prefab's card.
  • Warnings only for what can cause a problem in the game. What can't (loot counts, how pieces will look, the cutaway's details, unchanged edits) is no longer listed among the warnings, and the prefab test lists warnings only. A piece sunk into the ground no longer counts as outside the grid.
  • A building's floors: which pieces belong to a floor of a building you draw or change now skips pieces that collide with nothing (lamps, wires, decoration), which matches how the game's own maps are listed more closely.
  • A faster editor, measured on Forest Grove with a 460-piece Landed Large UFO prefab:
    • opening the prefab in the builder: about a second, from 20 seconds;
    • checking it: just over a second, from 16;
    • each edit in the builder: 9–15 ms, from 50–85;
    • pasting 500 pieces: under a tenth of a second, from 1.3 s;
    • drawing the map: the sun's shadows are drawn again when something changes (and once a second), not every frame.
  • A visible busy state: opening a prefab or a project counts on the loading screen, placing and pasting count the pieces, and deleting, undoing or redoing 60 pieces or more shows a busy mark with a bar.
  • The Build panel and the guide give a baked build's time as about a minute or two for a small edit (they still said several minutes).

Bugs fixed

  • The Small Landed UFO prefab showed its roof on floor 1. Some of the game's maps list which pieces belong to which floor by hand (the UFO's roof is one), and those lists were lost as soon as the building's floor boxes were moved or changed, in a prefab or in a project. They are carried through such edits now.
  • A prefab with spot lights copied from a map failed its test with "outerConeAngle must be 0 to 89.99". Some maps store a spot light's cone wider than the game uses (the UFO maps' blue lights store 100). The editor now stores the cone the game lights it as (89.99), so it looks the same. A prefab saved before tests as it is, and is corrected the next time it is saved.
  • Copies of some pieces were refused because their mesh sits off the piece's own centre (a fence in the Landed Large UFO). Such a copy now keeps the offset and is built.

Known limits

  • Not played in the game yet: what 0.5.1 adds (maps and prefabs over 18 levels, builds with pieces left out, pieces built with the Untried warning) and the faster bake's lighting from 0.5.0. They build without errors; please report how they play, with Save a bug report from the Build panel.
  • A new map starts from one of the game's. Clear map empties it, but the sun, the time of day and the mission stay the base map's.
  • Only the game's own pieces: you can't import your own models, textures or sounds.
  • Tried with Long War Rebalance through Steam. Plain Enemy Within is a best guess, and other Long War versions and game folders outside Steam haven't been tried.

Checksums (SHA-256)

fc7e7c7a8265fb344d0237278aac92022d11cd5ada2d10366702d4bb32a28fed  XCOM-Map-Workshop-0.5.1-Setup.exe
0ba65ffd7e903fa2ccbb62762a9a3f3892da25f5d895af33dfed167145d8085a  XCOM-Map-Workshop-0.5.1.zip

XCOM Map Workshop 0.5.0 (preview)

Choose a tag to compare

@ruskyandrei ruskyandrei released this 13 Nov 21:44

An early preview: see the README for what you need and the user guide (in the release) for how it works.

Download XCOM-Map-Workshop-0.5.0-Setup.exe (recommended) or the zip. Windows SmartScreen may say "Windows protected your PC" because the installer isn't signed: choose More info, then Run anyway.

Upgrading from 0.4.1: install over it. Your projects, builds and the maps you installed in the game are kept. Two things happen by themselves:

  • Each map is read from the game again the first time you open it (about half a minute), because the editor now takes more from each map: its buildings, its landing zones, its storeys. The page says "Map schema updated. Re-exporting." and carries on.
  • Old copies of opened maps are deleted when the editor starts, and after each map it reads again, keeping only the newest of each map. Here that freed 11 GB of 14. Projects saved on an older copy build from the newest one, and saving a project moves it onto the copy it was edited on.
  • Old build work folders are cleared by the first Build. Each project keeps its three newest whole, and only the logs and small records of older ones. Here that freed about 4.5 GB.

Faster baked builds

Builds with Bake the lighting ticked are three to four times faster, and faster again when a project is built a second time.

  • The Temple Ship project here took about 10 minutes to build before. It now takes under 3 minutes on a fresh bake, and under 2 minutes when built again after a small change. Edits on the Bar went from 2½–5 minutes to between 40 seconds and 1½ minutes.
  • Quick builds (Bake the lighting off) take a few seconds instead of up to a minute.
  • How:
    • each package is decoded once and kept for the next build;
    • a large piece is split up and relit by several workers at once, the largest first;
    • a light is worked out only where it reaches;
    • only the parts of a piece that the edit can change are relit.
  • Each project keeps its relit pieces, so building it again after a change relights only what that change can reach.
  • More of the game's own lighting is kept as it was:
    • a piece whose light changes by less than a small amount is left alone;
    • a piece keeps its lightmap's original scale where the new light fits under it;
    • the parts of a lightmap that no edit touches stay as they were;
    • the edges around each lightmap are written along with it.

New features

  • Pieces from other maps. The piece list (P) has All maps: every piece of every map your install plays, to place in the map you are editing. The game's maps are read once (about half a minute), and the list can be filtered, sorted (most used, recently used and more) and starred.
    • Destructible props, collectibles, fracturing pieces, physics props, doors, ladders, cars, vans and prefab pieces all come across. A car, a door with its frame or a van with its building is one entry, brought whole and placed as one.
    • Pieces brought from another map are lit by a baked build like the map's own.
  • Prefabs. A set of pieces, or a whole building with its lights, saved to place again in any map and passed on as a file (Add a piece → Prefabs).
    • The prefab builder (Prefabs → New) makes one from nothing, on a blank workspace.
    • Test in game in the builder plays the prefab on a lit stage, with no aliens.
    • A prefab whose pieces your install lacks is opened with a warning, and Find missing pieces looks for them again after All maps has been read.
  • Buildings. The Buildings view (Shift+B) draws the floor boxes that make a roof hide and the walls cut down in the game as the cursor goes up and down the storeys.
    • Draw them over a house you put together, storey by storey, so the game treats it as a building.
    • The map's own buildings can be changed the same way: moved, made larger or smaller, given storeys, or deleted.
    • A building moves with its pieces when they are grouped, and a map building copied with its pieces brings its floor boxes along.
  • Clear map (Project menu) takes every piece off a map, to build a new one on its light, sky and landing. It can keep the scenery outside the play area.
  • Map grid (tool strip) resizes the play area by its handles: larger and taller on any map, and any size, smaller too, once the map is cleared. On a grown map the new storeys get the cursor's floors, and the scenery in the new area is walkable.
  • Landing zones. Where the squad lands, in a view of its own (Shift+Z): move and turn a zone with its gizmo, add one from the Add panel, delete one, and set which game uses it (Long War, plain Enemy Within or both).
    • Land here plays a battle with the squad on that zone.
    • Maps with no drop zone frame (Basic Training, the Temple Ship, the alien bases) have their landing as a zone too.
    • A moved Skyranger takes its shadow with it in a baked build.
  • Box select (T): a box drawn over the ground selects everything inside it.
  • Four views: Normal, Buildings, Lights and Landing zones (Shift+N, Shift+B, Shift+L, Shift+Z). Each picks only its own kind of thing; the Normal view can show lights and floor boxes beside the pieces.
  • Groups in groups, and groups that hold lights and buildings, so a house moves with its lamps and its floor boxes.
  • Cover blocks that break: a cover block grouped with a breakable piece, with Break together in the game ticked, goes when the piece is destroyed, so it leaves no invisible wall.
  • A copy by dragging: hold Shift as you take a move handle, and a copy is dragged off while the original stays.

Changes

  • 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. Now built with a warning, where the Build used to stop:
    • a ladder that isn't expected to climb (it is built without a climb of its own);
    • moving or deleting a piece the mission script uses, or one of the landing's own pieces (move the landing zone instead);
    • deleting a piece of a kind the editor can't otherwise build, such as merged scenery.
  • Doors without a frame build. They haven't been played in the game yet.
  • A ladder's check counts the floors your project adds (walls and storeys you built, invisible floors, a grown grid's levels), in the editor and in the Build.
  • The header's change count includes buildings, a resized grid, landing zones and a cleared map, and Reset all puts them all back.
  • The user guide has a New in this version section, new sections for prefabs, buildings, Clear map, Map grid, landing zones, and cover blocks and invisible floors, five new typical tasks, and its pictures taken again. What it can't do yet is rewritten to what holds now.

Bugs fixed

  • A project saved after the editor had read its map again kept building from the older copy, so it missed what the newer one adds. Saving now moves the project onto the copy it was edited on.
  • The opened maps' folder kept every older copy of each map, about 150 MB a map for each version of the editor. Old copies are deleted now (see Upgrading).
  • The builds folder kept every build's work folder, several GB after a few weeks of baked builds. Old ones are cleared now (see Upgrading).
  • If one of the bake's workers died, the Build could wait forever. It now stops, and names the pieces that were left.
  • A baked build's progress now counts pieces as they finish, so it no longer sits still while large pieces are relit.

Known limits

  • Played once or twice in the game: pieces from other maps, prefabs and their test stage, buildings made from nothing, the map's own buildings changed, a cleared map with its own landing zones, cover blocks that break with their group.
  • Built, but not played yet: doors without a frame; a map grown larger or taller as it is; Clear map with the scenery outside kept; a landing moved on a map with no drop zone (Basic Training, the Temple Ship, the alien bases); the moved Skyranger's shadow; a ladder built with the warning that it isn't expected to climb; a building marked UFO; landing zones on plain Enemy Within. These build without errors. Reports of how any of them plays are very welcome.
  • The faster bake's lighting hasn't been played in the game yet. It matches the old bake byte for byte when told to work as before, and the tests compare the new way with it, but no one has played a map baked the new way. Please report anything that looks lit wrong, with Save a bug report from the Build panel.
  • A new map starts from one of the game's. Clear map empties it, but the sun, the time of day and the mission stay the base map's.
  • Only the game's own pieces: you can't import your own models, textures or sounds.
  • Maps installed for campaigns haven't been played in a campaign yet, and only abductions have been played with an edited map.
  • Council missions can be replaced but not added to: install a map to replace the original to play it there.
  • Long War Rebalance's invisible cover stays where it was when the piece it covers moves, and a mission's own pieces (the data recovery's encoder) can't be moved.
  • The test battle is a plain one with six squaddies, not a campaign mission.
  • Tried with Long War Rebalance through Steam. Plain Enemy Within is a best guess, and other Long War versions and game folders outside Steam haven't been tried.

Checksums (SHA-256)

a1c8497fb3bcca455f30a6df141eb923fd0f26f5a2afc147c475fdb2fc46cd20  XCOM-Map-Workshop-0.5.0-Setup.exe
a5177c53c8123635e68ca7c185c99924e776bb42b4986b0c5c87e12088a7f94b  XCOM-Map-Workshop-0.5.0.zip

XCOM Map Workshop 0.4.1 (preview)

Choose a tag to compare

@ruskyandrei ruskyandrei released this 11 Nov 03:00

An early preview: see the README for what you need and the user guide (in the release) for how it works.

Download XCOM-Map-Workshop-0.4.1-Setup.exe (recommended) or the zip. Windows SmartScreen may say "Windows protected your PC" because the installer isn't signed: choose More info, then Run anyway.

Upgrading from 0.4.0: install over it. Your projects and builds are kept, and maps don't need preparing again. Two things change by themselves:

  • What earlier plays left in your game (the map records, landing zones and files of builds you played) is taken out the first time the editor opens with XCOM closed. Your builds are untouched, and playing one puts it back in for that play.
  • Remove from game has moved: it is now Undo everything in the new Game maps window (Project menu).

New features

  • Project manager (Project menu, Manage projects…): every project with its last build (when it was built, of which revision, whether its lighting is baked, and the editor version that built it) and what is in the game of it.
    • Filter by text or by state, sort by any column, and tick projects one by one, as a Shift+click run, or all that the filter shows (Ctrl+A).
  • Install maps for campaigns. Until now a build could only be played in a test battle. The manager's Install in the game puts the ticked projects' builds into the game's map list so that campaign missions use them, one of two ways:
    • Additional maps: your map joins the rotation beside the original, and missions draw from both.
    • Replace the original maps: your map is used where the original was. The original's records are commented out, not deleted, and come back when you undo it. This also covers council missions, which ask for their map by name.
    • Each row's Install as gives that project its own way, so one install can replace some maps and add others.
    • The manager warns, without stopping you, about a build whose lighting isn't baked, a build older than its project, and maps that serve missions other than abductions.
  • Map packs. Zip as a map pack makes one zip of the ticked builds to hand to other players, who don't need the editor:
    • Install.cmd asks for their game folder (it offers the Steam install it finds), keeps a copy of DefaultMaps.ini as it is, copies the files and adds the maps, replacing or adding as you chose for each.
    • Uninstall.cmd takes the pack out again and says whether DefaultMaps.ini is exactly as it was.
    • The zip's README also lists every line, to add by hand.
  • Game maps (Project menu, Game maps…): every map record the game has, by map or by mission, saying whether missions draw it from the rotation or ask for it by name, and what the editor did to it.
    • Untick a record of the game's own and the game stops using it; tick it to bring it back. Switch off the shown and Switch on the shown do it for everything the filter shows.
    • A map replaced by one of your projects says by which. Each record the editor added has Undo, which takes that project out and brings back the map it replaced.
    • Undo everything takes all of the editor's back out of the game: the config files end exactly as they were.

Changes

  • Play in game leaves nothing behind. What a play installs is taken out again once XCOM has closed (or the next time the editor opens, if it was closed meanwhile). Maps installed through the project manager stay. A tactical save made during a test battle on a build won't load afterwards.
  • Remove from game is gone from the Project menu: Game maps' Undo everything does the same, and its Undo takes out one project.
  • The user guide has a section for the project manager and one for Game maps, and its Project menu picture shows the new items.

Bugs fixed

  • A build stopped with "the hidden piece at … crosses no tile of the map" when a deleted, copied or cover piece stood outside the map's playable tiles, such as the backdrop pieces round Basic Training (a tester's build report: thank you).

Known limits

  • Maps installed for campaigns haven't been played in a campaign yet. Installing, replacing and undoing are checked on the game's files, down to the byte, but not yet in the game: whether a campaign draws an added map, stops drawing a replaced one, and plays a replaced council mission's map is still to be confirmed. Only abductions have been played with an edited map. Please report what you see.
  • Council missions can be replaced but not added to. The game has a fixed list of council missions, each tied to one map by name, so a map installed as additional is never picked for one (it still joins the rotation for its other missions). Install it to replace the original to play it there. The one exception: Long War turns an extra bomb map into an extra bomb mission, so an additional map on a bomb map should appear as one (not played yet).
  • A map pack's lines copy the records of the install it was made from. A game with other records for those maps (another Long War version, plain Enemy Within) gets yours; a map whose base map that game doesn't have is left out. The scripts were tried on Long War Rebalance only.
  • Undoing one project in Game maps leaves its files in the game until Undo everything.
  • A first-mission install made by a version before 0.3.0 is put back at the next Play in game or by Undo everything, not by the automatic clean-up.
  • Tried with Long War Rebalance through Steam. Plain Enemy Within, other Long War versions and game folders outside Steam haven't been tried.
  • The test battle is a plain one with six squaddies, not a campaign mission.
  • A cover block gives no cover to a soldier standing on a slope (the game's rule), though it still blocks movement there. Ragdolls and debris pass through blocks.
  • Pieces moved off the grid build with a warning, but haven't been played in the game yet. A ladder off the grid climbs from the tiles its ends fall in.

Checksums (SHA-256)

cf1630de4361696744b4da59d01101aa22c30fc0a967bab8d91d6e4341d45918  XCOM-Map-Workshop-0.4.1-Setup.exe
59d5707f79caf3a56d02b1e79244791cd303432dfe61d6b41899f5a998ce8141  XCOM-Map-Workshop-0.4.1.zip

XCOM Map Workshop 0.4.0 (preview)

Choose a tag to compare

@ruskyandrei ruskyandrei released this 10 Nov 18:31

An early preview: see the README for what you need and the user guide (in the release) for how it works.

Download XCOM-Map-Workshop-0.4.0-Setup.exe (recommended) or the zip. Windows SmartScreen may say "Windows protected your PC" because the installer isn't signed: choose More info, then Run anyway.

Upgrading from 0.3.x: install over it. Your projects and builds are kept. Each map you prepared before re-exports by itself the first time you open it ("Map schema updated. Re-exporting.", 10 to 30 seconds), so that the fixes below show. Some keyboard shortcuts have moved (see Changes).

New features

  • Invisible pieces in the Add panel (kind Invisible). The editor builds them itself, so they work on any install, with no Long War files needed.
    • Cover block: an invisible box that gives high or low cover and blocks movement. You can set its width and length (1 to 16 tiles each way) and its height.
    • Invisible floor: thin plates, one per tile, that soldiers can stand on, ignored for cover. Use one to make a walkable spot where the game finds no floor. It is placed on the ground. Its panel shows how high it stands over the ground at each tile, and Fit to ground puts it just over the ground as the game sees it (its collision, not the drawn mesh).
  • Basic Training (Act1_IntroLevel, the tutorial's map) is in the map browser under Abduction. You can edit it, build it and play it.
  • Camera keys:
    • WASD moves the camera like the arrow keys, and Q and E turn the view.
    • View options has a new Keys move along the view setting. With it on, forward and back follow the way the camera faces, and a left-drag looks round from where the camera stands instead of orbiting.
  • Play area: the map's playable bounds show as faint amber walls. B, or View options' Play area, hides and shows them.
  • Play in game in the build window: once a build finishes, its window has a Play in game button that installs the build and starts the battle on it.
  • Maps update themselves: a map prepared by an earlier version re-exports when you open it.

Changes

  • Shortcuts moved to make room for WASD and Q/E:
    • Move is G (was W).
    • Rotate is R (was E). While placing a piece, R still turns it.
    • The Add panel's piece list is P (was A).
    • Solo is O (was S).
    • World or local axes is X (was Q).
  • One camera speed: the camera keys move at the same speed on every map and at every zoom, about 52 tiles a second (Shift for three times that). It used to follow the zoom, so it was very fast on big maps.
  • No snapping limits: with snap off, any piece moves and turns freely, including ladders, doors, cars, vans and fracturing walls and floors. An Off the grid chip warns when such a piece is off its grid. Tile snap still keeps them on it.
  • Wheel zoom: the mouse wheel zooms towards what is under the cursor.
  • Interior draws a piece that reaches into the area whole, instead of slicing it off at the edge (a car across the edge now shows entire).

Bugs fixed

  • Some props drew as see-through glass or with holes: the Farm's tractors, dairy tanks and pipes, and a barn lamp. Masked materials now use their real cut-out mask (maps re-export to pick this up).
  • Zooming in barely moved on big maps once you were zoomed in away from the map's centre.
  • On some maps, a full build stopped with "Texture has no own 8-byte TextureFileCacheName" (seen on Street Overpass with copied pieces).
  • A full build of DLC1_1_LowFriends stopped while relighting (a tester's bug report: thank you).
  • Variants of the alien bases (AlienBase01, AlienBase02) stuck in the entrance cutscene, so the battle never started. AlienBase02 hasn't been played since the fix.
  • The getting-started notes' line on plain Enemy Within no longer mentions the old first-mission install.

Known limits

  • Tried with Long War Rebalance through Steam. Plain Enemy Within, other Long War versions and game folders outside Steam haven't been tried.
  • The test battle is a plain one with six squaddies, not a campaign mission.
  • A cover block gives no cover to a soldier standing on a slope (the game's rule), though it still blocks movement there. Ragdolls and debris pass through blocks.
  • Pieces moved off the grid build with a warning, but haven't been played in the game yet. A ladder off the grid climbs from the tiles its ends fall in.

Checksums (SHA-256)

144b047a81955043bb1174e74a726f97960337bb0c974ff8a91a43d118d1370a  XCOM-Map-Workshop-0.4.0-Setup.exe
3028dbf699e8e467026f815cad8f1ac942decd4cc4b1b547984f23fe94efd342  XCOM-Map-Workshop-0.4.0.zip

XCOM Map Workshop 0.3.1 (preview)

Choose a tag to compare

@ruskyandrei ruskyandrei released this 10 Nov 01:57

The first release on this page. An early preview: see the README for what you need and the user guide (in the release) for how it works.

Download XCOM-Map-Workshop-0.3.1-Setup.exe (recommended) or the zip. Windows SmartScreen may say "Windows protected your PC" because the installer isn't signed: choose More info, then Run anyway.

In this version

  • Play in game: starts the game straight in a battle on your variant (or on any of the game's maps), through Steam, with no campaign to start. Nothing of the game's own is changed; Remove from game takes everything back out.
  • A map that needs preparing again asks in a dialog in the middle of the window, and a build that failed for that reason offers Prepare the map.
  • Projects and builds are kept in the editor's own folder; an upgrade keeps them. (Projects an earlier preview left in Documents stay there.)
  • A build is its folder (the map files and a README with the config lines); no zip beside it.
  • In the build window, the build's folder and a bug report's zip open in Windows Explorer when clicked.

Known limits

  • Tried with Long War Rebalance through Steam. Plain Enemy Within, other Long War versions and game folders outside Steam haven't been tried.
  • The test battle is a plain one with six squaddies, not a campaign mission.

Checksums (SHA-256)

72ab4a85c9e9485e8e54c0a6e7a6256ca835905fc52c92a34d39ffe00fa516ba  XCOM-Map-Workshop-0.3.1-Setup.exe
398fcbae50a00c10ec7b08cf5defaa677db5a6d5c5fbc9ef3704183f7769e0e7  XCOM-Map-Workshop-0.3.1.zip