Skip to main content
nebulaModding docs
Nebula home

lumalink run

Start the installed game with a mod - a folder is packed first, then imported into the game's mods. A mod folder with code plays in dev mode - each change to its code is built and reloaded in the running game until the game is closed.

Start the installed game with a mod: a folder is packed first, then imported into the game's mods. A mod folder with code plays in dev mode: each change to its code is built and reloaded in the running game until the game is closed.

#Example

Shell
lumalink run moon-jump

#Usage

Text
lumalink run [OPTIONS] <PATH> [ARGUMENTS]...

#Arguments

Argument Description
<PATH> A mod folder or a .luma file.

#Options

Option Description
--names <FOLDER> The game's self-description folder (function rows and types), for the rules on a mod's code. Default: the installed game's.
--platform <PLATFORM> A platform to check the code for (repeat for several). Default: all nine.
--game <FILE> Your imported game (Nebula's game.pak): its files, tables and keys. Default: the installed game.
--no-installed Leave out the installed game: only what --game and --names name is read, and the rules they would check are named as not checked.
--mods <FOLDER> Your mod folder: the mods (folders and .luma files) a mod's needs are found in. Without it, they are looked for beside the mod, in the installed game's mods and in the mods that come with the game.
-h, --help Print this help.
--language <LANGUAGE> The language LumaLink and the validator speak: one of the game's 14, by its name in the game (UsEnglish, EuGerman, JpJapanese...). Default: UsEnglish.

Every message and help text is available in each of the game's 14 languages, chosen with --language.