Skip to content

Releases

v0.0.19

Choose a tag to compare

@github-actions github-actions released this 05 Nov 17:18
98dfd11

What's Changed

  • Collect gen0 once a minute while the game server is idle by @onionhammer in #119

Full Changelog: v0.0.18...v0.0.19

Install

Installed copies update themselves — you only ever download an installer once.

  • Windows — StellarAllegiance-win-Setup.exe. Installs per-user (no admin prompt) and adds Start menu + desktop shortcuts. Unsigned: SmartScreen will ask once (More info → Run anyway).
  • macOS — StellarAllegiance-osx-Portable.zip. Unzip, drag Stellar Allegiance into Applications, then run it from there. Ad-hoc signed (not notarized): clear quarantine once with xattr -dr com.apple.quarantine "/Applications/Stellar Allegiance.app". (A .pkg is attached too — choose Install for me only: an all-users install is owned by root, and every update would then ask for an admin password.)
  • Linux — StellarAllegiance.AppImage. chmod +x it, keep it somewhere writable (it replaces itself when it updates), and run it.

Coming from a pre-launcher zip build (v0.0.12 or older)? Install once with the link above; your settings and sign-in are kept.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.19

Set SIM_PUBLIC_NAME to be listed in the public server browser. See docker-compose.server.yml for the full env/NAT configuration.

This image self-updates. Once no player is connected it downloads and applies the next release in place and relaunches itself — no redeploy needed. Set SIM_AUTO_UPDATE=warn to only log that an update is available instead, or off to disable the check entirely (see docker-compose.server.yml / .env.example).

A server still running a PRE-auto-update image won't pick this feature up on its own — pull and recreate it once: docker compose -f docker-compose.server.yml pull && docker compose -f docker-compose.server.yml up -d. From there it updates itself going forward.

Not using Docker? Bare Linux AppImages are attached below too — StellarAllegianceServer-server-linux-x64.AppImage / -arm64. chmod +x and run (needs the fusermount helper: apt install fuse3). Outside a container the default is SIM_AUTO_UPDATE=warn; set SIM_AUTO_UPDATE=on and it updates itself the same way (systemd unit in docs/DEPLOY.md).

v0.0.18

Choose a tag to compare

@github-actions github-actions released this 05 Nov 00:09
71583fe

What's Changed

  • Stop the server's safety-net feed poll while the lobby link is up by @onionhammer in #116
  • Tune GC for lobby memory and game server balance; fix simbot spawning and /admin after restarts by @onionhammer in #117
  • Let the game server sleep while nobody is connected by @onionhammer in #118

Full Changelog: v0.0.17...v0.0.18

Install

Installed copies update themselves — you only ever download an installer once.

  • Windows — StellarAllegiance-win-Setup.exe. Installs per-user (no admin prompt) and adds Start menu + desktop shortcuts. Unsigned: SmartScreen will ask once (More info → Run anyway).
  • macOS — StellarAllegiance-osx-Portable.zip. Unzip, drag Stellar Allegiance into Applications, then run it from there. Ad-hoc signed (not notarized): clear quarantine once with xattr -dr com.apple.quarantine "/Applications/Stellar Allegiance.app". (A .pkg is attached too — choose Install for me only: an all-users install is owned by root, and every update would then ask for an admin password.)
  • Linux — StellarAllegiance.AppImage. chmod +x it, keep it somewhere writable (it replaces itself when it updates), and run it.

Coming from a pre-launcher zip build (v0.0.12 or older)? Install once with the link above; your settings and sign-in are kept.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.18

Set SIM_PUBLIC_NAME to be listed in the public server browser. See docker-compose.server.yml for the full env/NAT configuration.

This image self-updates. Once no player is connected it downloads and applies the next release in place and relaunches itself — no redeploy needed. Set SIM_AUTO_UPDATE=warn to only log that an update is available instead, or off to disable the check entirely (see docker-compose.server.yml / .env.example).

A server still running a PRE-auto-update image won't pick this feature up on its own — pull and recreate it once: docker compose -f docker-compose.server.yml pull && docker compose -f docker-compose.server.yml up -d. From there it updates itself going forward.

