SpaceCorps 2027 0.2.3
SpaceCorps 2027 0.2.3 makes shields, shield cells, thrusters and laser amps work the way the item cards say: your absorbance now decides how much of each hit your shields take.
The game plays on the public server https://spacecorps-game.sliplane.app. Your pilot, ships and items carry over, modules included.
Download page: https://spacecorps.github.io/play/
What's new
Absorbance decides the damage split
- Until now every hit went 80% to your shields and 20% to your hull, whatever your absorbance. Now your absorbance is your shields' share of each hit, and the hull takes the rest.
- Your absorbance is the average of your shields, each with the shield cells fitted into it, at most 100%. A Light Shield Core alone is 70%, a Basic Shield Core 80%, a Heavy Shield Core 85%. Shield cells add 2%, 4% or 6% each. A Basic Shield Core with two Advanced cells is 88%, so your hull takes 12% instead of 20%.
- When your shields run out, the hull takes the whole hit, as before.
- Aliens still split every hit 80/20. Company pilots fly two Light Shield Cores, so their hull takes 30%.
- The hangar's combat stats show the split under the tiles ("Each hit: shields 88% · hull 12%"). In flight, the Ship window shows your shields' share on its bottom line, after Speed (hover it for the split).
Modules
- Adaptive Cores now take shield cells and thrusters, one per slot, of either kind. Their squares on the hangar board are real slots.
- Clicking a shield cell or thruster fits it into the first shield or engine with room, then into an Adaptive Core. If nothing has room, it goes to an ability slot, and the game now tells you it gives an ability there, not shield stats or speed.
- Only shields take a share of a hit. A shield cell in an Adaptive Core adds shield points, but with no shield equipped they go unused: the hangar says so, and a clicked cell prefers an ability slot on a ship without a shield.
- An item's tooltip lists its module slots, what is fitted and what each module adds, and the item's own totals with them. A module's tooltip says what it fits into.
- A refused fit says why: no free module slot, or the item doesn't take that kind of module.
- Fusing items now works when the items fused away hold modules. Those modules go back to your inventory. The item you keep keeps its own.
- Your modules count in flight exactly as the hangar shows, after a launch, a respawn, a reconnect and a configuration swap. Swapping configurations in flight now also switches Shield Regen and Speed Boost to the new configuration's ability slots, and a booster you add in flight counts at once.
Balance changes you will notice
- Adaptive Cores now give their bonuses: AC-I +5% shields and +3% speed, AC-II +8% and +4%, AC-III +15% and +5% (times the slot's share). Before, they added nothing and even halved your absorbance.
- Shields slow your ship again, as the item cards always said: Light Shield Core −1%, Basic −3%, Heavy −5% speed each (times the slot's share). Company pilots fly at 202 instead of 206.
Updating
- From 0.2.1 or 0.2.2: the game downloads 0.2.3 by itself. Click Restart to Update, or quit the game, and it installs. You can also look for it under Settings › About › Check for Updates.
- From 0.2.0: download it once from the download page and replace the old app or folder. From then on the game updates itself.
On macOS, keep the game in Applications. A game started from the disk image or from Downloads can't replace itself.
Platforms
| Package | For |
|---|---|
SpaceCorps2027-macos-universal.dmg |
macOS 12 Monterey or later, Apple silicon and Intel |
SpaceCorps2027-windows-x86_64.zip |
Windows 10 and 11, 64-bit |
SpaceCorps2027-linux-x86_64.AppImage |
Linux x86_64, glibc 2.35 or newer (Ubuntu 22.04, Debian 12, Fedora 36 and later), Vulkan |
SpaceCorps2027-linux-x86_64.tar.gz |
the same Linux build, as a folder to unpack |
Graphics need Metal (macOS), DirectX 12 or Vulkan (Windows), or Vulkan (Linux, Mesa 22 or a vendor driver). The game needs 4 GB of RAM (8 GB recommended) and 400 MB of free disk space.
First launch
The builds are not signed by Apple or Microsoft yet, so on a first install your system asks once before it opens the game. Updates the game installs itself don't ask again.
- macOS: open the dmg and drag SpaceCorps 2027 onto Applications.
- macOS 15 and newer: open the app once and click Done. Then go to System Settings › Privacy & Security and click Open Anyway next to "SpaceCorps 2027 was blocked".
- macOS 12 to 14: right-click (Control-click) the app, choose Open, then Open again.
- Windows: right-click the zip, choose Extract All, and start
spacecorps2027.exefrom theSpaceCorps 2027folder. Theassetsfolder must stay next to it. If SmartScreen says it "protected your PC", click More info, then Run anyway. - Linux: run
chmod +x SpaceCorps2027-linux-x86_64.AppImage, then start it. Or unpack the tar.gz and startSpaceCorps2027/spacecorps2027.
Known issues
- The builds are unsigned, so macOS Gatekeeper and Windows SmartScreen warn on a first install (see above).
- Updating from inside the game was tested end to end on macOS. On Windows and Linux it is covered by automated checks only, so please report anything that goes wrong.
- There is one public game server with limited capacity. It may restart for updates, and your ship is saved when it does.
Report problems at https://github.com/SpaceCorps/play/issues or on Discord.
Verify your download
SHA256SUMS lists every package's SHA-256 and is signed with the SpaceCorps release key
(SHA256SUMS.minisig, minisign). With both files next to
the package:
minisign -Vm SHA256SUMS -P RWRhY8TTCr07i1iOS7MT45OHD3LFJJnWXWCF19fy7hjV1RD8cwWlVKF1
shasum -a 256 -c SHA256SUMS --ignore-missing # Linux: sha256sum -c SHA256SUMS --ignore-missingChecksums
| Package | SHA-256 |
|---|---|
SpaceCorps2027-macos-universal.dmg |
c9ca572d9ce63630c201f4166609454cfe49f8427e55d89b93c0e8b7e99f3d1d |
SpaceCorps2027-windows-x86_64.zip |
6088c3ffef3580ff1d14697e5a5e6a41d679c5f535faef7afe9a5eef0f2a0984 |
SpaceCorps2027-linux-x86_64.AppImage |
791fbd2cb3f2a842dc9ed34557be948795117685f6117aec13d6d67906fe82f9 |
SpaceCorps2027-linux-x86_64.tar.gz |
d88551a7a0c01bca426aea6d8d187930d93e5216c38cfae27341640accc1c966 |