MCM1 SX Plugin File Formats

Version 1.0 (Beta) - 7/9/26

This document describes the plugin-side files used by MCM1 Plugin Editor and TrackEdit-style construction sets:

Examples use the checked-in classic plugin:

General Text Rules

Plugin files are INI-like text files.

Plugin Scheme

A TrackEdit installation is expected to have this shape:

The selected plugins.ini tells MCM1 Plugin Editor where the TrackEdit root is. From there, the editor loads construction-set INI files from plugins/, construction-set assets from plugins/<set name>/, and normal tracks from tracks/.


plugins.ini Format

FORMAT BANNER: plugins.ini

Registry file listing the construction sets available to TrackEdit and the editor. Example: plugins/plugins.ini.

The file has one required section:

Keys

TotalConstructionSets

Number of Set_N entries expected in the file.

Set_N

Construction-set base name. The editor resolves Set_1=classic to:

Do not include .ini in Set_N; the track file uses Plugin=classic.ini, but plugins.ini uses the base name classic.


Construction-Set xxxx.ini Format

FORMAT BANNER: xxxx.ini

Definition for one construction-set plugin. Example: plugins/classic.ini.

Each construction-set file contains one [ThisConstructionSet] section and one [TrackPiece_NN] section for each piece.

[ThisConstructionSet]

Classic example:

TotalConstructionSetPieces

Number of [TrackPiece_NN] sections.

Description

Human-readable plugin name shown by the editor.

SampleBitmap

Preview image in the plugin asset folder. Classic uses plugins/classic/example.bmp.

DefaultConstructionPiece

Piece id used to fill empty or new tracks. Classic uses piece 1, the default terrain perimeter piece.

StartFinishPiece

Piece id that marks the start cell and race direction. Classic uses piece 12.

[TrackPiece_NN]

Classic piece 02 is a straight:

Track Piece Keys

ToolTipText

Piece display name in the editor.

StatBarText

Longer description for the piece.

GeometryNorth, GeometryWest, GeometrySouth, GeometryEast

ASC geometry files for each orientation. These must resolve inside the plugin asset folder unless a relative path points elsewhere. Classic straight pieces use StrNS.asc for north/south and StrEW.asc for west/east.

TextureMapNorth, TextureMapWest, TextureMapSouth, TextureMapEast

TGA texture maps for each orientation. The editor uses these to build the .ter terrain palette.

ToolbarIconUp, ToolbarIconDown

BMP toolbar icons for TrackEdit. The editor preserves and displays these asset references where available.

BitmapNorth, BitmapWest, BitmapSouth, BitmapEast

BMP construction-grid preview images for each orientation.

Connectivity

Cardinal ports for the north-oriented piece. Values are made from N, S, E, and W. The DAT writer rotates connectivity by the placed orientation when it traces the race route.

Classic examples:

PieceConnectivityMeaning
TrackPiece_02 Straight AwayNSconnects north/south
TrackPiece_08 90 Degree TurnSEconnects south/east
TrackPiece_01 Default TerrainNSEWavailable on all sides, but not a race piece

PieceType

Numeric behavior used by TrackEdit and the editor's DAT writer:

ValueMeaning
0generic flat
1straight away
290 degree turn left
3takeoff ramp
4landing ramp
5whoops
6table top
790 degree turn right
8left or right turn, resolved to 2 or 7 in DAT output
9obstacle

PieceType=0 and PieceType=9 are treated as non-racing cells by the current DAT writer.

NumberMapOrientations

Controls texture handling in generated .ter files.

RandomOrientation

TrackEdit flag for randomizing orientation when terrain is written. The editor preserves the value in plugin files.


Plugin Asset Folder

FORMAT BANNER: plugin asset folder

Asset directory paired with a construction-set INI. Example: plugins/classic/.

The asset folder name normally matches the construction-set base name:

Classic assets include:

Asset Roles

ASC files define the 16 x 16 elevation mesh for a construction tile.

TGA files define the terrain texture maps used by MakeTerr.

BMP files define editor and TrackEdit UI previews.

The .trk file stores only piece ids and orientations. For example, tracks/classic_test.trk starts with:

When the editor builds that track, it combines:

to generate the track-side .ter, .scn, and .dat files.