Your resort.
Your Ticket Office.

STEP 01

Open the source project

You need an existing map source folder containing custom-map.json. Create one with the editor map tutorial or the workshop’s New button.

Install or update the tools, close the game, then update its loader:

pipx install --force --index-url https://skieomap.emillon.fr/downloads/pypi/ skieo-custom-map
skieomod update
skieomod editor my-mountain

Replace my-mountain with your project folder, or run skieomod editor and select it with Open. Use skieomod setup for your first game installation. The tools and the installed Custom Map loader both need version 1.15 or later.

Checkpoint: the workshop shows your source terrain in 3D and the toolbar contains Triggers, Resources and Objects.

STEP 02

Which kind of model do you have?

STEP 03

Import and inspect the resource

Click the toolbar’s Resources icon, then Import…. Use Browse… to select the OBJ, set its resource ID, choose model, units and up axis, and add its licence or credit. Click Import.

Select the model in the library to check it in 3D. Right drag rotates it, middle drag moves the view and the wheel zooms. Correct scale or orientation in your model/export if needed, then import a revised resource with a new ID.

The workshop copies the file into Resources/Files/ and keeps its options in Resources/assets.json. Close the Resource Editor to return to your map.

Checkpoint: the imported model appears upright in the 3D resource preview.

STEP 04

Choose the Ticket Office mesh

Click Objects in the toolbar and select Ticket Office in the left list. Search for MeshComponent, select MeshComponent.StaticMesh, then click Choose resource…. Select your imported resource and click Use resource.

The map value becomes asset:ticket-office for the sample and appears in bold. The change is already applied to the project. Click Place on map and left-click the terrain to add a Ticket Office. Press Escape to stop placing, then click Save.

Reset to game default removes the override. The CSV records differences only. The same editor exposes game properties such as construction cost; enter only changes you want your map to apply.

Change one placed building

Version availability: the per-object property controls below require the prepared 1.16 release, which is awaiting publication. The current public download is 1.15.

Select its footprint or its entry in the workshop’s Objects in this map list. The properties panel shows Default name and Name. Enter Not Ticket Office to rename only that building. Its custom name becomes bold; Reset name makes it inherit the type’s name again.

Below, the Property / Default / This object table edits this instance’s game properties. Search for a property such as BaseCost, double-click its value, or select MeshComponent.StaticMesh and click Resource… to choose a model for only this office. Changes apply immediately and support Undo/Redo. Reset value removes the instance’s difference.

STEP 05

Build, then test a Ticket Office

Click Build, then Test. Build reads the resource library and object CSV, converts the OBJ to portable geometry and combines the result with your existing map script, graph/Lua triggers and compiled forest.

Click Play to start the editor’s own test instance, or reload that instance after rebuilding. Your ordinary game session stays separate. In this fresh map session, the Ticket Office you placed in the editor is created automatically on the final terrain. You can also place additional offices with the game’s building controls. Existing Ticket Offices in the loaded map and offices built later receive the override.

skieomod build my-mountain
skieomod test my-mountain
skieomod run my-mountain

The replacement remains attached to the original component, using its transform and material. Its original actor, construction behaviour and collision remain in use; the OBJ does not create a new collision shape. Keep the visual footprint close to the original building when collision matters. Overrides are restored when the map unloads.

The main terrain viewport previews relief, trees and labelled object footprints. The Resource Editor previews the OBJ; the actual placed building is inspected in the game.

Checkpoint: your map’s Ticket Office uses the selected model. Other maps and the game’s class defaults keep their normal values.

The source files behind the buttons

The workshop adds these project-relative build instructions to custom-map.json. You can author the same files manually and use the CLI; no separate converter is required.

"build": {
  "resources": { "file": "Resources/assets.json" },
  "objects": { "file": "Objects/overrides.csv" }
}

Merge these keys into your existing build object, retaining heightmap, forest and vegetation settings.

{
  "version": 1,
  "assets": [{
    "id": "ticket-office",
    "kind": "model",
    "file": "Resources/Files/ticket-office.obj",
    "units": "meters",
    "up_axis": "z",
    "license": "CC0 1.0"
  }]
}

The UTF-8 CSV uses the columns object,field,type,value. Values are JSON literals, quoted as required by CSV:

object,field,type,value
/Game/Blueprints/Buildings/BP_TicketOffice.BP_TicketOffice_C,MeshComponent.StaticMesh,model,"""asset:ticket-office"""

Build produces Scripts/skieomod-generated-authoring.lua and uses it as the packaged script entry. Your original script remains a source. Resource JSON, object CSV and OBJ authoring files stay in the project; runtime geometry is compiled into the package. Edit the sources and rebuild.

Common questions