Repository navigation
SpaceCorps 2027 0.5.10 makes Davidski's Nightmare much harder, gives the clan dungeons a third Phantom's Lance illusion and a lower bar for the reward, lets a Clan Warden keep its whole hull and shield whatever the size of the crew, doubles the Skylab's kills without making its hull wear out faster, and shows the kick, mute and ban notices in the Global chat. It also keeps a pilot's number and an alien's id apart. For chat and Premium it adds emoji and coloured messages for Premium pilots, an emote wheel, a gold name for every pilot who has ever paid for Premium, 5 Chroma Archives with every 30-day Premium payment and a chat translation that is switched off until we switch it on. It also adds personal loot crates for groups, a chance of a free buff when the Forge tiers a piece up, the Dormant Keycard, and fixes for the readability of the flight HUD and for typed smileys. It also makes a new pilot tick a box for the Terms of Use and the Privacy Policy before registering, changes the Android app for Google Play's closed test, and changes the iOS app and the release job so that the iOS build can go to outside TestFlight testers.
It also takes some things away, and some of them are heavy. A small clan may not be able to beat a Clan Warden any more, the Nightmare is a run of about an hour and a half where it was planned as 45 to 60 minutes, and a clan dungeon party can no longer out-damage the Phantom's Lance heal until its illusions are dead. The Items and Formations wheels give one place to the emote wheel, so a page of the Items wheel holds one item fewer. The Premium wording of 0.5.9 ("no extra features") is no longer true and is replaced. A new pilot has to tick a box before registering, the Android app loses its Discord button, its crash report switch and plain http servers, and neither phone app has a link to the release notes any more (the iOS app also loses its news card). Each is described below under its own heading and again under Known limits.
The numbers below are the ones in the game files. They were worked out on paper, in the design models and in tests. Most of the changes of this release ran only in tests and in the models: people have not played them yet.
Download page: https://play.spacecorps.tech/
On Hangar: https://hangar.sliplane.app/p/spacecorps/spacecorps-2027
What's new
Highlights
- Davidski's Nightmare is much harder. Every ship of the gate deals 3 times the damage, Evil Davidski has 10 times the hull and shield, and he cannot be hurt at all while any golden ship lives. His rocket barrages fire Dormant Lances, the homing rockets that follow you.
- Phantom's Lance has three illusions in the clan dungeons (it had two).
- A clan dungeon pays at 0.1 % of the boss. A pilot is paid when he dealt 0.1 % of the boss's hull and shield (it was 0.2 % in 0.5.9).
- A Clan Warden keeps its whole hull and shield at any crew size. Its damage, its mending and its reinforcements still follow the size of the crew.
- Twice the Skylab's kills, at the same hull wear an hour as in 0.5.9.
- The kick, mute and ban notices are lines of the Global chat.
- A pilot's number is never an alien's id.
- Chat for Premium: 105 emoji and one of ten colours for a message, typed smileys drawn as emoji, no daily limit on emotes. A gold name in chat for every pilot who has ever paid for Premium.
- An emote wheel: hold N, slide to an emote, and it shows over your ship for the pilots around you.
- 5 Chroma Archives with every 30-day Premium payment (cosmetic cases whose prizes are looks), and once at the update for a pilot whose Premium is active and was paid for. A Premium from a rank reward or from the staff gives none.
- Personal loot crates for groups, cut by the damage each pilot dealt.
- The Forge: a tier-up has a 25 % chance to put one free buff into an empty socket.
- The Dormant Keycard for whoever claims the 20th Signal, and once at the update for whoever has claimed it.
- Chat translation, built and off until we switch it on: a line you pick goes to an AI model that we run on our own computer, or to Claude (Anthropic) for Hungarian and when that computer is not available, and you read it in your language.
- A readable flight HUD: the numbers on the bars and the phone's buttons and panels read over bright space.
- Registering needs a ticked box: "I am 18 or older and I accept the Terms of Use and the Privacy Policy". The Register button does nothing until it is ticked. Every build has it, in 13 languages. The Terms of Use are at https://play.spacecorps.tech/terms/, and the game links them from the Register card, Settings and About.
- The Android app for Google Play's closed test: links are written out as addresses because a link cannot open on Android yet, the start card says Early Access and has no Discord button, there is no crash report switch, and a server address must be https (localhost excepted).
- The iOS build for outside testers: the iOS app shows no news card and names no other place to get the game, and the release job can put the iOS build into a public TestFlight group of outside testers (Apple's review comes first).
New
- Davidski's Nightmare, the hard mode. The gate and its waves, its price and its pay are as in 0.5.9. What changed is the fight:
- 3 times the damage from every damage dealer of the gate: the Evil ships and their rockets, the golden ships, Evil Davidski's summons and his own lasers (7,800 to 9,600 a hit) and every move of his.
- 10 times the hull and shield for Evil Davidski: 5,500,000 hull and 6,600,000 shield.
- He cannot be hurt at all while any golden ship lives. Lasers, rockets, blasts and abilities do nothing to him and a lock-on on him is refused with the line the game already has. In 0.5.9 a fifth of the damage got through; that is gone, and the one-tick blow that could kill him through the protection with it. You have to destroy the golden ships first.
- His two rocket barrages fire Dormant Lances (homing, and they go through more of a shield than a Rivet does). The rockets of the Evil ships stay Rivets.
- What the model says it costs you: the day-one clear takes about 84 minutes (83.6) where the plan on the wiki is 45 to 60 and 0.5.9's model said 52, and the boss fight alone about 40 minutes (9 in 0.5.9). Clearing it in 45 minutes asks for about 1.8 times the output of the model's day-one pilot, and the boss's enrage, 8 minutes into his second phase, comes for a pilot who deals less than about 23,000 a second. The boss wave is not saved: a death, Leave or a restart in it brings him back at his full hull and shield, so one death can cost you the whole fight. Nobody has played it: the model's pilot cannot die, so whether a pilot survives 40 minutes of this boss is not known.
- Phantom's Lance, three illusions. The Warlord comes back with three illusions of 500,000 hull (two in 0.5.9). Each still fires half of its volley and heals the Warlord 50,000 hull and 50,000 shield a second, so the three heal 150,000 and 150,000 a second together (100,000 and 100,000 with two). No party gets through the heal while all three illusions live: a party needs more than 300,000 damage a second to reach the Warlord's hull, and the planning damage is 60,000 (party of 3) to 200,000 (party of 10). Destroy the illusions first. A party of 5 needs about 15 seconds to kill the three (10 seconds for two). At stage 1 the volleys of the three illusions alone take about 34 seconds to kill a stock pilot of 700,000 hit points (about 51 seconds with two), by the model's mean volley of the boss. The in-game hint and the wiki say three, in 13 languages.
- Clan Warden at full strength. A Warden's hull and shield (the leader, its escorts and its drones) are the numbers of the file at any crew size. Its damage, its shield recharge, its mending, its rockets and its reinforcements follow the table of the crew as before (for example 16 % with five pilots present). The chat line when a Warden arms says it: "Crew present: 5. Brood Warden II has its full hull and shield. Its damage, mending and reinforcements are at 16%." The Tesseract never scaled with the crew and is unchanged. In the model, a crew of 13 pilots or fewer no longer wins any Warden inside its 40 minutes (nine Wardens with 3, 5, 8, 13, 20 and 37 pilots present make 54 cases: the old rule won all 54 inside the 40 minutes, the new rule with the table unchanged wins 3, Siege Warden III with 20 and with 37 pilots and Brood Warden III with 37; the model's pilots never respawn and the game's do, so this is a bound, not a play). The Warden's wiki section is rewritten in 13 languages.
- Skylab: twice the kills, the same hull wear an hour. The aliens that come by and the kill budget are doubled, and so are the Defense magazines and the Trophies Bay, so that a trip lasts as many hours as before. A kill costs the Skylab's hull half of what it cost (
hull.lossPerKillFactor0.5 inExpedition.json, 1 when the key is missing), so with twice the kills the hull a Skylab loses an hour is what it was in 0.5.9. The preview's "Destroyed after" and the damage a cell asks are unchanged. Pay, loot, experience and honor stay per kill and so double with the kills; the quest limit of 250 kills a day is unchanged. A kill also fires its rounds, so a magazine of a fixed number of rounds lasts half as many hours: a full Defense magazine lasts as long as before, a half full one half as long. A Skylab that runs dry before its hull would go stops fighting and mends; it is not destroyed (the preview tells both numbers: "Destroyed after" is the hull's, "Ammo lasts" the magazine's). - Chat: the sanction notices. "{name} was kicked / muted / banned by an admin." is a line of the Global tab now, in the server's colour, with no sender. It counts as unread in Global, the station's bar shows it, and Hide Global hides it. The pilot's own lines and the mute's refusal are as before.
- Chat for Premium: emoji and colour. A pilot with an active Premium can put emoji in a message (105 pictures, written like
:fire:) and give it one of ten colours. Everyone sees the picture, and a pilot without Premium who types the same sends the text. Names and channels keep their own colours. A smiley button beside the chat box opens the picker; a pilot without Premium sees it locked where the build allows it. A new switch, Show others' colours and emoji (the chat window's menu, and Settings, Interface), turns it off for you: every line is drawn plain. Typed smileys (a list of 29, such as:),xD,<3,;)andB)) are drawn as emoji for a Premium pilot who reads them; a free pilot, and a pilot who turned the switch off, sees the typed text. The pictures are Microsoft's Fluent Emoji (MIT). - The gold name. A pilot who has ever paid for Premium has a gold name in chat, for good, also after that Premium has ended. A Premium that came as a wipe reward or from the staff does not make a name gold, and gold gives nothing in play. A pilot who paid before the update gets the gold name at the update (only live payments count, never a test payment). Every chat line now carries two flags: whether the sender has ever paid for Premium (the gold name) and whether the sender's Premium is active at that moment (the emoji and the colour are drawn only then). The name over a ship, the online list, the group panel, the kill feed and the Target window do not show gold. A game from before 0.5.10 reads the lines as before.
- The emote wheel. Hold N (Settings, Controls changes it) and slide to one of sixteen emotes: it shows over your ship for three seconds for the pilots around you. A pilot has ten a day with a pause of three seconds between two; a pilot with Premium has no daily limit, and the count follows the start and the end of Premium at once. On a gamepad press the right stick and choose Emotes; on a phone choose Emotes on the Items wheel (a phone on the Hotbar has no way in yet). The Items and Formations wheels now carry an Emotes wedge on every page, so a page of the Items wheel holds one item fewer. Settings, Interface, Show other pilots' emotes hides the others'. A server can switch the wheel off (
EMOTES_ENABLED); it is on. - Chroma Archives with Premium. Every 30-day Premium payment (a purchase of either Premium product and each monthly renewal) also gives 5 Chroma Archives, the cosmetic case whose prizes are all looks (skins, colours, exhaust effects, auras). When you already own every look of a grade, an opening of that grade pays Thulium instead (25 to 4,000 an opening, by grade). A pilot whose Premium is active and was paid for gets 5 once at the update. A Premium that came as a wipe reward (a rank reward) or from the staff, the 1 Day pass, and a payment made with Stripe's test keys give none. The other four containers are not given. The Premium card and the Thulium page of the direct downloads and the web version say it in 13 languages, with the odds and the guarantee on the Containers page; the Steam and phone builds have no such card.
- Chat translation (off until we switch it on). Right-click another pilot's line, or a private message you received, and choose Translate: the text of that line (at most 200 characters) and the language you read go from the server to an AI model that the developers run on their own computer, or to Claude (Anthropic) for some languages (Hungarian today) and when that computer is not available. The result shows under the line, marked as a machine translation by an AI model; only you see it, it can be wrong, and you can hide it. No name and no id is sent, and nothing is kept on disk. A pilot has 20 translations a day, 200 with Premium, and the same line asked for again within 24 hours (by anybody) comes from a copy kept in the server's memory and does not count against the day. The translation service has a daily budget of its own: when it is used up, the game says the translation did not work. It works only when we set a translation provider on the main server, and we do not before the privacy page and the store disclosures name it. A game or a server from before 0.5.10 shows no Translate item.
- Personal loot crates for groups. When two or more pilots of a group damaged an alien or a swarm boss and the group holds the kill, its loot is cut into one crate for each of them by the damage they dealt. A crate is its pilot's alone for 30 seconds, then free for everybody. A pilot alone, or the only damager of his group, gets the one crate for him and his clan as before. A group mate who dealt no damage, or who died or left the map before the kill, gets no crate. The aliens of a clan dungeon count too: the crates go to the group of the pilot who dealt the most among the pilots the clear pays, and a clan mate outside that group is paid as before and gets no crate. The aliens of the solo gates and rifts lay nothing at the kill and still do not. Credits, Thulium, experience and honor are paid as before. Loot is never copied: what cannot be shared evenly (one plate among several pilots, a unique piece) goes to one pilot, drawn by chance in proportion to the damage. This also repairs the private boxes of the Clan Warden and the Tesseract, where one kill could lay the same plate in two boxes or in none: their loot is rolled once a kill and cut between the pilots (the Dark Matter cap of 5 a pilot stays). The luck of that roll is the paid group leader's loot luck, so a group mate's own loot booster no longer lifts his own Warden or Tesseract box.
- The Forge: a free buff. A tier-up has a 25 % chance to put one free buff into an empty socket of the piece, on a random stat at the strength of the tier it just reached, at no Echo Shard, Lattice Shard or integrity. The Tinkerer's Badge rolls it on its free tier-up. A free buff counts as a tuned socket, so the next tune costs the next socket's price: a full piece needs about a quarter fewer Echo Shards (112.5 instead of 150 for four sockets when each is tuned as it wakes; about a tenth fewer, 135.6, when the sockets are left empty and tuned together at the top). Fractures can still take points off a free buff. The Upgrade view states the chance and names the stat and the value when one landed.
- The Dormant Keycard. A purple keycard with infinite uses, yours when you claim the 20th Signal. You can hold one: if you already have one, the claim still works and you get no second. It cannot be sold or thrown away, and a wipe does not take it. It opens nothing yet: a later update will use it to enter a new map. A pilot who claimed the 20th Signal before this update gets the card once when the server updates. A new wiki page about the Signals is in 13 languages.
- The Terms of Use tick box. The Register form has a box under its fields (under the Link to my Steam account switch in the Steam build): "I am 18 or older and I accept the Terms of Use and the Privacy Policy." The two names are links where links open, which is every build but Android (there the two addresses are written out under the box: see Changed). The Register button is off until the box is ticked, Enter in a field sends nothing either, and a line under the button says "Tick the box above to register." Log In never waits for the box. The box is never remembered: it is off each time the Register form opens and each time you switch between Log In and Register. It is in every build (Windows, macOS, Linux, Steam, the web version, Android and iOS) and in 13 languages. The tick is checked in the game only: the server is not told and keeps no record of it, and a game from before 0.5.10 has no box. The Terms of Use are https://play.spacecorps.tech/terms/, a page on the site's new host; the Privacy Policy is https://play.spacecorps.tech/privacy/ (0.5.9 linked the site's old address for it, which now redirects here). Both are also linked from Settings, Privacy and from About, More in every build; the privacy link under the sign-in card is as before. The pages are published by the site, not by this release.
Changed
- The Premium wording. 0.5.9 said "Premium currently gives no gameplay advantage and no extra features: it shows a Premium badge on your pilot." The Help card now says what Premium gives: a Premium badge, emoji and coloured text in chat, no daily limit on emotes, a larger translation allowance (when a server translates), and the Chroma Archives, with a row for each. The Containers page says "none is sold on its own", where it said "nobody sells them". The sentence "no gameplay advantage" is now "Premium does not make ships stronger" in the Help card, the Thulium page, the emoji picker's lock and the Premium notices, in 13 languages: a pilot who already owns every look of a grade gets Thulium from an Archive, so the older sentence was no longer strictly true.
- A readable flight HUD. The bars of the flight HUD (target and ship, phone and desktop) draw their numbers in dark ink on the bright green and blue fill and in light ink on the empty part, so 764 / 800 reads across the edge. The phone's buttons, chips, item picker and panels are darker behind their text; because of that the phone's panels follow the HUD opacity slider like the windows do (less see-through at 84 % and below). Rock names over the map are no longer dimmed, the experience feed's text has a darker outline and the minimap's grid letters are a little brighter.
- Clan dungeons: the share that pays. A pilot is paid when he dealt 0.1 % of the boss's hull and shield (0.2 % in 0.5.9, 2 % before), or destroyed 10 of the dungeon's aliens, or healed other pilots for 50,000 during the fight with the Warlord. The other rules stay (he must not have pressed leave and stayed away, at least 2 minutes inside, one paid clear of a stage a day and 10 a week). It is a number in the dungeon file (
bossShare0.001); of a boss with 18,000,000 hull and shield (stage 1, a party of 5) 18,000 pays and 17,999 does not. Nobody has measured what this does to the rewards. The wiki follows it in 13 languages. - Davidski's Nightmare texts. The cue says that he cannot be hurt while a golden ship lives, in 13 languages. The Nightmare's rows of the wiki tables of the Solo Gates article carry the new numbers in 13 languages. The article's prose about the Nightmare (what Evil Davidski does and that he cannot be hurt while a golden ship lives) is English only: the 12 translations of the Solo Gates article are older than the Nightmare's prose, as they were in 0.5.9, and the wiki says so on each of them.
- The Android app (the game's part of Google Play's closed test). Five changes, all in the Android build only; every other build is as it was.
- Links are written out. A link cannot open on Android yet: the game starts a program that no phone has, and the app has no way to ask Android to open a page. So where the other builds show a link, the Android build shows the address as text to read and type into a browser. That is the two pages under the Register box (with the line "Links do not open in this app. Read both pages in a browser:"), the Privacy Policy under the sign-in card, the Privacy Policy, the Terms of Use and Discord in About, More, and both pages in Settings, Privacy. There is no Copy button: the Android build has no way to reach the system clipboard, and the button is drawn only where it has one.
- The start card says Early Access and has no Discord button. It says what the Steam build says ("Early Access", not "Private Beta" and not "Join Discord for Beta Access"), and its Discord button is left out. The Steam build keeps its "Join our Discord" button and the direct and web builds keep the Private Beta card.
- No crash report switch. Settings, Privacy has no Send Crash Reports switch on Android and the setting reads as off, so no crash report is sent from an Android phone. A report the engine saved stays on the phone and can be deleted in Settings.
- A server address must be https, except for localhost, 127.0.0.1, [::1] and names ending in .localhost (so a developer can still try a server on the same computer). An address typed with no scheme gets https://. A typed http:// or ws:// for any other host is refused with "Plain http:// works for localhost only. Use https://." (13 languages). A plain http address that an Android pilot saved earlier, for a host that is not the computer itself, is ignored at the next start and the game uses the public server.
- No link to the release notes on either phone. About, More on Android and on iOS has the Privacy Policy, the Terms of Use and Discord, and no link to the website (already so in 0.5.9) or to the release notes (new).
- The iOS app for outside testers (the game's part). The changes make the app fit the two App Review rules that the lane read from Apple's guidelines: no purchase offer (3.1.1) and no other place to get the game (2.3.10). No build has gone to Apple's Beta App Review yet.
- The Dashboard has no news card and the app does not ask the server for the news list: the posts name the download page, Hangar, Steam, the web version and Android.
- About, Software Update is one line, "Updates come through TestFlight", with no button, switch, release notes, Hangar or download page; the update notice is never drawn; the About header names the system "iOS" (it showed the build target "aarch64-apple-ios").
- Invite Friends, Copy invite message leaves the download address out, as the Steam build's does; the Invite Friends wiki article says so in 13 languages.
- The start card keeps "Private Beta" and its Discord button says "Join our Discord" (it said "Join Discord for Beta Access").
- The Steam account card of a pilot who linked from Steam no longer says, on iOS, where linking is done.
- What the app declares: no purchase offer (no Premium button or card, no Restore Purchases, no checkout link, no Thulium offers; a pilot who has Premium still sees "Premium Active" in the top bar), and no use of non-exempt encryption (
ITSAppUsesNonExemptEncryptionfalse in the app's Info.plist; the client carries its own TLS library next to the system's, so the answer is confirmed in App Store Connect; the release job's external step sets it to false only for a build that has no answer yet). Both were already so in the 0.5.9 tree. - The export is no longer internal-only:
testFlightInternalTestingOnlyis false inmobile/ios/ExportOptions.plist. An iOS build exported with it true can never go to outside testers, and every iOS build up to 0.5.9 build 2611181955 is such a build: outside testers get the build of this release.
Fixed
- Typed smileys were refused as spam.
:),;),:D,<3and^_^now go out in Local, Global, Group, Clan and private messages. - Gift toasts named the id. The toast of a gift of a special item says the item's name.
- Not a change in play, but now tested: when an alien, a boss, a Warden or a computer-controlled ship lands the final hit on a pilot, no other pilot gets a PvP kill for it.
- Pilot numbers and aliens' ids. A ship in the sky uses its pilot's number as its id, and an alien made by a map's own spawner had a random id from 100,000 up with no check that it was free, so an alien could take a pilot's place on a map. Now an ordinary alien never has a number a pilot's ship has, and a ship never takes an alien's id: the ids are drawn free on the map, the ones that clash are given another id (once a second for a pilot who is on another map), the rockets in flight follow a moved alien, and something that cannot be moved (a swarm member, a station) that has the pilot's number refuses the ship with the line the game already has for a world change ("try again in a moment"). An old client shows that line. See Known limits for what stays.
For the release job
- TestFlight upload. With an App Store Connect API key the job sends the signed iOS build with
altool(Xcode's own upload answered "Account credentials have expired" on the Mac mini, where Xcode has no account), andtestflight.sh validateasks Apple whether it takes a build. The upload step of the job itself has run only against stand-ins: its first real run is this release. - External TestFlight testers. After the upload, the Mac mini runs
testflight.sh external(scripts/mobile/asc-external.py: the App Store Connect API over https, signed with the same API key, no Apple tool). Each step reads what App Store Connect has first and writes only what differs, so a second run changes nothing. In this order it:- finds the app, and checks the build's audience before any write: a build that is listed already as internal-only or expired is refused (exit 14) and nothing is changed;
- makes the external group "SpaceCorps Testers" if it is not there, with its public link on, feedback on and a limit of 1,000 testers on the link (a group that exists keeps the limit it has);
- sets the Beta App Review details from the owner's contact file (the contact, no demo account required), and the beta app description and feedback e-mail from the same file, also for any other language of the description that has none;
- waits for Apple to process the build, up to 30 minutes, and answers the export compliance question (no non-exempt encryption) only when the build has no answer yet;
- writes the build's "What to Test":
SpaceCorps 2027 <version> (build <number>).followed by thewhatToTesttext of the owner's contact file (it is not taken from these notes); - puts the build into the group;
- sends the build to Beta App Review, unless it or an earlier build of the same version is already waiting, in review or approved;
- prints the group's public link.
- When it runs, and what it never does. It runs only when the job's phone step is switched on for iOS, the owner's review contact file
~/.spacecorps-asc/review-contact.jsonis on the Mac mini (never in git; the template isscripts/release/review-contact.example.json, and a file that still has its template values is refused) and the API key is in the Mac's settings file; otherwise it is skipped with one line in the job's log.AUTORELEASE_IOS_EXTERNAL=0switches it off. It never fails the iOS lane or the release: its outcome is one line in the log and inexternal.txt("done" with the public link, "skipped" with the reason, or "failed" with the exit code and the reason), and a build that Apple refuses (exit 14) or that is not processed in 30 minutes (exit 16) is not tried again by the job. It does not wait for Apple's review and does not read its result (testflight.sh external --statusdoes), and it never submits the app to the App Store. - What it sets on every run. The group's public link on, feedback on, and "demo account required" off. So a public link that the owner switched off in App Store Connect is switched on again by the next release, and a demo account entered there is set to "not required" (its name and password stay). An owner who wants other values switches the step off and does the rest by hand.
- The Steam upload's executable check (
scripts/steam/check-exe.py) knows both hosts of the site,spacecorps.github.io/playandplay.spacecorps.tech, and allows only two pages on either:/privacy/and/terms/. Any other address of the site in the Steam executable (the download page, a Premium page, the site's root) fails it, as before, and a normal build must still carry the download page's link.
Servers and privacy
- The server and the game go live together, on all three servers. Home (Helsinki), Singapore and US East must run the same build. A regional server that is not the same build as Home is shown as updating and takes no flights, and this release also changes the wire spec of the pilot's copy that Home lends it (the new column
Players.IsSupporter; the spec's hash was 6e05f85d in 0.5.9 and is ae20a2f1 now), so a server that runs the other spec is refused by Home with a 409 and the three must be updated together, not one by one. - Two data steps and three new columns, no new table. They are listed under Data steps and schema below, with what the release job prints for them. The data steps run on Home only. The new key
hull.lossPerKillFactorof the Skylab is a file the server reads at start. - The update moves no Credits and no Thulium and takes nothing from a pilot. It gives the Dormant Keycard, the 5 Chroma Archives and the gold name described above.
- Chat translation sends text to a third party once it is switched on. It is off in this release until the developers set a provider on the main server (
TRANSLATE_PROVIDERS). Then the text of a line a pilot chooses to translate (at most 200 characters, with the language he reads, no name and no id) goes from the game's server through our own translation service (hosted at Sliplane) to an AI model that the developers run on their own computer and, for Hungarian and when that computer is not available, to Claude (Anthropic, United States). No other translation service is set up. Nothing is written to disk by the game's server; a translation is kept in its memory for up to 24 hours, and the server counts the translations a pilot used a day, without the text. We do not set the provider until the privacy page and the Steam AI disclosure say this; the draft of the privacy text is indocs/privacy-addendum.md. - What the chat shows of a pilot. The gold name shows that a pilot has ever paid for Premium, to everybody who can read the chat, and each line shows whether his Premium is active at that moment. A regional server's copy of a pilot carries the gold name's yes or no and nothing else of his payments.
- The pages the game links. The Terms of Use (https://play.spacecorps.tech/terms/) and the Privacy Policy (https://play.spacecorps.tech/privacy/) are pages of the public site, not of the game's server. The game does not fetch either page: a browser opens it when a pilot clicks the link, and an Android pilot types the address. The Register tick box is not sent to the server and nothing about it is stored. The Terms, Android and iOS changes touch no server file.
- Apple, for the iOS testers. When the external step runs, the contact, the beta description and the feedback e-mail of the owner's file go to Apple through App Store Connect (and the privacy policy and website addresses, if the file names them). The job sends nothing about a pilot.
If you already play
- Update the game; the server and the game go live together. A game from before 0.5.10 flies as before and shows the kick, mute and ban notices the way 0.5.9 did. It shows no gold names, no emoji or colours, no emote wheel and no Translate item.
- At the update you may get: the Dormant Keycard if you have claimed the 20th Signal, 5 Chroma Archives if your Premium is active and was paid for, and a gold name if you have ever paid for Premium. Nothing is taken from you.
- A Nightmare run you have open keeps its saved wave. The boss wave is not saved: if you are in it when the server updates, you start that wave again against the new, harder boss.
- A Skylab that is out on a trip keeps its stored schedule; the stretch since your last look is paid at the new rates (twice the kills) within the Bay's new room and the hull of the row.
- The tick box is on the Register form only. A pilot who logs in is asked to accept nothing, and nothing is stored about it.
- On Android, a plain http server address saved earlier (any host but localhost) is ignored at the next start and the game uses the public server; type the address again with https://. There is no Discord button on the start card (its address is in About, More) and no crash report switch.
Data steps and schema
The release job compares the server's code of 0.5.9 and of this release. Run in the release tree as source scripts/auto-release.sh && backup_risks v0.5.9 HEAD, it printed exactly these five lines:
data step keycard-signal20-v1
data step premium-cases-v1
schema ALTER TABLE CLANCHAT ADD COLUMN COLOUR
schema ALTER TABLE CLANCHAT ADD COLUMN FLAIR
schema ALTER TABLE PLAYERS ADD COLUMN ISSUPPORTER
These are steps the server runs once, by itself, at its start. The job prints the names in capitals for the schema lines. What each line means:
data step keycard-signal20-v1: gives the Dormant Keycard to every pilot who has claimed the 20th Signal and holds none. One transaction with its row inDataMigrations; a pilot who holds a card is skipped, so nobody gets a second. The log line isData step keycard-signal20-v1: N pilots who had claimed Signal 20 got the Dormant Keycard, M more held one already. Home only.data step premium-cases-v1: gives 5 Chroma Archives once to every pilot whose Premium is active now and was paid for (the gold name's flag is set). One transaction with its row inDataMigrations, and the gift has its own key in the containers' ledger (premium-backfill-v1), so a lost row still gives nothing twice. A Premium that came as a rank reward or from the staff gets none. The log line isData step premium-cases-v1: N pilots with an active, paid-for Premium got 5 Chroma Archive each; M pilots with an active Premium that was never paid for got none. Home only. It needs the container catalogue and its switchgrantSources.premium: without them nothing is written, the step logs it and runs again at the next start.schema ALTER TABLE PLAYERS ADD COLUMN ISSUPPORTER: the columnPlayers.IsSupporter(a yes or no, the gold name), made when the table lacks it, 0 for every pilot. A fill follows it: a pilot whose payment history holds a live Stripe Checkout session (cs_live_) is set to 1. It runs at every start and flags a pilot once; a test session (cs_test_) does not count, and nothing clears the flag. This column is in the wire spec that Home and the regional servers compare, which is why the three servers must run the same build.schema ALTER TABLE CLANCHAT ADD COLUMN FLAIRand... COLOUR: two small numbers a kept clan chat line holds for the gold name, the emoji and the colour. Empty (NULL) for every older line.
The columns are made when the server opens its database, each only when the table lacks it, so a second start changes nothing; a regional server makes them too, empty. They are additive: a server of 0.5.9 ignores them on the same file. The data steps need no table of their own.
Updating
- From a recent version: the game downloads a patch by itself when the job made one for your version. Click Restart to Update, or quit the game, and it installs. If a patch cannot be used the game downloads the whole package. A Linux AppImage game gets a patch from a newer version than the other packages.
- From an older version: the game downloads the whole package. If you installed the game with Hangar, Hangar updates it.
- From 0.2.0: download it once from the download page and replace the old app or folder.
- What the update does to your account: nothing is taken. It moves no Credits and no Thulium; it can give you a Dormant Keycard, 5 Chroma Archives and a gold name (see "If you already play").
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 |
SpaceCorps2027-windows-aarch64.zip |
Windows 11 on Arm (Snapdragon X and similar), 64-bit |
SpaceCorps2027-linux-aarch64.AppImage |
Linux ARM64, glibc 2.35 or newer, Vulkan |
SpaceCorps2027-linux-aarch64.tar.gz |
the same Linux ARM64 build, as a folder to unpack |
SpaceCorps2027-android-aarch64.apk |
an early-access Android APK for 64-bit ARM phones and tablets (Android 9 or later), signed with SpaceCorps' own key and installed from the file, with no store |
The Android APK is attached only when the release job's Android step was switched on and finished in time. If it is not among this release's files, this release has none. The APK does not update itself (the updater is off on phones): a newer version is a new file.
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 at the least and 8 GB is recommended. It needs 400 MB of free disk space. On computers with 8 GB, Medium or Low uses noticeably less memory than High. The web version at web.spacecorps.xyz needs a browser with WebGPU or WebGL2. The Android and iOS apps are works in progress and neither is in a public store. The early-access Android APK in the table, when this release has it, is open to everyone. The iOS app is open to outside testers only through TestFlight's public link, and only when the release job has run its external step and Apple's Beta App Review has passed the build (see "For the release job" and Known limits).
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: the whole game is in that one file. 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 limits and open points
- Nobody has played the new features. What ran: the tests written with each change on the branch of that change; the design models' own checks (
--checkof the models for the dungeons, quests, market, mines, modules, research, ships, forge shards, swarms, special items, solo gates, achievements, clans, gate categories, chat, containers, cosmetics, wipe rewards, login calendar and pilot skills, all of them on the merged tree; the containers and chat models again after the last change); and the release job's own gates on the integration headc16470a99(fmt, clippy, i18n, the dungeon model and the whole test suite all passed there; clippy found no warning in the game crates and 156 in the server, which the job only counts; the whole suite had 37 failures: 33 of tests the job already lists as failing on Windows, and 4 server tests that fail under load and passed when run again alone, by the job and again by hand). After that head the integration changed only the wording of the Containers wiki page (13 languages, with its phrase books), a comment inflight/spec.rs, the privacy addendum and these notes. The server's wiki, wire-spec and supporter tests (176 tests) and the client's wiki tests (233 passed; one failure, a table test that is on the job's Windows list) ran again on that tree; the job's own gates were not run again on it. Three more lanes were merged after that (the Terms tick box with the Android changes, the iOS client, and the iOS external testers in the release job), and with them the client's code for sign-in, About, Settings, the start card, the update notice, the news card, the clipboard and the server address check, the language files of all 13 languages, the release scripts and the Steam executable check; the head after those merges is007a88703. No server file changed. On that tree these ran: the formatting check of the three client crates (passed);cargo checkof the three client crates with all targets (no error, no warning); client tests picked by area (build rules, legal pages, sign-in, start card, About, Settings, server address, language files, news, invites, Steam card, update notice, clipboard, menu): 789 passed and 2 failed, both failures on the job's Windows list;scripts/release/tests/test-asc-external.sh(53 passed, run again for this note),test-mobile.sh(210 passed) andtest-mobile-ios.sh(184 passed; one earlier run had 1 failure, the check that the heartbeat ran while the step waited, a race in the test that passed on the next two runs); and the Steam script tests andtest-changes.sh, which fail on this Windows PC (the Steam script tests failed 115 of 455 checks in the merge run and 122 in a second run, mostly because a helper cannot find python3; none of the failures is about the site hosts, and the new cases for them passed; the merge run found the same failures on the head before the merge;test-changes.shfailed 1 of 94, ased -isyntax difference on Windows). The job's own gates were not run on that tree: not clippy, notscripts/i18n.sh check, not the dungeon model check and not the whole suite. The release job runs them again on the final tree, and a clippy warning in the game crates would stop it. No real client was played against a real server for the hard mode of the Nightmare, the three illusions, the Warden's whole hull, the doubled Skylab or the Global chat notices, and none of the three new lanes was looked at in a real window or on a phone: the Register box, the Android and iOS screens were drawn headless by tests only. - What got weaker or harder (each was ordered on purpose; the consequences were measured in the models and are not changed):
- Davidski's Nightmare: about 84 minutes for a day-one clear in the model (the wiki's plan says 45 to 60), a boss fight of about 40 minutes, and a boss wave that is not saved. The model's scripted pilot cannot die, so whether a real pilot survives it is unknown: the hardest single blow is 315,000 (45 % of a stock pilot's hull and shield) and the peak fire 44,900 a second against the 20,000 limit of the gate's model. A Dormant Lance barrage homes, so the real intake is above the model's. The plan on the wiki still says 45 to 60 minutes until we choose one of the options in
docs/design/davidskis-nightmare.md(a longer plan and enrage, a smaller multiplier, or a checkpoint at the change of phase). - Clan dungeons: with three illusions no party out-damages the Phantom's Lance heal (150,000 hull and 150,000 shield a second) while all three live; a party of 5 is at a third of the damage that would pass it. The model does not read the heal: while a party kills the illusions one by one the Warlord can win back up to 3.0 million of hull and shield a cast at a party of 5 (5.0 million at a party of 3), which is about 30 seconds more at a party of 5 and 83 at a party of 3 for each cast. The whole run takes 19.1 / 24.6 / 32.2 minutes at stages 1 / 2 / 3 for a party of 5 (34.2 minutes at the longest, stage 3 with a party of 3) in the model, which does not read the heal; the time limits are 95 / 130 / 165 minutes.
- Clan Wardens: a small crew meets a Warden with its whole hull and shield and only its damage, mending and reinforcements scaled down. In the model this loses 51 of 54 cases, so a small clan may not finish the clan line (step 5), the Warden achievements (
warden_1,warden_all) and the quests The Bestiary and Subject You. The options the clan model lists (a table for whole hull and shield, floors for the damage and the mending too, a longer time limit) are not chosen. - Skylab: a Skylab whose lasers or magazine limit its kills loses less hull an hour than in 0.5.9, down to half of it, and is never destroyed sooner. A magazine of a fixed number of rounds lasts half as many hours. The preview's "Destroyed after" is the hull's alone and does not clip to the hours the rounds last: it can show a longer time than "Ammo lasts" for a stay that the rounds end. The doubled kills fire twice the rounds an hour: the model's rule that a level 15 Ammo Printer on x2 (3,000 rounds an hour) makes more than the reference kit burns at any tier holds, but a smaller Printer (level 5 makes 1,000 an hour on x2) or the x3 and x4 modes were not checked against it, so auto-feed may not fill a magazine as fast as the kills empty it.
- Registering and the phone apps: a new pilot cannot register without ticking the Terms of Use box (every build). The Android app has no Discord button on the start card, no crash report switch, and takes a server address that is not https for localhost only (a plain http address saved earlier is dropped at the next start). Neither phone app links the release notes, and the iOS app has no news card. Written-out addresses on Android must be typed into a browser by hand.
- Davidski's Nightmare: about 84 minutes for a day-one clear in the model (the wiki's plan says 45 to 60), a boss fight of about 40 minutes, and a boss wave that is not saved. The model's scripted pilot cannot die, so whether a real pilot survives it is unknown: the hardest single blow is 315,000 (45 % of a stock pilot's hull and shield) and the peak fire 44,900 a second against the 20,000 limit of the gate's model. A Dormant Lance barrage homes, so the real intake is above the model's. The plan on the wiki still says 45 to 60 minutes until we choose one of the options in
- Pilot numbers and aliens' ids. What stays after this release, for a pilot whose number is 1,000,000 or more: a swarm member, a station or a portal that has his number on another map of his world cannot be moved, so his ship is refused with "try again in a moment", and the cause lasts for minutes (members) or for ever (the portals, clan gates and stations that have fixed ids: 2,000,000 and up). A non-ordinary entity of the pilot's number on a map that is looked at before his ship's map is still taken for the ship by the lookups. A ship whose pilot number is 5,000,000 or more still cannot be shot at with a targeted attack (the rocks' ids start there). The sweep that gives an alien a new id when it has the number of a pilot on another map runs once a second, so a clash can last up to a second. All of it was tested in the server's tests through the real ticker, never with a real client, and no live pilot number was looked up.
- Chat. The notices are Global lines: a pilot who has hidden Global does not see them.
- Chat and Premium. The emoji and colour pickers, the emote wheel, the gold name, the typed smileys, the Chroma Archives of a payment, the loot crates of a group, the Forge's free buff and the Dormant Keycard ran in tests and in the design models, not in a game that people played. The emote wheel's layout on a phone, beside the emoji picker, was not seen. A phone on the Hotbar has no way into the emote wheel yet. A refunded Premium payment keeps its days and its 5 Chroma Archives: nothing in the game reacts to Stripe's refunds. If the Archives of a payment cannot be given (the switch
grantSources.premiumis off), the payment is still fulfilled and the log names it, and nothing gives them later by itself: an administrator gives them by hand. The pilots who get the 5 Archives at the update are counted by two facts, an active Premium and a payment ever made; a pilot who bought only the 1 Day pass, which is no longer sold, and still has Premium is counted. On a server that uses Stripe's test keys, a renewal invoice of a test payment is not recognised as a test and could set the gold name and give 5 Archives; a server with live keys is not affected. - The wiki in the Steam and phone builds. The wiki is in every build. Its Containers page now says that Premium brings 5 Chroma Archives with every month of it and names no payment; the Premium card and the Help card of the Steam and phone builds say nothing of it. Whether that fits our answer to the Steam questionnaire about random items is to be read again before the Steam upload (
docs/STEAM_CLAIMS.mdis not updated). - Chat translation. It is off, and the server's tests ran it against stand-ins: no real translation proxy, model or Claude key took part in the checks this note describes. An AI model's translation can be wrong; the game's output guard looks at the shape of an answer (a line break, quotes, an explanation, a length far above the line's) and not at its meaning, and no moderation model checks it. The proxy's daily budget is the key's: when it is used up the proxy refuses every request of the key, the local model too, and translation stops for all languages until the UTC day turns. A private message can be translated by the pilot who received it; the sender is not asked. We have not yet checked what Anthropic keeps of the text it receives and whether it may train on it, whether the home computer or the tunnel in front of it keeps a copy, or that the translation service's own message log is off in the running service (it is off in its settings file). The privacy text and the Steam, Apple and Google forms that name AI come before we set the provider.
- Loot crates of a group. A group's crates go to the party of the single top dealer, not to the party with the most damage in all: a group of three that dealt 20 % each loses the loot of that kill to a pilot alone who dealt 25 %, and the group is paid by its share as before. Whether every pilot who damaged the alien should get a crate, whatever his group, is not decided. The crates lie in a pool of 128 a map apart from the 64 other boxes, so a dense pack that a group clears before it collects can lose its first crates after the 3 minutes a crate lies. The Forge shard model assumes that a pilot takes about three fifths of his even part of a dungeon alien's box (marked as an assumption); with crates reserved for 30 seconds he takes more, so the Echo Shards from dungeon aliens may go up. We did not change that model.
- A pilot who dies to an alien. When an alien destroys a pilot, no other pilot gets a PvP kill for it (tested, no change). A second reading of that rule is open: a pilot who dies to an alien in the same tick in which his own shot destroys another pilot gets no kill for that shot, and a rocket of his in the air at his death hurts nobody. Both are as they were; we have not decided whether they should change.
- The emoji pictures in the packages. The 105 emoji are one picture file (
assets/icons/emoji/atlas.png, about 100 KB). That the web, Steam and delta packages carry it was read from the code, not from a built package. - The Solo Gates article in the 12 other languages has the Nightmare's table rows with the new numbers but not the Nightmare's prose, which is English only: those translations are older than it, as in 0.5.9.
- The Dormant Keycard opens nothing yet.
- The release job's TestFlight upload and its external step have run only against stand-ins. Not one call was made to the real App Store Connect. The external step's 54 tests run against a stand-in server written for them (
scripts/release/fake-asc-server.py), and the shapes of Apple's calls were read from Apple's documentation, not seen on a real call. Unsure until the first real run: whether the group's list of builds shows the build right after it is added; which order Apple wants for the group and the review submission (the step handles both); how soon a new build is listed and what state it is in after it joins the group; when the public link is filled in (the step then prints that it has no address yet); whether Apple's review accepts "no demo account" for a game that needs a sign-in (the contact file's review notes can say how to get in); and whether the Mac's ownopensslsigns with the key (the tests used OpenSSL 3 on Windows).altooldoes not send the dSYM files (not checked), so crash reports in App Store Connect may be unsymbolicated. - Apple's review is Apple's. Until Beta App Review passes a build, the group's public link exists but installs nothing (as Apple documents it, according to
docs/MOBILE.md). A rejection is mailed and shown in App Store Connect; the job does not poll for it and does not send a build again that Apple refused. A TestFlight build expires after 90 days. Nobody has run the iOS app on a real iPhone: an outside group will meet phones with 2 to 3 GB that may end the game while it loads. Left on purpose: Settings, Privacy's crash report sentence names GitHub (SpaceCorps/play), the Achievements wiki article names Steam, and a pilot who linked a Steam account still sees the Steam account card. - The Terms tick box is the game's own check and nothing more. The server keeps no record of who ticked it or when, a game from before 0.5.10 registers without it, a pilot can say he is 18 or older without any proof, and the web version has the box once the web page of this release is published. The Terms page and its text are the owner's, on the site, not in this release.
- Android: links still do not open. The buttons that open a link call the same code on Android as everywhere else and answer with a toast, "Could not open the browser" and the system's reason: the clan page's Discord link, the links in a news post and the Discord card of the Thulium page. A link inside a wiki article does nothing at all on Android and on iOS (a log line only; read from the code, not tried). The update notice's Download button would answer with the toast too, but the updater is off on phones, so that notice is never drawn there. The Android build has no clipboard: no Copy button and no pasting into a text field. None of this was tried on a phone, and the real fix (an Android intent) is not in this release.
- Open points of 0.5.9 that stand: the Nightmare's real boss has not been played at its real size, the web version on phones and tablets was not tried on a real device, the builds are unsigned, the phone apps are works in progress, and the limits of 0.5.9 and 0.5.8 stand unless this note replaces them below.
Replaces earlier notes
These lines of the shipped notes are no longer true in 0.5.10; this note replaces them, and the shipped files are not edited.
- 0.5.9, Davidski's Nightmare: "Evil Davidski has 550,000 hull and 660,000 shield" is 5,500,000 and 6,600,000. "While any of them lives, a fifth of the damage you deal gets through to him" and "a blow that would kill Evil Davidski in one 50 millisecond tick while a golden ship lives is no longer final" are replaced by: he takes no damage at all while any golden ship lives. "The plan is 45 to 60 minutes" and "clears the gate in 50.4 minutes (the model says 52.3)" are about 84 minutes in the model (83.6) now. Every damage number of the gate is three times the 0.5.9 one. The boss's two rocket barrages fire Dormant Lances, not Rivets.
- 0.5.9, clan dungeons: "0.2 % of the boss's hull and shield" is 0.1 %. Phantom's Lance "two illusions" is three.
- 0.5.7, Clan Wardens: "a Warden fights at the percent of its strength that the crew present makes" (hull, shield, damage, mending and reinforcements) is true of the damage, the mending and the reinforcements only; the hull and the shield are whole.
- 0.5.9, ships and aliens: "an alien made by a map's own spawner is given a random id from 100,000 up to 900,000 with no check that it is free" is no longer true: it is drawn free of every pilot's number and a clash is repaired within a second.
- 0.5.8, sanction lines: the chat line that says who was kicked, muted or banned is a Global line now.
- 0.5.9, Premium: "Premium currently gives no gameplay advantage and no extra features: it shows a Premium badge on your pilot" is replaced by the Help card's list of what Premium gives (see Changed): emoji and colours in chat, no daily limit on emotes, a larger translation allowance when a server translates, and 5 Chroma Archives with every month. "The update moves no Credits, Thulium or items" stays true of Credits and Thulium; 0.5.10 gives a few items and containers (see "If you already play").
- Containers (0.4.26 and later): "Containers are random rewards earned in the game. They are never sold" and "Premium changes nothing" are now: none is sold on its own, the Chroma Archive also comes with every month of Premium, and Premium gives no extra openings and no better chances.
- Loot of a group's kill (earlier notes): the loot of an alien or a swarm boss that two or more pilots of a group damaged is cut into one personal crate for each of them by the damage they dealt (30 seconds, then free for everybody); the Clan Warden's and the Tesseract's boxes are rolled once a kill.
- Skylab, kills: the kills of a Skylab are twice 0.5.9's at the same hull wear an hour; the Defense magazines and the Trophies Bay are twice as big and a magazine of a fixed size lasts half as long.
- 0.5.9, the phone release step: "the iOS step goes to TestFlight's internal testers only" is no longer true. The export is not internal-only, and the job can add the build to an external TestFlight group and send it to Beta App Review. It still never submits the app to the App Store and never uses Google Play's production track.
- 0.5.9, About on the phones: "About, Links has no Website entry on Android and iOS" stays true, and the phones now have no Release Notes entry either (both phone builds had one). About, More on both phones has the Privacy Policy, the Terms of Use and Discord; on Android the three are written addresses, not links.
- Steam documents before 0.5.10: "the only address of the game's site in the Steam program is the privacy policy's" is now the privacy policy's and the Terms of Use's, both on the site's new host; the Steam upload's executable check allows exactly those two pages.
- Invite Friends wiki article: "outside Steam, where to get the game" is "outside Steam and iOS" (13 languages): the iOS app's invite message leaves the download address out.
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 |
640faf9b6c10419683ffc149aa37e4449f9a8d39de7f24ea42abefc435373244 |
SpaceCorps2027-windows-x86_64.zip |
beb7b3983ffed9ea4286463bc8576529c25eb285f0cd54bacecd3cfd55832b21 |
SpaceCorps2027-linux-x86_64.AppImage |
c3efee4534c04d93375856dec1207e0814319c48f5b6f0a28a01221290f6b8a0 |
SpaceCorps2027-linux-x86_64.tar.gz |
96760633e5e1e4ff2827927ecd59df1651c1c94a5e117aefed158de9411d2d20 |
SpaceCorps2027-windows-aarch64.zip |
ce3f48840a599eeea61fb7fd5efcc4f92a0a4c60d39bad7c4a16e4064d36eb6d |
SpaceCorps2027-linux-aarch64.AppImage |
88aff11f42445c798b1039e0ae716511db64902e6e56b3352a8c3814c412c9e4 |
SpaceCorps2027-linux-aarch64.tar.gz |
c84773c7ba9c5721a281da83bc83fa5af0828d305ab6fe7e47cea2c037fe2acb |