emulators.pcsx2

Root of the RomM library mount (env ROM_ROOT, default /romm).

A resolved disc image must sit under it; candidates resolving outside are discarded.

PCSX2's data root, holding inis/, memcards/ and sstates/.

Not configurable, and deliberately: nothing on pcsx2-qt's command line names it (-help offers only -portable, which forces the tree next to the binary), so an override would move only the ini the broker patches and the states it globs, while PCSX2 kept resolving its own. launch exports the root this resolved to instead.

The PCSX2.ini the broker patches before every launch, inis/PCSX2.ini under DATA_DIR.

Directory PCSX2 writes its .p2s save states into, sstates under DATA_DIR.

The GameDB/widescreen/fix patch bundle PCSX2 opens at boot, from its install resources.

Not configurable, and not under DATA_DIR: pcsx2-qt reads this one path and no other (a copy under the user tree is ignored), and it never downloads the file itself. The Ubuntu +dfsg package ships without it, so a missing file means a permanent "Failed to open patches.zip" warning and no game fixes. _ensure_patches_zip fetches it before a launch.

Upstream's rolling release of the patch bundle, rebuilt by CI on every push to its main branch.

Hardcoded, like the destination: this download ends in a root-owned file, so neither end of it may come from a request, the environment or config. Upstream publishes no checksum, so trust rests on TLS to GitHub plus _patches_zip_problem.

Whether launches fetch patches.zip (env PCSX2_PATCHES_FETCH, default true).

Set it to false (or 0, no, off) on a deploy with no route to GitHub, or one that should not use sudo at all: PCSX2 then runs without game patches, as it did before.

Age in seconds past which an installed bundle is refreshed in the background.

Upstream rebuilds on every merge, but patches change slowly; a week keeps launches to one fetch between container recreations without letting fixes lag far behind.

Log file the broker tails for this emulator (env PCSX2_LOG_PATH, default /config/pcsx2-qt.log).

Default slot the broker works in (env PCSX2_STATE_SLOT, default 10).

10 is PCSX2's own autosave slot, which the per-emulator broker has always used, so containers that ran that one keep resolving their existing states.

Only a default: each Pcsx2 copies it into state_slot at construction and every state operation reads that instance attribute, so a session can be pointed at another slot without moving the whole process.

Directory PCSX2 keeps its memory cards in, memcards under DATA_DIR.

Name of the Slot-1 card the broker owns (env PCSX2_SLOT1_CARD, default romm-slot1).

PCSX2 tells a folder card from a file card by what it finds at the path, so this is a directory and the name carries no .ps2 extension, to keep it from reading as one of PCSX2's own file cards. Validated by _slot1_card_name.

File that marks a directory as a folder card.

PCSX2 only counts a directory as a folder card once this file is inside it, and skips the directory entirely otherwise, which leaves the slot reading as missing with nowhere for the game to save.

Seconds a save state has to land on disk after the PINE save command (env PINE_WAIT, default 20).

Seconds the boot watchdog gives the VM to start running (env RESUME_LOAD_WAIT, default 90).

Seconds to wait after the VM reports running before a resume load is sent (env RESUME_LOAD_SETTLE).

Seconds a booted VM gives the resume state to arrive (env PCSX2_RESUME_STATE_WAIT, default 60).

Its own budget rather than whatever is left of the boot deadline: RomM pushes its resume pick after activate returns, so a slow boot would otherwise leave the wait no time at all and the player would start a fresh game.

Path of the PINE Unix socket pcsx2-qt listens on.

Disc formats pcsx2-qt can boot, best first.

A folder holding several candidates picks by this order so a .chd beats the raw .bin beside it.