v1.7.3
What's Changed
Relevant changes since last stable version
General
- Launcher fix: if multiple servers are found and the last server is choosen it no longer ignores the selection and starts a new server.
- Launcher fix: agent returning error when only reverting the CDN mapping, updating internal state and returning the proper exit code.
- Launcher fix: reverting certificates in case of error in
config-admin
now correctly prints it's successful and return the successful exit code. - Launcher fix: if an unexpected error occurs it is printed and no longer returns a success exit code.
- Launcher enhancement: better error handling.
- Enhancement: added
ExtKeyUsageClientAuth
as the original certificate has it.
Linux
General
- Fix: launching scripts "Press any key to continue..." message on some shells.
- Fix: mark generated certificate as CA to have better compatibility.
Launcher
- Fix: panic (workaround) when reloading certificates in rare instance.
- Fix: not reading processes PIDs correctly, required for the main binary and
launcher-agent
. - Fix: installing a certificate now has a fallback if moving from temporary directory to the final directory cannot be done.
- Fix: finding a process when the process calling is normal and the one being queried is admin. No longer
config
incorrectly waits 30s forconfig-admin-agent
to start. - Fix: using the \n line ending when editing the hosts file (instead of \r\n as windows uses).
- Enhancement: added extra steam installation paths.
- Enhancement: reduced uncompressed archive size by ~10%.
See Github differences v1.7.2...v1.7.3
Files
- Full:
- Windows:
- 10 on x86-64: ..._full_1.7.2_win_x86-64.zip
- 11 on ARM: ..._full_1.7.2_win_arm64.tar.xz
- Linux:
- x86-64: ..._full_1.7.2_linux_x86-64.tar.xz
- ARM64: ..._full_1.7.2_linux_arm64.tar.xz
- Windows:
- Launcher:
- Windows:
- 10 on x86-64: ..._launcher_1.7.2_win_x86-64.zip
- 11 on ARM: ..._launcher_1.7.2_win_arm64.tar.xz
- Linux:
- x86-64: ..._launcher_1.7.2_linux_x86-64.tar.xz
- ARM64: ..._launcher_1.7.2_linux_arm64.tar.xz
- Windows:
- Server:
- Windows:
- 10 (IoT), Server (IoT) 2025 on ARM64: ..._server_1.7.2_win_arm64.zip
- 10 (IoT), (Storage) Server 2016, Server IoT 2019 on x86-64: ..._server_1.7.2_win_x86-64.zip
- 10 (IoT) on x86-32: ..._server_1.7.2_win_x86-32.zip
- Linux:
- Kernel 3.1 on ARM64: ..._server_1.7.2_linux_arm64.tar.xz
- Kernel 2.6.23 on ARM32:
- ARMv5 (armel): ..._server_1.7.2_linux_arm-5.tar.gz
- ARMv6 (sometimes called armhf): ..._server_1.7.2_linux_arm-6.tar.gz
- Kernel 2.6.23 on x86-64: ..._server_1.7.2_linux_x86-64.tar.gz
- Kernel 2.6.23 on x86-32: ..._server_1.7.2_linux_x86-32.tar.gz
- macOS - Big Sur (v11): ..._server_1.7.2_mac.tar.gz
- Windows:
Note: If you are using Antivirus it may flag one or more executables as virus, this is a false positive.
Verification
The verification process ensures that the files you download are the same as the ones that were uploaded by the maintainer.
- Download the
ageLANLanServer_1.7.2_checksums.txt
andageLANLanServer_1.7.2_checksums.txt.sig
files. - Import the release public key and import it to your keyring if you haven't already.
- Verify the
ageLANServer_1.7.2_checksums.txt
file with theageLANLanServer_1.7.2_checksums.txt.sig
file. - Verify the SHA-256 checksum list inside
ageLANServer_1.7.2_checksums.txt
with the downloaded archives.
Simplest way to use it
- Download the asset
ageLANServer_full_1.7.2_...
. - Uncompress it somewhere.
- Windows Optional: You may need to add the launcher/server binaries to the exception list of your Antivirus
- Windows Optional: Unblock the
.exe
files as explained here - If not using the Steam or Xbox launcher, edit the
launcher/resources/config.<game>.toml
file with a text editor (like Notepad) and modify theClient.Executable
section to point to the game launcher path.
You will need to use a custom launcher (plus what my other repo provides) for 100% offline play. - Execute
launcher/launcher_<game>
script: you will be asked for admin elevation and confirmation of other dialogs as needed, you will also need to allow the connections via the Microsoft Defender Firewall or any other. - Repeat the above steps for every PC you want to play in LAN with by running the launcher, the first PC to
launch it will host the "server" and the rest will auto-discover and connect to it. - In the game, when hosting a new lobby, just make sure to set the server to Use Local Lan Server (AoE II),
select LAN before creating the Lobby (AoE III) or select the "LAN" menu option (AoE I). In AoE I/II, setting it to public visibility is recommended. - If the lobby is Public, they can join directly in the browser or you can Invite friends by searching them by name and sending an invite as needed. You can share the link to join the lobby automatically (only works if already in-game).
Help
Look for the Troubleshooting if you have any issues (or QA for any doubt), create an issue or look for other related issues.