Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/retired64/sm64coopdx_launcher/llms.txt

Use this file to discover all available pages before exploring further.

DynOS (Dynamic Object System) packs are resource bundles that replace or augment the game’s built-in assets at runtime. Common uses include character model replacements and texture packs. The launcher’s DynOS Packs panel lets you enable or disable any installed pack before launching the game, writing changes to sm64config.txt automatically.

What Are DynOS Packs?

DynOS packs extend the game’s visuals and gameplay without modifying the base executable:
  • Character model replacements — swap Mario for a custom character mesh and animations.
  • Texture packs — replace environmental textures, UI elements, or object skins.
  • Asset mods — any other resource bundle the DynOS subsystem supports.
The game reads enabled packs from sm64config.txt at startup and loads them from the dynos/packs/ directory.

Pack Directory

All DynOS packs live under:
~/.local/share/sm64coopdx/dynos/packs/
Only immediate subdirectories inside packs/ are treated as packs. Plain files placed directly in the packs/ folder are silently ignored — the scanner calls .is_dir() on each entry and skips anything that is not a directory. The launcher creates the dynos/packs/ directory automatically on first run if it does not already exist.

Opening the DynOS Packs Panel

1

Open the arc menu

Press Tab from the main launcher screen to open the arc navigation menu.
2

Select DynOS Packs

Navigate to DynOS Packs and confirm. The panel opens with an alphabetically sorted list of every detected pack.

Toggling Packs On and Off

Use the keyboard to navigate and toggle packs:
KeyAction
/ Move selection up or down
Enter or SpaceToggle the selected pack on (✓) or off (—)
EscClose the DynOS Packs panel
When you toggle a pack, the launcher immediately rewrites the dynos-pack: section of the active profile’s sm64config.txt. All other config lines (mod enables, network settings, etc.) are preserved exactly.

How Enabled Packs Are Stored

Enabled packs are recorded as dynos-pack: <name> lines in sm64config.txt, where <name> is the subdirectory name inside dynos/packs/. The parser reads lines that begin with the prefix dynos-pack: (with a space after the colon):
dynos-pack: MarioModelPack
dynos-pack: HD_Textures
The write is atomic — the launcher writes to a .tmp file first, then renames it over the target, so the config file is never partially written.
You can enable multiple packs simultaneously. The game loads them in the order they appear in sm64config.txt. If two packs replace the same asset, the last one loaded wins.

Installing a New Pack

1

Locate the packs directory

Open a terminal or file manager and navigate to ~/.local/share/sm64coopdx/dynos/packs/.
2

Copy the pack directory

Copy the pack’s root directory (not its contents) into packs/. After the copy, the structure should look like:
~/.local/share/sm64coopdx/dynos/packs/
└── MyNewPack/
    ├── mario/
    │   └── ...
    └── ...
3

Refresh the DynOS Packs panel

Close and reopen the DynOS Packs panel. The new pack appears in the list and is ready to be toggled on.
The pack must be a directory — the launcher only scans immediate subdirectories of dynos/packs/. Loose files placed directly in the packs/ folder are ignored.

Keyboard Shortcuts Summary

KeyAction
/ Navigate the pack list
Enter / SpaceToggle selected pack on/off
EscClose the DynOS Packs panel

Build docs developers (and LLMs) love