dl.seraph.si. Nothing else is official.
Our domains always end in
seraph.si. A launcher from anywhere else is not ours, whatever the
file is called.The launcher
Windows
Download for Windows x64An installer. Windows may warn about an unrecognised app the first time you run it.
macOS
Download for Apple SiliconA disk image for M1 and later. Intel Macs are not published yet.
Linux
Download for Linux x64An AppImage. Make it executable with
chmod +x seraph-launcher.AppImage before running it.How the download URLs are built
Every build is published under its own version, so a link never changes what it points at:
The current release is 0.3.0. Alongside each build sits the bundle the updater installs
(
seraph-launcher.app.tar.gz on macOS) and a .sig file, which is the signature the launcher
checks before it installs anything.
How the launcher updates itself
The launcher reads a manifest for its channel on startup:Releases are cut on three channels:
stable, beta and alpha. Ordinary installs follow
stable.How the mod updates
The mod is not something you download. The launcher fetches it for you and installs or injects it each time you launch, so the mod is current whenever the launcher is. While you are in game, Seraph is also told about new releases over its stats socket, and says so in chat once per version:Verifying what you downloaded
1
Check the domain
The address bar must read
dl.seraph.si. Not a lookalike, not a mirror, not a shortener.2
Check the file name
seraph-launcher.exe, seraph-launcher.dmg or seraph-launcher.AppImage. Anything ending
in .scr, .bat, .jar or .zip claiming to be the launcher is not.3
Let it update itself
Once installed, the launcher only ever installs signed builds from its own manifest. Taking
updates from it, rather than from a link someone sent you, is the safest route.