Not using Docker? Bare Linux AppImages are attached below too — StellarAllegianceServer-server-linux-x64.AppImage / -arm64. chmod +x and run (needs the fusermount helper: apt install fuse3). Outside a container the default is SIM_AUTO_UPDATE=warn; set SIM_AUTO_UPDATE=on and it updates itself the same way (systemd unit in docs/DEPLOY.md).

v0.0.17

Choose a tag to compare

@github-actions github-actions released this 24 Oct 18:27
2986d0b

What's Changed

  • Wipe the last match's result when an emptied server recycles (#110) by @onionhammer in #113
  • Add Aspire controls plugin with core functionality and types by @onionhammer in #114
  • Upgrade outdated dependencies + lobby/game-server reconnect resilience by @onionhammer in #115

Full Changelog: v0.0.16...v0.0.17

Install

Installed copies update themselves — you only ever download an installer once.

  • Windows — StellarAllegiance-win-Setup.exe. Installs per-user (no admin prompt) and adds Start menu + desktop shortcuts. Unsigned: SmartScreen will ask once (More info → Run anyway).
  • macOS — StellarAllegiance-osx-Portable.zip. Unzip, drag Stellar Allegiance into Applications, then run it from there. Ad-hoc signed (not notarized): clear quarantine once with xattr -dr com.apple.quarantine "/Applications/Stellar Allegiance.app". (A .pkg is attached too — choose Install for me only: an all-users install is owned by root, and every update would then ask for an admin password.)
  • Linux — StellarAllegiance.AppImage. chmod +x it, keep it somewhere writable (it replaces itself when it updates), and run it.

Coming from a pre-launcher zip build (v0.0.12 or older)? Install once with the link above; your settings and sign-in are kept.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.17

Set SIM_PUBLIC_NAME to be listed in the public server browser. See docker-compose.server.yml for the full env/NAT configuration.

This image self-updates. Once no player is connected it downloads and applies the next release in place and relaunches itself — no redeploy needed. Set SIM_AUTO_UPDATE=warn to only log that an update is available instead, or off to disable the check entirely (see docker-compose.server.yml / .env.example).

A server still running a PRE-auto-update image won't pick this feature up on its own — pull and recreate it once: docker compose -f docker-compose.server.yml pull && docker compose -f docker-compose.server.yml up -d. From there it updates itself going forward.

Not using Docker? Bare Linux AppImages are attached below too — StellarAllegianceServer-server-linux-x64.AppImage / -arm64. chmod +x and run (needs the fusermount helper: apt install fuse3). Outside a container the default is SIM_AUTO_UPDATE=warn; set SIM_AUTO_UPDATE=on and it updates itself the same way (systemd unit in docs/DEPLOY.md).

v0.0.16

Choose a tag to compare

@github-actions github-actions released this 30 Sep 00:16
b9bb3fc

