yarn dlx -p @sabinmarcu/mods mods --game grounded2 install "/path/to/mod.zip"
pnpm dlx --package @sabinmarcu/mods mods --game grounded2 install "/path/to/mod.zip"
npx --package @sabinmarcu/mods mods --game grounded2 install "/path/to/mod.zip"
Select the target game and pass the archive after the install command:
yarn dlx -p @sabinmarcu/mods mods --game grounded2 install "/path/to/mod.zip"
pnpm dlx --package @sabinmarcu/mods mods --game grounded2 install "/path/to/mod.zip"
npx --package @sabinmarcu/mods mods --game grounded2 install "/path/to/mod.zip"
Use --game-root when automatic discovery cannot locate the game:
yarn dlx -p @sabinmarcu/mods mods --game grounded2 --game-root "/path/to/Grounded2" install "/path/to/mod.7z"
pnpm dlx --package @sabinmarcu/mods mods --game grounded2 --game-root "/path/to/Grounded2" install "/path/to/mod.7z"
npx --package @sabinmarcu/mods mods --game grounded2 --game-root "/path/to/Grounded2" install "/path/to/mod.7z"
The archive must be a .zip, .7z, or .7zip file. The CLI finds complete triplets even when they are inside archive folders. A single new triplet installs immediately. In other cases, it shows a selector. Use arrow keys or j and k to move, Space to select an eligible mod, a to select or clear all eligible mods, Enter to install, and q to quit.
An existing mod is labelled installed when every archive timestamp matches the corresponding installed file. It remains visible but cannot be selected. A nonmatching installed mod is labelled update when at least one archive file is newer; otherwise it is labelled older.
During installation, each destination file is first extracted to a temporary file. Existing complete triplets are backed up, and the installation is rolled back if a later write fails. Archive timestamps are preserved on the installed files.
Documentation files such as README, INSTALL, LICENSE, .txt, .md, .nfo, and .rtf are allowed alongside triplets. Any other file type stops installation, including incomplete triplets and duplicate mod names. The CLI lists the archive files and leaves them untouched so the mod author's instructions can be followed manually.
There is no remove or uninstall command. The CLI does not delete mod files.
To remove a mod, close the game and delete its complete triplet from the selected mods directory: the matching .pak, .ucas, and .utoc files. For a disabled mod, delete the corresponding .pak.disabled, .ucas.disabled, and .utoc.disabled files. Do not delete only one member of a triplet; the manager ignores incomplete sets and cannot restore missing files.