Importing community maps

Community maps arrive as archives of any shape: folders inside folders, pictures, documents, readmes in three languages. drahtseilakt-toolbox import-maps DIR sorts an unpacked download into levels/user-levels/ the way the game lists it: one folder per map, its .nmo, its picture as preview.jpg or .png, and a level.txt saying where it came from.

drahtseilakt-toolbox import-maps ~/Downloads/maps --catalogue CustomMapList.md

With the community catalogue

With --catalogue (the community’s BallanceCustomMaps list), each map is looked up by its file’s and folder’s name — case, punctuation, full-width characters and “v1.0”/“V1.0” do not matter — and gets its English title, its original (often Chinese) title, its author and its difficulty (the catalogue’s 1–5 doubled to the game’s 1–10).

What is set aside

  • A map neither in the catalogue nor with a readme beside it, and packed archives, go into an unsorted folder with a README.txt saying why — to look at by hand.
  • Sets of modified originals (45-degree, reversed, invisible…) go into levels/modified/<Set>/.
  • The same file found twice becomes one level; names are made safe for every system.

import-maps --refresh DIR --catalogue FILE [--source DIR] brings an already imported folder up to a newer catalogue in place. Links are never followed, the source is only read, and every level is written into a hidden folder first and renamed into place.

The check

After the import the toolbox asks the game (drahtseilakt beside it or on the PATH) to try each map, and keeps the verdict beside it as report.txt: plays fully, plays with differences, may not be passable, or does not load. The game shows it in the list of your levels. Without the game at hand the maps are still imported; run drahtseilakt --audit-report DIR later.