What's Changed

  • Add Target Pane for Tab-focused HUD display (#97) by @onionhammer in #99
  • Windows: embed the app icon in the launcher and game exes by @onionhammer in #103
  • Settings: VIDEO tab — window mode, vsync, max FPS, render scale, UI scale (#96) by @onionhammer in #104
  • Audio: sound the silent gameplay events — dock, warp, shields, alarms (#105) by @onionhammer in #106
  • Equipment, energy & ammo: shield/afterburner/cloak parts, energy and ammo pools, Scout cloak (protocol 44) by @onionhammer in #107
  • Client: persist one lobby session per lobby (fixes re-auth on lobby switch) by @onionhammer in #111
  • Match end: out of play at once — Esc lands in the lobby, world swept silently (protocol 45) by @onionhammer in #112

Full Changelog: v0.0.15...v0.0.16

Install

Installed copies update themselves — you only ever download an installer once.

  • Windows — StellarAllegiance-win-Setup.exe. Installs per-user (no admin prompt) and adds Start menu + desktop shortcuts. Unsigned: SmartScreen will ask once (More info → Run anyway).
  • macOS — StellarAllegiance-osx-Portable.zip. Unzip, drag Stellar Allegiance into Applications, then run it from there. Ad-hoc signed (not notarized): clear quarantine once with xattr -dr com.apple.quarantine "/Applications/Stellar Allegiance.app". (A .pkg is attached too — choose Install for me only: an all-users install is owned by root, and every update would then ask for an admin password.)
  • Linux — StellarAllegiance.AppImage. chmod +x it, keep it somewhere writable (it replaces itself when it updates), and run it.

Coming from a pre-launcher zip build (v0.0.12 or older)? Install once with the link above; your settings and sign-in are kept.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.16

Set SIM_PUBLIC_NAME to be listed in the public server browser. See docker-compose.server.yml for the full env/NAT configuration.

This image self-updates. Once no player is connected it downloads and applies the next release in place and relaunches itself — no redeploy needed. Set SIM_AUTO_UPDATE=warn to only log that an update is available instead, or off to disable the check entirely (see docker-compose.server.yml / .env.example).

A server still running a PRE-auto-update image won't pick this feature up on its own — pull and recreate it once: docker compose -f docker-compose.server.yml pull && docker compose -f docker-compose.server.yml up -d. From there it updates itself going forward.

Not using Docker? Bare Linux AppImages are attached below too — StellarAllegianceServer-server-linux-x64.AppImage / -arm64. chmod +x and run (needs the fusermount helper: apt install fuse3). Outside a container the default is SIM_AUTO_UPDATE=warn; set SIM_AUTO_UPDATE=on and it updates itself the same way (systemd unit in docs/DEPLOY.md).

v0.0.15

Choose a tag to compare

@onionhammer onionhammer released this 21 Sep 00:55
7caad37

Two bugs that were in every installed build are fixed here. Both were reported as something else — "server lag" and "the launcher crashes".

Stations and ships are solid again

Installed builds shipped with no collision data. Every station was treated, client-side, as a featureless 90-unit sphere with no docking doors — so your ship spawned inside it and the server corrected you every tick. That is what the rubber-banding and jitter near a station was; the servers were healthy the whole time.

The collision geometry now ships as a small sidecar beside each model (268 KiB for all 31), and packaging refuses to build a release that cannot load it. A model that still fails is now loud — an error in the log, an alert under the server browser, and an alert on the flight HUD if the server actually fielded it — instead of silently becoming a sphere.

Quitting to desktop no longer crashes

Quitting a game joined through the lobby crashed on the way out roughly two times in three. The launcher then greeted you with THE GAME CLOSED UNEXPECTEDLY, and macOS raised a crash dialog a few seconds later.

The quit was being read as a lost connection, so the client started reconnecting to the server it was in the middle of leaving. Hanging up is now terminal: no reconnect, no crash, a clean goodbye to the server. Losing the connection for real still reconnects and reclaims your ship, as before.

Also fixed on the way out: leaked cursor textures that logged errors at every exit, and a client that could sit on "Connected" after a peer had gone silent.

Launcher

It no longer aborts when the Mac's display is asleep — it logs the failure and exits instead of leaving a crash report waiting for whoever wakes the screen.

Install

Installed copies update themselves — you only ever download an installer once.

  • Windows — StellarAllegiance-win-Setup.exe. Installs per-user (no admin prompt) and adds Start menu + desktop shortcuts. Unsigned: SmartScreen will ask once (More info → Run anyway).
  • macOS — StellarAllegiance-osx-Portable.zip. Unzip, drag Stellar Allegiance into Applications, then run it from there. Ad-hoc signed (not notarized): clear quarantine once with xattr -dr com.apple.quarantine "/Applications/Stellar Allegiance.app". (A .pkg is attached too — choose Install for me only: an all-users install is owned by root, and every update would then ask for an admin password.)
  • Linux — StellarAllegiance.AppImage. chmod +x it, keep it somewhere writable (it replaces itself when it updates), and run it.

Coming from a pre-launcher zip build (v0.0.12 or older)? Install once with the link above; your settings and sign-in are kept.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.15

Set SIM_PUBLIC_NAME to be listed in the public server browser. See docker-compose.server.yml for the full env/NAT configuration.

This image self-updates. Once no player is connected it downloads and applies the next release in place and relaunches itself — no redeploy needed. Set SIM_AUTO_UPDATE=warn to only log that an update is available instead, or off to disable the check entirely (see docker-compose.server.yml / .env.example).

A server still running a PRE-auto-update image won't pick this feature up on its own — pull and recreate it once: docker compose -f docker-compose.server.yml pull && docker compose -f docker-compose.server.yml up -d. From there it updates itself going forward.

Not using Docker? Bare Linux AppImages are attached below too — StellarAllegianceServer-server-linux-x64.AppImage / -arm64. chmod +x and run (needs the fusermount helper: apt install fuse3). Outside a container the default is SIM_AUTO_UPDATE=warn; set SIM_AUTO_UPDATE=on and it updates itself the same way (systemd unit in docs/DEPLOY.md).

v0.0.14

Choose a tag to compare

@github-actions github-actions released this 20 Sep 20:22
67507e4

What's Changed

  • NativeAOT game server compilation by @onionhammer in #86
  • Repaint sector environment on row arrival by @onionhammer in #87
  • Upgrade dependencies and enforce .NET SDK version by @onionhammer in #88
  • Game-server auto-update via Velopack, triggered by the public lobby by @onionhammer in #89
  • Release rehearsal follow-ups: e2e release gate, hand-run relaunch fix, Node 24 actions by @onionhammer in #90
  • Plan index: the server auto-update rehearsal is done by @onionhammer in #91

Full Changelog: v0.0.13...v0.0.14

Install

Installed copies update themselves — you only ever download an installer once.

  • Windows — StellarAllegiance-win-Setup.exe. Installs per-user (no admin prompt) and adds Start menu + desktop shortcuts. Unsigned: SmartScreen will ask once (More info → Run anyway).
  • macOS — StellarAllegiance-osx-Portable.zip. Unzip, drag Stellar Allegiance into Applications, then run it from there. Ad-hoc signed (not notarized): clear quarantine once with xattr -dr com.apple.quarantine "/Applications/Stellar Allegiance.app". (A .pkg is attached too — choose Install for me only: an all-users install is owned by root, and every update would then ask for an admin password.)
  • Linux — StellarAllegiance.AppImage. chmod +x it, keep it somewhere writable (it replaces itself when it updates), and run it.

Coming from a pre-launcher zip build (v0.0.12 or older)? Install once with the link above; your settings and sign-in are kept.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.14

Set SIM_PUBLIC_NAME to be listed in the public server browser. See docker-compose.server.yml for the full env/NAT configuration.

This image self-updates. Once no player is connected it downloads and applies the next release in place and relaunches itself — no redeploy needed. Set SIM_AUTO_UPDATE=warn to only log that an update is available instead, or off to disable the check entirely (see docker-compose.server.yml / .env.example).

A server still running a PRE-auto-update image won't pick this feature up on its own — pull and recreate it once: docker compose -f docker-compose.server.yml pull && docker compose -f docker-compose.server.yml up -d. From there it updates itself going forward.

Not using Docker? Bare Linux AppImages are attached below too — StellarAllegianceServer-server-linux-x64.AppImage / -arm64. chmod +x and run (needs the fusermount helper: apt install fuse3). Outside a container the default is SIM_AUTO_UPDATE=warn; set SIM_AUTO_UPDATE=on and it updates itself the same way (systemd unit in docs/DEPLOY.md).

v0.0.13

Choose a tag to compare

@github-actions github-actions released this 19 Sep 21:59
e9ea0e8

What's Changed

  • Public lobby: stop a redeploy from revoking game-server credentials by @onionhammer in #74
  • Post-protocol-38 cleanup pass: format, green suites, shared helpers, YAML autopilot knobs, token migration, god-file splits by @onionhammer in #75
  • Netcode 1/6: source-generated wire codecs (shared frame definitions + equivalence tests) by @onionhammer in #76
  • Netcode 2/6: server speaks the shared frames; legacy writer/reader deleted by @onionhammer in #77
  • Netcode 3/6: Godot client reads and writes the shared frames by @onionhammer in #78
  • Netcode 4/6: one declaration per low-rate stream (hub) + shared set reconciler (client) by @onionhammer in #79
  • Netcode 5/6: team count on the wire (protocol 41) by @onionhammer in #80
  • Netcode 6/6: sim→hub StepEvents seam + shared test kit by @onionhammer in #81
  • Implement ship salvage functionality and enhance netcode by @onionhammer in #82
  • Add offline interpolation test harness and update README by @onionhammer in #83
  • Implement crew-served turret mechanics and client-authoritative aiming by @onionhammer in #84
  • Add game launcher and installer by @onionhammer in #85

Full Changelog: v0.0.12...v0.0.13

Install

Installed copies update themselves — you only ever download an installer once.

  • Windows — StellarAllegiance-win-Setup.exe. Installs per-user (no admin prompt) and adds Start menu + desktop shortcuts. Unsigned: SmartScreen will ask once (More info → Run anyway).
  • macOS — StellarAllegiance-osx-Portable.zip. Unzip, drag Stellar Allegiance into Applications, then run it from there. Ad-hoc signed (not notarized): clear quarantine once with xattr -dr com.apple.quarantine "/Applications/Stellar Allegiance.app". (A .pkg is attached too — choose Install for me only: an all-users install is owned by root, and every update would then ask for an admin password.)
  • Linux — StellarAllegiance.AppImage. chmod +x it, keep it somewhere writable (it replaces itself when it updates), and run it.

Coming from a pre-launcher zip build (v0.0.12 or older)? Install once with the link above; your settings and sign-in are kept.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.13

Set SIM_PUBLIC_NAME to be listed in the public server browser. See docker-compose.server.yml for the full env/NAT configuration.

v0.0.12

Choose a tag to compare

@onionhammer onionhammer released this 08 Sep 22:53

What's Changed

  • Implement score screen and update anti-base launcher magazine sizes by @onionhammer in #72
  • Public lobby: accounts, Verified servers and the ladder (protocol 38) by @onionhammer in #73

Full Changelog: v0.0.11...v0.0.12

Client downloads

Pick your platform below. Unzip and run.

  • macOS — ad-hoc signed (not notarized). After unzipping, clear quarantine once:
    xattr -dr com.apple.quarantine stellarallegiance.app, then launch.
  • Windows / Linux — keep the whole unzipped folder together (the executable needs
    its sibling .pck and data_* directory).

On first launch you can browse the public lobby or enter a server address directly.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.12

Set SIM_PUBLIC_NAME to be listed in the public server browser. See
docker-compose.server.yml for the full env/NAT configuration.

v0.0.11

Choose a tag to compare

@onionhammer onionhammer released this 15 Aug 12:19
3807ea8

What's Changed

  • Refactor and document code review findings by @onionhammer in #61
  • Gray out unaffordable build/research items by @onionhammer in #64
  • F3 map: text type labels for constructors, miners, and ships by @onionhammer in #63
  • Suppress nav/target distance readout across sectors by @onionhammer in #62
  • Refactor scripts to PowerShell and remove obsolete plans by @onionhammer in #65
  • Implement per-base research trees and update documentation by @onionhammer in #66
  • Improve performance logging and resource management by @onionhammer in #67
  • Refactor docking mechanics and enhance HUD performance by @onionhammer in #69
  • Enhance capital ship handling and visual fidelity by @onionhammer in #70
  • Implement timed reload for cargo-fed launchers and dispensers by @onionhammer in #71

Full Changelog: v0.0.10...v0.0.11

Client downloads

Pick your platform below. Unzip and run.

  • macOS — ad-hoc signed (not notarized). After unzipping, clear quarantine once:
    xattr -dr com.apple.quarantine stellarallegiance.app, then launch.
  • Windows / Linux — keep the whole unzipped folder together (the executable needs
    its sibling .pck and data_* directory).

On first launch you can browse the public lobby or enter a server address directly.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.11

Set SIM_PUBLIC_NAME to be listed in the public server browser. See
docker-compose.server.yml for the full env/NAT configuration.

v0.0.10

Choose a tag to compare

@onionhammer onionhammer released this 18 Jul 22:37
4660727

What's Changed

  • Implement commander and prospecting order functionalities by @onionhammer in #59
  • Implement tech tree enhancements and base building mechanics by @onionhammer in #60

Full Changelog: v0.0.9...v0.0.10

Client downloads

Pick your platform below. Unzip and run.

  • macOS — ad-hoc signed (not notarized). After unzipping, clear quarantine once:
    xattr -dr com.apple.quarantine stellarallegiance.app, then launch.
  • Windows / Linux — keep the whole unzipped folder together (the executable needs
    its sibling .pck and data_* directory).

On first launch you can browse the public lobby or enter a server address directly.

Self-hosting a game server

Run the published image (pairs with docker-compose.server.yml in the repo):

docker pull ghcr.io/wivuu/stellarallegiance-sim:0.0.10

Set SIM_PUBLIC_NAME to be listed in the public server browser. See
docker-compose.server.yml for the full env/NAT configuration.