This is a AppImage for Yamagi Quake II
AppImage is a format for distributing portable software on Linux without needing superuser permissions to install the application It tries also to allow Linux distribution-agnostic binary software deployment for application developers, also called Upstream packaging. Released first in 2004 under the name klik, it was continuously developed, then renamed in 2011 to PortableLinuxApps and later in 2013 to AppImage. wikipedia
All credits here:
https://www.yamagi.org/quake2/
https://github.com/yquake2/yquake2
Download the AppImages from the release page! Then, make the AppImage an executable by entering chmod +x $FILE in a terminal or by right-clicking the file then selecting "Properties" then "Permissions", and checking the executable checkbox. Then, double-`click the AppImage to run Yamagi Quake II. To launch mods, use the game menu or enter in the terminal:
./Yamagi_Quake_II-8.3.0-x86_64.AppImage +set game <mod name>
AppImage include xatrix rogue zaero ctf mods.
This package only provides the engine, you need a valid copy of the (proprietary) game data to launch the game. When you first start the game, you will be asked to place your game data along the following paths:
~/.yq2/baseq2
~/.yq2/xatrix
~/.yq2/rogue
~/.yq2/ctf
~/.yq2/zaero
You can place game data in these paths before starting the game. Then the game will start immediately.
All AppImages are signed, including those compiled using GitHub Action.
You can check the application signature by running the command in the terminal:
./Yamagi_Quake_II-8.3.0-x86_64.AppImage --appimage-signature
Get keyid and verify:
./Yamagi_Quake_II-20240226-8.3.0-x86_64.AppImage --appimage-signature | gpg --list-packets | grep keyid
:signature packet: algo 1, keyid CDC41982C027BAAA
gpg --recv-keys --keyserver keyserver.ubuntu.com CDC41982C027BAAA
| CI | Platform | Compiler | Configurations | Platforms | Status |
|---|---|---|---|---|---|
| GitHub Actions | Ubuntu | GCC | Release | x64 | |
You can download a the automatically build based on the latest commit.
To do this, go to the Actions tab, select the top workflows, and then Artifacts.