Skip to content

Documentation

Mods, shaders and packs

Search and install mods, resource packs, shaders and data packs from Modrinth and CurseForge without leaving the launcher, per instance.

Built-in catalogs

  • Per-instance search in both catalogs, with a page for every project: description, gallery and changelog.
  • Installing a mod brings its required dependencies, verifies every file and records everything.
  • Installed mods can be checked and updated in place.
  • Packs and shaders work even in vanilla instances. Data packs go to the chosen world and are listed and managed per world.

The mods table

The Mods section of every instance is a table you can work in: disable, remove, update when a newer build exists, identify or delete a jar you dropped in by hand, with a filter by name or file.

  • The disk is the truth: a jar placed by hand in mods/ shows up with the name it gives itself; a file deleted from outside is marked as missing; a mod enabled or disabled in the file manager fixes the launcher record.
  • Loose files are identified by hash in the catalogs and gain a project, a version and an update path.

Loaders

Fabric, Quilt, Forge and NeoForge, with builds listed live and installed on top of the vanilla version. Forge and NeoForge are installed by the launcher itself, everything verified before running.

  • Quilt instances accept Fabric mods; NeoForge 1.20.1 accepts Forge mods.
  • Forge 1.13 to 1.16 install, in the game and on servers.

Respect for authors

  • When a pack ships a mod whose author does not allow other programs to download it, the launcher installs everything else and leaves a MODS-QUE-FALTAM.txt in the instance folder saying which ones are missing and where to get each.
  • Exports point to the mods instead of redistributing them.