Luma (tool) on Luanti Documentation

Command line

Mon, 01 Jan 0001 00:00:00 +0000

Passing a command runs it without opening the terminal UI. Commands take the form <noun> <verb>:

luma [global flags] <noun> <verb> [flags] [arguments]

Global flags, such as --dir, go before the command. See Global flags for the full list.

luma --dir /path/to/luanti mods list
luma --flatpak mods outdated

command	shows
`luma --help`	global flags and command groups
`luma mods --help`	the commands of a group
`luma mods update --help`	the flags of a command

code	meaning
0	success
1	error
2	usage error, e.g. unknown command or flag

Results are written to standard output, errors and warnings to standard error.

Mon, 01 Jan 0001 00:00:00 +0000

Global flags apply to both the terminal UI and the command line. They go before any command:

flag	meaning
`--dir <path>`, `-d <path>`	use the Luanti install at `<path>`, defaults to the current directory
`--flatpak`	use the Luanti flatpak install
`--engine-version <version>`, `-e <version>`	override the detected engine version

--dir and --flatpak can’t be used together. If no install is found, luma exits with an error.

Without --dir or --flatpak, the current directory is assumed to be the Luanti install, so luma can be run with no arguments from inside it:

Mon, 01 Jan 0001 00:00:00 +0000

Running luma without a command opens the terminal UI:

luma --dir /path/to/luanti
luma --flatpak

The main menu shows the folders and engine version in use, and leads to the mods, games and texture packs screens.

q is ignored while certain operations are happening to avoid leaving directories in an invalid state.