4.8 KiB
PristonTale EU for Linux
Version 0.9.0 installs, updates, repairs, and launches PristonTale EU through a native Linux dashboard. Game files come directly from the publisher and are not included in this archive.
Install
Keep the archive, detached signature, checksum, and
launcher-update-public.pem together. First confirm the public-key fingerprint
through an independent trusted channel; the expected DER SHA-256 fingerprint is
3ae6e8dc483b93796b32e3ca270c367d247caf8d047eb796826c8e558a4a9e34.
Then run:
openssl pkey -pubin -in launcher-update-public.pem -outform DER | sha256sum
openssl dgst -sha256 -verify launcher-update-public.pem \
-signature pristontale-eu-linux-installer-v0-9-0.tar.gz.sig \
pristontale-eu-linux-installer-v0-9-0.tar.gz
sha256sum -c pristontale-eu-linux-installer-v0-9-0.tar.gz.sha256
tar -xzf pristontale-eu-linux-installer-v0-9-0.tar.gz
cd pristontale-eu-linux-installer-v0-9-0
./install.sh
The default installation directory is ~/Games/PristontaleEU. To use another
disk or directory:
./install.sh --install-dir "/path/to/PristontaleEU"
Existing installations at the previous default location are preserved during
upgrades. The installer adds PristonTale EU to the application menu and
installs the pristontale-eu command in ~/.local/bin.
Steam Proton 7.0 is discovered in both the default Steam library and secondary
libraries registered with the Steam client. If Proton uses an unregistered
manual layout, open Settings → Optional Overrides and select the exact
Proton 7.0/proton script.
Use
Open PristonTale EU from the application menu or run:
pristontale-eu gui
The main launcher button automatically shows Install, Update, or Play according to the managed game's state.
Commands
pristontale-eu --help Show all commands and options
pristontale-eu gui Open the native dashboard
pristontale-eu doctor Check required host components
pristontale-eu runtime-bootstrap Prepare the verified UMU helper
pristontale-eu container-host Test the Bubblewrap sandbox
pristontale-eu container-host --repair Repair recognized Ubuntu AppArmor states
pristontale-eu login-diagnostics Check the login route without credentials
pristontale-eu login-diagnostics --runtime proton7
Compare the direct-Proton prefix read-only
pristontale-eu login-trace Retired; refuses without starting the game
pristontale-eu update Install or update official files
pristontale-eu update --repair Verify and repair every game file
pristontale-eu update --dry-run Preview an update
pristontale-eu import-game "/path/to/game" Import an existing installation
pristontale-eu prepare Build the safe runtime view
pristontale-eu play Launch through the managed Proton window
pristontale-eu play --no-box Launch without X11 window styling
pristontale-eu play --no-world-fix Compatibility alias for the pristine launch
pristontale-eu settings Show current settings
pristontale-eu settings --init Create/migrate settings without resetting choices
pristontale-eu settings --reset Explicitly restore every launcher default
pristontale-eu launcher-update --check Check the signed launcher channel
pristontale-eu launcher-update --verify Validate the full release without installing it
pristontale-eu launcher-update Install and activate an update
pristontale-eu launcher-update --rollback Restore the previous launcher
pristontale-eu sync Sync without import discovery
pristontale-eu wine-update Run the legacy WPF updater
pristontale-eu fetch Fetch the publisher launcher
pristontale-eu setup Prepare its Wine environment
pristontale-eu cache-compatibility PATH Cache a verified compatibility pair
Use ./install.sh --dry-run to preview dependency installation or
./install.sh --skip-deps to manage distribution packages and the host sandbox
manually.
On Ubuntu, install and launcher-update operations run a harmless Bubblewrap
user-namespace probe. If AppArmor produces the exact bwrap UID-map permission
denial, the launcher can install and load a pinned upstream restrictive bwrap
profile. It also repairs only UMU's known broken
bwrap-userns-restrict-umu link. Authentication is required; the repair does
not disable AppArmor or change global kernel security settings, and it refuses
to install a competing profile when another bwrap policy is present.