LE-CODE/Distribution FAQ

LE-CODE

LE-CODE & related file formats

• LE-CODE: General description
• LE-CODE: History
• LE-CODE: FAQ for track creators
• LE-CODE: Distribution Tutorial
• LE-CODE: Definition file for distributions
• LE-CODE: FAQ for distribution creators
• LE-CODE: Item Cheat
• LE-CODE: Controllers & Buttons
• LE-CODE: Slot usage
• LE-CODE: Exception Handler
• LPAR: File format for parameters
• LEX: File format and definitions
• LTA: LE-CODE Track Archive
• LFL: LE-CODE File List
• Wiimm's Test Tracks

Extended presence flags

• Introduction
• Technical Description
• Track Tutorial
• Software Overview
• Implementation Hints

Related Categories

• LE-CODE
• Extended Presence Flags

Overview

This article answers frequently asked questions about how to use LE-CODE's various extentions in a custom track distribution.

Common Files

Files found in Common.szs can be replaced per track. This is done by placing these files in a ./Common/ directory in the track SZS. More information can be found at the track FAQ.

Currently, there are six files that are supported:

• ObjFlow.bin
• GeoHitTableItem.bin
• GeoHitTableItemObj.bin
• GeoHitTableKart.bin
• GeoHitTableKartObj.bin
• minigame.kmg

Extracting Common Files

The common files need to be stored outside of the track SZS file when used in a distribution. Their location should be ./files/Race/Common/%N/*, where %N is the slot number of the track in a three-long lowercase hexadecimal number. The command

wszst xcommon ./files/Race/Course/*.szs -qiod ./files/Race/Common/%N/

can extract all common files to their correct places.

Issue Multiplayer Files

Currently, only common files of the standard track are loaded. This means that the Multiplayer variant of the track will load the same files. Usually this is not a problem, since they often use the same common files, but situations can arise where different files are desired.