Repository navigation
Releases: KSAModding/Borea
Release list
v0.4.0
Borea v0.4.0
Borea is the community content manager for Kitten Space Agency: find mods, install them with their dependencies into separate instances of the game, and launch through StarMap.
Website | Discord | Content index | Source and issues
Coming from v0.3.x
Click "Update now" on the Home banner, or run borea update-self.
Your instances, mods and settings stay as they are.
Pins and mods detached from a modpack are new in the record of an instance. An older Borea still reads such an instance, but it drops the pins and the detached mods when it saves that instance. So once you pin or detach a mod, do not go back to v0.3.x with that instance.
Highlights
- Descriptions and release notes show all of their formatting: links open in the browser, and tables, lists, code and dividers look as the author wrote them.
- Select and copy text across a whole description, through paragraphs, headings, lists, tables and code.
- Pin a mod at its version, and Borea tells you when a pin holds back the update of another mod.
- Detach a mod from its modpack to choose its version yourself, and attach it again later.
- Mods that you installed by hand now show on the Content tab of the instance, below the mods that Borea manages.
- Filter Discover by more than one license.
- Mod authors see a preview of their description in the listing editor while they type.
For players
Descriptions and release notes
- Links in descriptions and release notes open in the browser and show their address when you point at them. A bare address such as
https://example.comis a link too. - Tables, dividers, nested lists, escaped characters, line breaks and
<br>show as the author wrote them, with no Markdown characters left over. - Inline code and code blocks take the colors of the theme instead of a black bar.
- A drag selects text across paragraphs, headings, list items, table cells and code blocks. Ctrl+C, or Copy in the right-click menu, copies the whole selection with a blank line between the blocks, and Ctrl+A selects the whole description. A press after the end of a line starts the selection there.
- Headings can be selected too.
- A link on the second or a later line of a long paragraph now opens on a click.
Instances
- The Content tab now also lists the mod folders that Borea did not install, in a table "Not managed by Borea" below the mods that Borea manages. The "Manual installs" tab is gone.
- Each of these rows says that Borea cannot update the mod. "Manage with Borea" is a button on the row, and "Replace with the latest release" is in its "..." menu.
- That table always has "Open folder" in its header, also when it is empty, so you can still add a mod by hand. Thanks to @LaurensDeV for the report.
- "Pin version" in the "..." menu of a mod keeps it at its installed version, and the row shows a pin mark. "Update all", the update of the mod itself and a pack update leave a pinned mod alone, and the other mods still move. "Unpin" takes the pin away.
- A plan that needs another version of a pinned mod stops and names the pin.
- When a pin keeps another mod from its newest release, the row of that mod says so, for example "2.0.0 needs Aircraft HUD >= 1.1.0, which is pinned at 1.0.0", instead of an update button. Home does not count it as an update.
Mod packs
- "Detach from modpack" in the "..." menu of a pack mod makes it a mod you chose, and it moves to the Mods group. A pack update leaves it at its version, and a detached mod that you remove does not come back with a later pack update.
- The instance header says how many mods differ from the pack, for example "2 mods differ from Tools Pack 1.0.0", and the pack update confirmation names each detached mod that it leaves alone.
- "Attach to modpack again" undoes it. When the mod is at another version than the pack pins, Borea asks before it changes to the pack's version.
Discover and mod pages
- The License filter shows each license once, such as MIT or CC-BY-SA-4.0, the most used first. You can select more than one, each selected license shows as a chip that removes it, and a mod or pack shows when its license names one of them. The Modpacks tab works the same way.
- The "..." menu of a mod or pack page has "Copy share link" and "Report". Report opens the takedown form or the id dispute form of the content index on GitHub, with the listing filled in, and says in one line what each form is for.
For mod authors
- The listing editor has a Preview switch next to the Description heading. The preview stands next to the description field, shows the description as the mod page shows it, with your images, and follows the text while you type.
- Borea now shows links, tables, dividers, nested lists, escapes, entities and hard line breaks in a description. Raw HTML shows only as its text. What the preview shows is what players see.
Command line
borea pinandborea unpinpin a mod at its version and take the pin away.borea pack detachandborea pack attachdetach a mod from the pack of its instance and attach it again.
Good to know
- This version is tested with KSA 2026.10.7.5541.
- Borea is a community project by the KSA Modding team. It is not made by RocketWerkz.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.4.0-linux-x64.tar.gz | 03e8c033bb1b5f3190d8f851d857c4227641764a7dacf067158467c6836a383e |
| Borea-0.4.0-macos-arm64.tar.gz | b0fdcc4ed94e2214fadc6e6607e41d70d154279b3a182491e2035b674a5aead4 |
| Borea-0.4.0-win-x64.zip | 92d0dd14746bed4fe6b01f74d15091368deff63686b28db3f83240bff358b8af |
| Borea-0.4.0.cdx.json | a0bcbf786e40493db9a6c6af85aba6610271b3cb2cde9197e5a92514b3cfb5cc |
| Borea-Cli-0.4.0-linux-x64.tar.gz | 2c4134f072e6a4c083c9d1c8bf66dace9ce7051f7d546e4e338f7c0bfe4d6ba4 |
| Borea-Cli-0.4.0-macos-arm64.tar.gz | 7e26cc279187b49f1b248e3b8f77e3cea32e42c4347d1d283c0d73ab10ab600d |
| Borea-Cli-0.4.0-win-x64.zip | 572a54f3ba1ec0cfc0d55881a819f8b5bb16e17e7167ed81820e4171ecf1d284 |
| Borea-Cli-0.4.0.cdx.json | 5e6da54d73a4e8f13e48989364b62add8d19bc95825ef4c8f7d43d5c0d2479e0 |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
The App archive also contains BRANDING.md, because the Borea logo in the App is not covered by the MIT License.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
After the App has started once, Borea is in the application menu and starts from there without a terminal.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.4.0.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.4.0.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Rate a pack by the bounds of its pinned releases by @Maximilian-Nesslauer in #693
- Quote the button names in the hint under the share page buttons by @Maximilian-Nesslauer in #694
- Draw bold and italic text from real IBM Plex Sans faces by @Maximilian-Nesslauer in #695
- Merge release/v0.3 into main after v0.3.2 by @Maximilian-Nesslauer in https://github.com/KSAM...
v0.4.0-dev.1
Borea v0.4.0-dev.1: test build for developers
This pre-release is for the Borea team and developers who want to test v0.4.0 before it is released.
It is not for users. For normal use, stay on v0.3.2.
Tell us what did not work: Discord | GitHub issues
Please test these first
- Pins: pin a mod from its "..." menu, then run "Update all". The pinned mod should stay, and the other mods should update. When a pin keeps another mod from its newest release, that row should say which pin holds it back.
- Modpacks: detach a mod of a pack from its "..." menu, update the pack, and attach the mod again. The pack update should leave the detached mod alone and name it.
- Descriptions: open mod pages with long descriptions and release notes. Links, tables, lists and code should look as the author wrote them, and a drag should select across all of it.
- The Content tab: mods you installed by hand should show in "Not managed by Borea", and "Manage with Borea" should take one over.
- Pins and detached mods are new in the record of an instance. An older Borea drops them when it saves such an instance, so test them in an instance you do not open with v0.3.x again.
New since v0.3.2
- Descriptions and release notes show links, tables, dividers, nested lists and code as the author wrote them, and a drag selects text across all of it.
- Pin a mod at its version, and see which pin holds back the update of another mod.
- Detach a mod from its modpack and attach it again.
- The "Manual installs" tab is gone; mods that Borea did not install show on the Content tab.
- The "..." menu of a mod or pack page has "Copy share link" and "Report".
- The License filter of Discover takes more than one license.
- Mod authors: the listing editor previews the description while you type.
- The command line has
borea pin,borea unpin,borea pack detachandborea pack attach.
How to get the next test builds
With the default update channel, "Stable releases", Borea does not tell you about pre-releases like this one.
To see them, open Settings, General, and set "Update channel for Borea" to "All releases, dev builds included".
"Check for updates at start" must be on.
When v0.4.0 is released, every channel tells you about it.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.4.0-dev.1-linux-x64.tar.gz | 914cc5acdd2751a73f22908ea2e94d2d1535dc2148d66a9184e8ddcff55c5356 |
| Borea-0.4.0-dev.1-macos-arm64.tar.gz | 3d390c6c775bd7ccca68e66c7c3efb63fa9913a24bd5ac0dd7076c1c142c3386 |
| Borea-0.4.0-dev.1-win-x64.zip | e641cbf16edd7ce26ae0617645b84c0094a85894506227377e4c12f2e39068ab |
| Borea-0.4.0-dev.1.cdx.json | f74c609afbf7ba5ec0b23f3abc09efde55885add8684dc04e300d10a71711968 |
| Borea-Cli-0.4.0-dev.1-linux-x64.tar.gz | 981c4d643eca23c5639c69dc37602fdf1bd5822d8f09e6f400e9df3452dcbd70 |
| Borea-Cli-0.4.0-dev.1-macos-arm64.tar.gz | b7f3f7fc5efbd82badce9deb3e99580fc60f885c416f7701459790164c9b1942 |
| Borea-Cli-0.4.0-dev.1-win-x64.zip | e5cfe51502f1e32a471de8c91f67acd1c788cca0a83c476c5421d5b038eb0ac5 |
| Borea-Cli-0.4.0-dev.1.cdx.json | 3092921edfe6c88494238a13d02ab2ef0007a1e629311da335183903eaf8d113 |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
The App archive also contains BRANDING.md, because the Borea logo in the App is not covered by the MIT License.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
After the App has started once, Borea is in the application menu and starts from there without a terminal.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.4.0-dev.1.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.4.0-dev.1.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Rate a pack by the bounds of its pinned releases by @Maximilian-Nesslauer in #693
- Quote the button names in the hint under the share page buttons by @Maximilian-Nesslauer in #694
- Draw bold and italic text from real IBM Plex Sans faces by @Maximilian-Nesslauer in #695
- Merge release/v0.3 into main after v0.3.2 by @Maximilian-Nesslauer in #698
- Render the Markdown that listings and release notes use by @Maximilian-Nesslauer in #699
- Preview the description in the listing editor by @Maximilian-Nesslauer in #701
- Show mods that Borea did not install in the Content tab by @Maximilian-Nesslauer in #703
- Pin a mod to its version in an instance by @Maximilian-Nesslauer in #705
- Detach a mod from the modpack of its instance by @Maximilian-Nesslauer in #706
- Put Copy share link and Report in the menu of the mod and pack page by @Maximilian-Nesslauer in #707
- Filter Discover by license ids, with more than one selected by @Maximilian-Nesslauer in #708
- Add KSA 2026.10.7.5541 to the verified builds by @Maximilian-Nesslauer in #710
- Select text across the blocks of a description by @Maximilian-Nesslauer in #711
- Say which pin holds an update back by @Maximilian-Nesslauer in #712
- Add the release notes of v0.4.0 and v0.4.0-dev.1 by @Maximilian-Nesslauer in #713
Full Changelog: v0.3.2...v0.4.0-dev.1
v0.3.2
Borea v0.3.2
A fix release for v0.3.1. Update with "Update now" on the Home banner, or with borea update-self.
Website | Discord | Content index | Source and issues
Fixes
- A mod pack is now called Compatible only when every mod it pins fits your game too. When a pinned mod needs a newer game, Borea does not install the pack and names that mod. When your game is newer than a pinned mod supports, the pack shows Untested, the pack page names the mod and the last game version it supports, and Borea asks before it installs. Before, a pack could show Compatible and then crash the game. Thanks to @renancamm for the report.
- Bold and italic text in descriptions and release notes is sharp now. Borea ships the real IBM Plex Sans Bold and Italic letters instead of a thickened or slanted copy of the regular ones. Thanks to @LaurensDeV for the report.
- The line under the buttons of a share page now reads: "Open in Borea" and "Install with Borea" work only when Borea is installed on this computer. Thanks to @LaurensDeV.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.3.2-linux-x64.tar.gz | d1967be19d41d8aec8248565b36e9c3f864ea5df6978c3562348f3b307f47ff4 |
| Borea-0.3.2-macos-arm64.tar.gz | 46a92ecd6ebed966aba086e71ce21f676a12b71c790b124df4c56374b4c4b996 |
| Borea-0.3.2-win-x64.zip | ee30f7d72255d030728eacae39732a506b3bc939eb2a1e7fc4202b6e5027ddd4 |
| Borea-0.3.2.cdx.json | c70ef5b565aafcd3314a0148034a2f6acc6609ca89d6f28c42d564ef006856be |
| Borea-Cli-0.3.2-linux-x64.tar.gz | c00ab7ef2a2f21a658e03df3907c8398c93f47657bbd7b95eafdbb9a72407fd1 |
| Borea-Cli-0.3.2-macos-arm64.tar.gz | d5c77cc72f9ae67e063c25c067a2298169ae1409c9e409138ebe6a2af4acceba |
| Borea-Cli-0.3.2-win-x64.zip | 1bed9d454688bbd46fd1a5e25e0d271af7d3b626e8e233f4ed89ccd0e0cc353b |
| Borea-Cli-0.3.2.cdx.json | 60045e6de5785d8ffacdb681138daf36523150ffe4ac23a692c1cf919aa3b626 |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
The App archive also contains BRANDING.md, because the Borea logo in the App is not covered by the MIT License.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
After the App has started once, Borea is in the application menu and starts from there without a terminal.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.3.2.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.3.2.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Release v0.3.2 by @Maximilian-Nesslauer in #697
Full Changelog: v0.3.1...v0.3.2
v0.3.1
Borea v0.3.1
A fix release for v0.3.0. Update with "Update now" on the Home banner, or with borea update-self.
Website | Discord | Content index | Source and issues
Fixes
- Play no longer needs the internet when the mod loader is installed. Borea chooses the loader from the content index it already has, so the game starts at once. Before, Play asked SpaceDock first, and when SpaceDock or your connection did not answer, it waited for 100 seconds and then showed an unexpected error. If Borea has no content index yet and cannot load one, Play now tells you why. The same applies to
borea launch. Thanks to @Kiwi-Shark for the report. - A click beside a text field, for example on the empty page next to the Discover search, now takes the focus from the field, so its cursor and its highlight go away and your keys no longer go into it. In a modal, Tab stays in the modal and Escape still closes it. Thanks to @LaurensDeV for the report.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.3.1-linux-x64.tar.gz | 31cc6840611b56b8e5e44dc3fd31a60860031cedc15b7ce43a4c8b927fd14f9f |
| Borea-0.3.1-macos-arm64.tar.gz | 4a4f8be7117b4ec5358773bdd4e5fa67d4427f36bbf0dd44149781d794c3df0d |
| Borea-0.3.1-win-x64.zip | 96dc92e1300b5882aac8af072007c39178e5d833210ec67d9cef460434ac151c |
| Borea-0.3.1.cdx.json | 4a55245984152814f10e05f8707d881c06361209867fd2a16ff149f210533cea |
| Borea-Cli-0.3.1-linux-x64.tar.gz | 432ebe5ef957e474233fa7475fdef67a2e146948c6834ad0ced3977126b6817e |
| Borea-Cli-0.3.1-macos-arm64.tar.gz | e9fe33c2dc8e3cab545758927bc16a102714ec725a0b5539aa82e3c170046c49 |
| Borea-Cli-0.3.1-win-x64.zip | 73732abdc53414b0f82ffb7a5f26fc1e106dbdb11a632c50c7f7ed9b415e81ab |
| Borea-Cli-0.3.1.cdx.json | 0d4089bd053457b39d5370d75cee1e63d0be4b3a984ec110c72fe513267f240a |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
The App archive also contains BRANDING.md, because the Borea logo in the App is not covered by the MIT License.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
After the App has started once, Borea is in the application menu and starts from there without a terminal.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.3.1.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.3.1.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Start a launch from the held content index by @Maximilian-Nesslauer in #681
- Take the focus from a text field on a click beside it by @Maximilian-Nesslauer in #680
- Add the release notes of v0.3.1 by @Maximilian-Nesslauer in #682
Full Changelog: v0.3.0...v0.3.1
v0.3.0
Borea v0.3.0
Borea is the community content manager for Kitten Space Agency: find mods, install them with their dependencies into separate instances of the game, and launch through StarMap.
Website | Discord | Content index | Source and issues
Coming from v0.2.x
Click "Update now" on the Home banner, or run borea update-self.
Your instances, mods and settings stay as they are.
Highlights
- Borea keeps one copy of each mod release and links it into every instance that uses it, so a mod you already have does not need to be downloaded twice.
- When the game crashes after it started, Borea tells you, names the mod if one caused it, and opens the crash log for you.
- Discover scrolls smoothly now, even when you scroll fast through a long list.
- Mark your favorite mods and packs, and find the mods you already use in your other instances.
- Save the game settings of an instance as a preset and start new instances from it.
- Borea remembers your GitHub sign-in, so you stay signed in after a restart.
- Mod authors can now write and publish mod packs right from the App.
- Stewards of the content index can review, merge and moderate the index without leaving Borea.
- Experimental: on a Mac, Borea can play the Windows build of KSA through a Wine wrapper such as Sikarugir.
For players
Shared mod files
- Borea now unpacks each mod release only once, into
Static Mod Filesin your library folder, and links every instance to that copy. A second install of the same release does not need to download or unpack anything again. - When you remove a mod from one instance, only its link goes away. Borea deletes the stored copy once no instance uses it anymore.
- Some mods write into their own folder. When Borea notices that, it gives every instance its own copy of that mod and tells you which mod it was, so one instance cannot change the files of another.
- If you prefer a separate copy of every mod in every instance, turn off "Share mod files between instances" in Settings, General.
- The instance page counts linked mods in its size, so the total still tells you how much room the instance takes.
- Moving your library folder moves
Static Mod Filesalong with it. On Windows, moving the library to another disk now also works when an instance holds a linked mod.
Discover and mod pages
- Mark mods and packs as favorites from their "..." menu. Favorites get a small star, and "Only favorites" in the Show filters lists just them.
- "Installed in other instances" in the Show filters shows the mods you already use elsewhere. Combine it with "Hide already installed" to see what you have in another instance but not in this one yet.
- The search field says what it searches, such as "Search 20 mods".
- In a long list, "Back to top" at the bottom takes you straight back to the search and the filters.
- Hold the middle mouse button in any list or page and move the mouse to scroll, as in a web browser. The back and forward buttons of your mouse move between pages.
- Free-form tags now read like the curated ones, for example "Space Station". When a row has more tags than fit, a chip such as "+2" names the rest.
- Some mods need a step from you, before you play or when you remove them. Their mod page now shows those steps, and the install asks you to confirm them.
- When a release can no longer be downloaded from its host, Borea stops offering it for new installs and updates. The Versions tab still lists it, with the date it went away.
- Clicking "+" or Install without an active instance now tells you what to do, with a button that opens the Library.
- Fast scrolling no longer stutters. Borea reuses the rows that scroll out of view instead of building them again, so a list stays smooth also when you scroll quickly from the end back to the top.
- A scrollbar grows as soon as your pointer is over it, and shrinks again as soon as the pointer leaves.
- Long lists use less memory, and a list keeps its scroll position when you come back from a mod page.
- Buttons and links behave the same everywhere: the hand cursor on everything you can click, links that turn purple under the pointer, text in the center of the purple buttons and of the search fields, and tooltips that explain a number or a date that stands on its own.
Instances
- The Mods, Manual installs, Log and Game data tabs are now tables. The less common actions of a mod moved into its "..." menu, and the menu explains when an action is not available.
- Every instance has the same "..." menu, on the Library, on its Home card and on its own page, including "Back up all saves". Deleting an instance now asks first.
- "Save settings as preset" in the instance menu keeps the game settings of that instance. When you create a new instance, you can start it from a preset, and Settings, Game lists your presets so you can delete old ones.
- "Let Borea manage" now checks what the mod needs before it takes it over, and can install a missing required dependency in the same step.
- The Manual installs tab explains which mods the game loads and why Borea leaves them alone.
- Home shows two full rows of recently updated mods.
Saves and vehicles
- Rename a save or a vehicle from its row menu. Borea changes both the name the game shows and the folder on disk.
Mod packs
- A pack pins exact versions on purpose. Borea now tells you when its mods have newer releases, such as "1 of 3 mods has a newer release", but it never changes what the pack installs.
- "Copy forum list" on the pack page copies one line per mod, in the format the forum rules ask a pack thread to use.
- When a pack install stops, Borea tells you which mod stopped it and why.
- When a pack pins a release that can no longer be downloaded, Borea warns you before the install.
Launching and when something goes wrong
- When the game closes unexpectedly after it started, Borea tells you, names the mod if one caused it, and "Open log" takes you to the crash log. If the game crashed while Borea was closed, you see the message once at the next start.
- When StarMap restarts itself to load new mods, Borea now follows the restarted game. Play and a backup restore of that instance wait until you close it.
- When StarMap stops right after the start and names a mod file by its path, Borea now tells you why instead of showing "Something went wrong".
- The error bar at the bottom of the window has a solid background now, so its text stays readable.
- On Linux, Borea adds itself to your application menu at the first start, and from then on starts from there without a terminal. On Windows, Borea no longer opens a console window when it restarts after an update.
KSA on a Mac in a Wine wrapper (experimental)
KSA has no macOS build, so some players run the Windows build on their Mac inside a Wine wrapper app such as Sikarugir. Borea now supports this, but it is new and has only been tested by a few people, so please tell us how it works for you.
- Game detection finds the game and StarMap inside wrapper apps in
/Applicationsand~/Applications, and one folder below them, such as~/Applications/Sikarugir, where Sikarugir saves its wrappers. - Play starts StarMap through the wrapper, with the instance you chose, and "Play without mod loader" starts KSA through it too.
- Borea tells StarMap where the game is in the form that Windows programs inside the wrapper understand, such as
C:\Program Files\Kitten Space Agency, also when an older Borea had written a macOS path. - StarMap needs the .NET runtime for Windows inside the wrapper. When it is missing, Borea tells you which version you need and how to install it in three steps: download Microsoft's installer, install it through "Install Software" in the Configure window of the wrapper, and click "Check again". Borea never downloads or installs anything into the wrapper itself.
- Launch arguments cannot be passed through a wrapper, so an instance with launch arguments is refused with a message, and only one game at a time can run through the same wrapper.
- When the game crashes inside a wrapper, Borea does not show the crash message yet.
- On Linux, Borea does not try to start a Windows build of KSA and tells you why.
Updating Borea
- "Update now" runs as a task in the Tasks drawer, where you can follow the download. If an update fails, the task says why, and the build you have keeps working.
- When you change the update channel in Settings, or turn "Check for updates at start" on, Borea checks for a new release at once, without a restart.
GitHub sign-in
- When you sign in to GitHub in Settings, Borea keeps the sign-in in the secure credential store of your system and signs you in again at the next start. Turn off "Stay signed in on this computer" if you do not want that, and signing out always deletes it.
For mod authors
- Mod packs in the listing editor: start a new pack, pick its mods from the index, make the next version of a pack you already listed, or turn one of your instances into a pack. Borea opens the pull request for you, and the first version of a new pack also records you as its owner.
- Version bounds with one or two numbers, such as
min = "0.5", now work in a listing (RFC 0072), and the editor finds releases tagged0.5orv1. - "Stamp older releases from version" in the listing editor sets
sinceunder[releases](RFC 0079), so the index also stamps releases older than the newest one. - The free tag field accepts capitals and spaces, and stores the tag in lowercase with
-between the words. - The listing editor reads the prefix of your forum thread by its id, so it still picks the right tag when the forum renames a prefix.
- The steps your listing asks for, before play and when the mod is removed, are now shown to players on th...
v0.3.0-dev.2
Borea v0.3.0-dev.2: test build for developers
This pre-release is for the Borea team and developers who want to test v0.3.0 before it is released.
It is not for users. For normal use, stay on v0.2.1.
Tell us what did not work: Discord | GitHub issues
Please test these first
- The update channel: in Settings, General, switch "Update channel for Borea" between "Stable releases" and "All releases, dev builds included". The Home banner should follow the channel within a few seconds, without a restart.
- On a Mac with a Sikarugir wrapper in
~/Applications/Sikarugir: the game detection should find KSA there. - On a Mac whose wrapper has no .NET runtime: the message should say in three steps how to install it, and "Check again" should start the game once it is there.
New since v0.3.0-dev.1
- A change of the update channel, or turning "Check for updates at start" on, checks for a new Borea release at once. The Home banner and the release notes follow the new channel without a restart.
- On a Mac, the game detection also finds Wine wrapper apps one folder below
/Applicationsand~/Applications, such as~/Applications/Sikarugir/KSA.app, where Sikarugir saves its wrappers. - The message about a missing .NET runtime in a Mac wrapper names the version in its title and gives three numbered steps: download the installer, install it through "Install Software" in the Configure window of the wrapper, and click "Check again".
- The listing editor reads the prefix of a forum thread by its id, so a prefix that the forum renames still gives the right tag.
- The text of a purple button that holds only text sits in its center.
- The Discover search field says what it searches, such as "Search 20 mods", and its text sits in the middle of the field, level with the search icon.
Also in v0.3.0-dev.1, but not named in its notes
- Experimental: on a Mac, Borea can play the Windows build of KSA through a Wine wrapper such as Sikarugir.
- Long lists scroll smoothly, also when you scroll fast from the end back to the top.
How to get the next test builds
With the default update channel, "Stable releases", Borea does not tell you about pre-releases like this one.
To see them, open Settings, General, and set "Update channel for Borea" to "All releases, dev builds included".
"Check for updates at start" must be on. In v0.2.1 and v0.3.0-dev.1 the change takes effect at the next start, and from this build on it applies at once.
When v0.3.0 is released, every channel tells you about it.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.3.0-dev.2-linux-x64.tar.gz | 16836cce6971e969c307b18f3aab7e2eca9f92bd55e0d68e03bc7707e4c7e101 |
| Borea-0.3.0-dev.2-macos-arm64.tar.gz | 93ffac4f356bce13c23f99b7d73ae422e5c0227875da1a792b3330538330c466 |
| Borea-0.3.0-dev.2-win-x64.zip | 98c639e87bd50c8ba087758ff91bc9d3db3842df50e8206b1574e458d2562eb5 |
| Borea-0.3.0-dev.2.cdx.json | 32cc6bb65399845c249a604823aeadd00d4d694949c59a70c74f6cf1d2f2bce8 |
| Borea-Cli-0.3.0-dev.2-linux-x64.tar.gz | 8de29a1111aba7770e99ffbafa7504e002a066db68b7862edd9e8b933842cbe1 |
| Borea-Cli-0.3.0-dev.2-macos-arm64.tar.gz | 92d686d9bccd6add9ec4c7aae2802ec45cfa07199f91ce905b33188e08055e30 |
| Borea-Cli-0.3.0-dev.2-win-x64.zip | 7bf7f7f6588bffa97ce90e4971234fbe2ec42224ce615d3dae6d4ab417133ddb |
| Borea-Cli-0.3.0-dev.2.cdx.json | 54ea8ec173c4371f37faa14a3b323d652c2e519e0c7e9a1b3d8c18f3f34afe23 |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
The App archive also contains BRANDING.md, because the Borea logo in the App is not covered by the MIT License.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
After the App has started once, Borea is in the application menu and starts from there without a terminal.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.3.0-dev.2.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.3.0-dev.2.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Match forum prefixes by their id by @Maximilian-Nesslauer in #660
- Refresh in order in the steward status sign-out test by @Maximilian-Nesslauer in #663
- Center the text of a purple button that holds only text by @Maximilian-Nesslauer in #665
- Explain the .NET runtime install in three steps by @Maximilian-Nesslauer in #666
- Check for a Borea update when the update channel changes by @Maximilian-Nesslauer in #668
- Center the text of the search fields by @Maximilian-Nesslauer in #672
- Find wrapper apps one folder below the application folders by @Maximilian-Nesslauer in #669
- Name the count of the tab in the Discover search field by @Maximilian-Nesslauer in #674
- Add the release notes of v0.3.0-dev.2 by @Maximilian-Nesslauer in #670
Full Changelog: v0.3.0-dev.1...v0.3.0-dev.2
v0.3.0-dev.1
Borea v0.3.0-dev.1: test build for developers
This pre-release is for the Borea team and developers who want to test v0.3.0 before it is released.
It is not for users. For normal use, stay on v0.2.1.
v0.3.0 follows in a day or two.
Tell us what did not work: Discord | GitHub issues
Please test these first
- The update from v0.2.1: set the update channel as described below, then click "Update now" on the Home banner, or run
borea update-self. - Shared mod files: install the same mod in two instances. The second install should download nothing, and the game should start with the mod in both instances.
- Staying signed in: sign in to GitHub in Settings, close Borea and start it again. You should still be signed in. This matters most on macOS and Linux, where Borea uses the Keychain and the Secret Service.
- A crash after the start: when the game closes unexpectedly, Borea should tell you and open the crash log.
New since v0.2.1
- Borea keeps one copy of each mod release and links it into every instance that uses it, so a second instance with the same mod downloads and unpacks nothing. You can turn this off with "Share mod files between instances" in Settings.
- When the game crashes after it started, Borea tells you, names the mod if one caused it, and opens the crash log.
- When StarMap restarts itself to load new mods, Borea follows the restarted game, so the launch keeps running until you close it.
- Borea remembers your GitHub sign-in in the secure credential store of your system, so you stay signed in after a restart.
- Discover: favorites, a filter for the mods you already use in other instances, a "Back to top" button, and free-form tags that read like the curated ones.
- Scroll any list by holding the middle mouse button, and move between pages with the back and forward buttons of your mouse.
- Instances: the tabs are tables with a "..." menu for each row, new instances can start from game settings presets, and saves and vehicles can be renamed.
- When a mod needs a step from you, before you play or when you remove it, its mod page and its install show that step.
- Borea no longer offers a release that can no longer be downloaded from its host.
- Mod packs: Borea tells you when the mods of a pack have newer releases, and when a pack install stops, it names the mod that stopped it.
- Mod authors: write a mod pack in the listing editor, make its next version, or turn an instance into a pack, and open its pull request from the App.
- Stewards of the content index: a new Steward page for the review queue, reviews, merges, reports, status changes and release amendments.
- Translators: preview a translation in Borea without a build.
- Linux: Borea adds itself to your application menu at the first start and starts from there without a terminal.
How to get the next test builds
With the default update channel, "Stable releases", Borea does not tell you about pre-releases like this one.
To see them, open Settings, General, and set "Update channel for Borea" to "All releases, dev builds included".
"Check for updates at start" must be on, and the change takes effect at the next start.
When v0.3.0 is released, every channel tells you about it.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.3.0-dev.1-linux-x64.tar.gz | f684c70e8991d1cbff10ab1cc848752fdd636491f6f32232ccc69c8e86e7932f |
| Borea-0.3.0-dev.1-macos-arm64.tar.gz | d93a085d063f9c4944c459fa568afeb43486853b037f396161aa7c7480a2facd |
| Borea-0.3.0-dev.1-win-x64.zip | 1ee98a2d1ebad59f61c344ed6991928d49ee9cd28725e4f840131a6eb4fe98bd |
| Borea-0.3.0-dev.1.cdx.json | 2e52e938ea2dbd0789a5eee29b4d41d369087d23a07b7c9560193389a684f884 |
| Borea-Cli-0.3.0-dev.1-linux-x64.tar.gz | b7bb98e52b653c5574c9f19118d51227cfa4b8c112cf72cc16411cf1d1eb4df7 |
| Borea-Cli-0.3.0-dev.1-macos-arm64.tar.gz | 0b86ecb4ea95a244e9f62f8fd4c4a1f7d88a343b6e3e1e90d6db0bd098cebd98 |
| Borea-Cli-0.3.0-dev.1-win-x64.zip | a03a7f91c75d43a937f258fc082ea18b9e79dd179a63dd3d140e776f98172e69 |
| Borea-Cli-0.3.0-dev.1.cdx.json | f585f779a52e6b4e23412855839151be766593a5b1a54bcf6c55aca4915a0cf5 |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
The App archive also contains BRANDING.md, because the Borea logo in the App is not covered by the MIT License.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
After the App has started once, Borea is in the application menu and starts from there without a terminal.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.3.0-dev.1.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.3.0-dev.1.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Change saves and vehicles without asking whether a file is open by @Maximilian-Nesslauer in #515
- Show backup sizes and refuse a restore while the game runs in the CLI by @Maximilian-Nesslauer in #514
- Check the dependencies before Borea takes over a mod by @Maximilian-Nesslauer in #516
- Tell mod authors that an instance moves the game profile by @Maximilian-Nesslauer in #513
- Make the App react the same way wherever a player clicks by @Maximilian-Nesslauer in #532
- Show the lists of an instance as tables and move row actions into a menu by @Maximilian-Nesslauer in #533
- Show full rows on Home and one instance menu everywhere by @Maximilian-Nesslauer in #534
- Keep the cost of Discover with the window, not the list by @Maximilian-Nesslauer in #537
- Wait for the task history save before the self-update close test by @Maximilian-Nesslauer in #540
- Start the listing branch at a commit the fork already has by @Maximilian-Nesslauer in #538
- Merge the v0.2.1 release branch into main by @Maximilian-Nesslauer in #542
- Say when the mods of a pack have newer releases, and copy its forum list by @Maximilian-Nesslauer in #545
- Show the update of Borea itself as a task in the Tasks drawer by @Maximilian-Nesslauer in #546
- Store each mod release once and link instances to it by @Maximilian-Nesslauer in #548
- Turn the shared mod store on, and give a mod that writes into its folder its own copy by @Maximilian-Nesslauer in #549
- Name the member that stops a pack install by @Maximilian-Nesslauer in #547
- Navigate with the back and forward buttons of a mouse by @Maximilian-Nesslauer in #551
- Mark mods and packs as favorites by @Maximilian-Nesslauer in #552
- Show mods installed in other instances on Discover by @Maximilian-Nesslauer in #553
- Show a phone Copy...
v0.2.1
Borea v0.2.1
A fix release for v0.2.0. Update with "Update now" on the Home banner, or with borea update-self.
Website | Discord | Content index | Source and issues
Fixes
- Mod authors: opening the listing pull request from the App now works when your copy of content-index is older than a change to the index's own workflows. Before, it stopped with "GitHub refused access to the branch." Borea now starts the branch at a commit your copy already has, so the pull request shows only your listing file. When your listing changed in the index after you made your copy, Borea asks you to press "Sync fork" on GitHub, with a button that opens your copy. Thanks to @elevatorctln for the report.
- Saves and vehicles: Borea no longer claims that a file is open when it cannot know that. A copy, backup, restore or delete now reports the real error if one happens.
For mod authors
- Make your mod work in a Borea instance: a mod that reads
Documents/My Games/Kitten Space Agencyby a fixed path finds nothing in an instance. The page says what to use instead.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.2.1-linux-x64.tar.gz | c19fa2a9a6adceb75a10c65be81bd0447d53c3aeed6982fc6312334100f991b8 |
| Borea-0.2.1-macos-arm64.tar.gz | 3b865a5552f545086ddc804854fe0a06c1a84695447cf36fda046a7b931a7e9a |
| Borea-0.2.1-win-x64.zip | 4e0a7d0c10bab9d655052e8b66e302f594b570e389f6e558c72d9d7ff36665ef |
| Borea-0.2.1.cdx.json | 3bebfc1e5a8587aa1dbee11b1479ab9603993acb5110fbe984583f318fdc6c66 |
| Borea-Cli-0.2.1-linux-x64.tar.gz | 8ca7c6da7966118982a358fad4fb893fee9a5a4a425effc71e749e5b070bdeec |
| Borea-Cli-0.2.1-macos-arm64.tar.gz | 0f68ba92b7a4ff70cfb77d7b2291184bc4b71e8a19d48a2ad6af414d01e22701 |
| Borea-Cli-0.2.1-win-x64.zip | d8c661f91c181964355319a747caa37b05e77e32c1b570ea87f47dc6f9e75036 |
| Borea-Cli-0.2.1.cdx.json | d6d5c9bd95575ecb61b26dc907c1ea31f6d7504d4dfc15461c493a79aadaffce |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.2.1.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.2.1.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Release v0.2.1 by @Maximilian-Nesslauer in #541
Full Changelog: v0.2.0...v0.2.1
v0.2.0
Borea v0.2.0
Borea is the community content manager for Kitten Space Agency: find mods, install them with their dependencies into separate instances of the game, and launch through StarMap.
Website | Discord | Content index | Source and issues
Coming from v0.1.0
v0.1.0 cannot update itself, so download v0.2.0 from this page once.
The archive now unpacks into a folder named Borea. Put it where it can stay, such as %LocalAppData%\Programs\Borea or ~/.local/share/Borea, because from v0.2.0 on Borea updates itself into that folder: "Update now" on the Home banner, or borea update-self.
Highlights
- Borea updates itself, in the same folder, so shortcuts keep working.
- Mod packs: create an instance from a pack, and move it to a newer or older pack version.
- Mods you installed by hand: Borea takes them over, and it notices a mod whose folder is gone.
- Saves and vehicles: backups you can restore and delete, and old ones are cleaned up.
- Discover refreshes the content index while Borea runs, and shows the dependencies of a mod.
- Share a mod with a link: every listing has a web page with "Open in Borea".
- Mod authors: list and change your mods from the App.
For players
Updating Borea
- "Update now" on the Home banner downloads the build for your system, checks it against the checksums of the release, and puts it in place of the one you run. If something fails, your build stays as it was.
- Borea removes the unpacked files of its earlier builds, which used to stay on the disk.
Discover and mod pages
- A Refresh button next to the heading, and a check in the background when the index is older than ten minutes.
- The foot of the side panel says how many mods the list holds, or how many of them a filter shows.
- Each Game version box clears on its own, a chosen license or system is marked, and many filter chips wrap instead of running off the edge.
- A click anywhere on a row opens its page, and a back arrow leads to where you came from.
- Discover names the instance that "+" adds to.
- The compatibility chip shows only where it differs from the rest of the list.
- A mod page has a Dependencies tab, and "Change version" leads to the versions of an installed mod. The installed version offers no "+", and replacing a version always asks first.
- The download size follows the choices you make, and an install that does not fit on the disk is refused before it starts.
- The content categories are translated.
Instances
- The new instance dialog explains what an instance is, and small "?" buttons explain the game profile and other things in place.
- The whole instance card opens the instance.
- The instance page shows which mod loader the instance needs, and whether the right version is installed.
- A mod whose folder is gone is marked "Not on disk", with "Install again" or "Remove from the list".
- "Let Borea manage" on the row of a mod you installed by hand takes it over, so it updates and removes like any other.
- Core loads before the mods of an instance, so a new instance starts the way the game expects.
- When the game installation does not look the way Borea expects after a KSA update, Home says so and Borea does not change mod files until it is sorted out.
- Deleting an instance also deletes its backups.
- Moving the library folder no longer asks you to close a game that does not run.
Mod packs
- "New instance from this pack" on the page of a pack.
- Move an instance to a newer version of its pack, or install an older one from the Versions tab.
- A pack update that stops or fails keeps the mods you had.
Saves and vehicles
- Backups has a list of every backup with Restore and Delete, and "Delete backups older than" in the settings.
- "Copy from profile" can select or clear every item at once.
Launching and when something goes wrong
- When StarMap crashes while it loads mods, Borea names the mod that was loading.
- The error bar says what you can do, with "Copy details" and "Report this".
- Settings has a Help tab that says where to ask and what to put in a report.
- A second start brings the open Borea window to the front, and
borea://links open pages in Borea on Windows and Linux. - The window closes even when an install does not stop.
For mod authors
- "List or change your mod" on Discover writes the listing of your mod, checks it as you type, and opens the pull request to the content index after you sign in to GitHub. It also loads a listed mod to change it, with a search by name, id or author.
- Every listing has a share page at
https://ksamodding.github.io/Borea/mod/<id>/that you can link from a forum post, a README or social media. - If your mod reads files by a fixed path to
Documents/My Games/Kitten Space Agency, it finds nothing in a Borea instance. Use the folder of your mod, orKSA.Constants.DocumentsFolderPath, instead.
Command line
borea update-selfupdates Borea, and--checkonly says what it would install.borea game checklists what Borea assumes about the game installation, and whether each holds.borea instance shownames the mod loader an instance needs.borea instance backups,restore-backupanddelete-backupwork with the backups of an instance, andborea instance take-ownershiptakes over a mod you installed by hand.borea instance scan --jsonnow prints an object withforeignFoldersandmissingModsinstead of an array, which breaks a script that reads the array.
Good to know
- The builds are not code signed yet, so Windows warns on the first start. "First start" on this page says what to click.
- The macOS build runs on Apple silicon. Start it from Terminal the first time, as "First start" on this page explains.
- A translation no longer has to be complete. A text a translation does not have shows in English.
- Borea is a community project by the KSA Modding team, not made by RocketWerkz.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.2.0-linux-x64.tar.gz | 0b7c0217cfd175481995fc7cefd130136504bb865710ee0e43abd681b2b5a8c2 |
| Borea-0.2.0-macos-arm64.tar.gz | dedb0329ce174bdbc4bd5dfcd48a8ef6d8bd1eef641f96c28be0026c3df61133 |
| Borea-0.2.0-win-x64.zip | 38af431eae516687eb5210cb2b48eba4dc4353f39d086df4ae7fa1f2aec8bf96 |
| Borea-0.2.0.cdx.json | feb6c6715e6e77a30cce001596987e3461dad0ae26d107ea6101c1f3310c624a |
| Borea-Cli-0.2.0-linux-x64.tar.gz | d2b76ad3481897223ca3271a0faa31046462aab172ee61eaa11c43133cdb375f |
| Borea-Cli-0.2.0-macos-arm64.tar.gz | e271bf105b3e87e83e6e45b4747818d011e8326516a944e5dd6725c7e1e40a19 |
| Borea-Cli-0.2.0-win-x64.zip | 4998757bfd73bd73cd2149756ca6f858c09de6f15ec8ad4f708151febf71f642 |
| Borea-Cli-0.2.0.cdx.json | 77f32560e275425e0a5d83600a4e8d6f633520fc3cff819d0c3b923abd6ae53b |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.2.0.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.2.0.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Bring the open...
v0.2.0-dev.5
Borea v0.2.0-dev.5: test build for developers
This pre-release is for the Borea team and developers who want to test v0.2.0 before it is released.
It is not for playing. For normal use, stay on v0.1.0.
v0.2.0 follows right after this build.
Tell us what did not work: Discord | GitHub issues
Please test the update once more
This is the first build whose archive unpacks into a folder named Borea instead of one with the version in its name.
In dev.4, use "Update now" on the Home banner, or borea update-self, and tell us whether Borea restarts as dev.5 in the same folder.
Your folder keeps its name, because Borea updates itself into the folder it runs from.
New since v0.2.0-dev.4
- The App archive unpacks into
Borea, and the CLI archive intoBorea-Cli. Put that folder where it can stay, for example%LocalAppData%\Programs\Boreaon Windows or~/.local/share/Boreaon Linux.
How to get the next test builds
With the default update channel, "Stable releases", Borea does not tell you about pre-releases like this one.
To see them, open Settings, General, and set "Update channel for Borea" to "All releases, dev builds included".
"Check for updates at start" must be on, and the change takes effect at the next start.
When v0.2.0 is released, every channel tells you about it.
Downloads
| File | SHA-256 |
|---|---|
| Borea-0.2.0-dev.5-linux-x64.tar.gz | 2380ec2049e56f0774eb0e05482249e10e616565c5e0ee19d95a2f1ee19965f0 |
| Borea-0.2.0-dev.5-macos-arm64.tar.gz | 9fff0122a3214fdce690cef3465ee31afe607716459c8afa52df3cb7f0d40ff7 |
| Borea-0.2.0-dev.5-win-x64.zip | 3d103d4ca32648a64da4e304bf02204784f44d42b7af99c42cabb72821f3da88 |
| Borea-0.2.0-dev.5.cdx.json | d6936ef6ca845b7149fb3be0faff6424bb4ae77ac68e471260d0219285f2ee6f |
| Borea-Cli-0.2.0-dev.5-linux-x64.tar.gz | 3316a538ffce7f5a455e5d33c0267ac02454fdd4cc1cb109dbf87d7e935e8969 |
| Borea-Cli-0.2.0-dev.5-macos-arm64.tar.gz | 16a7aef2f186f0745c9bfbb261845c2eb363d11a6a36b5e99918ec423b8851f4 |
| Borea-Cli-0.2.0-dev.5-win-x64.zip | c5b71e537b135625962380654e298ccf3c0ebb423e6884b2e8b0b20f7f6aa15d |
| Borea-Cli-0.2.0-dev.5.cdx.json | d1f409a833b605fa4a49b47027503c9b7dd22d192322c5ef16b7b9229782a0b1 |
Each platform has two archives.
The App archive, for example Borea-<version>-win-x64.zip, contains the program borea.
Without arguments, borea opens the desktop App, and with arguments, it runs a command.
Most users want this archive.
Archives whose names start with Borea-Cli- are a smaller download that contains only the command line.
The builds include the .NET runtime and are self-contained, so there is nothing to install first.
Each archive contains borea (borea.exe on Windows), LICENSE and THIRD-PARTY-NOTICES.txt, in a folder named Borea, or Borea-Cli for the CLI archive.
Put that folder where it can stay, for example %LocalAppData%\Programs\Borea on Windows or ~/.local/share/Borea on Linux, because Borea updates itself into the folder it runs from.
First start
These builds are not code signed, so the first start might take an extra step on Windows and macOS. The README has the long explanation.
Windows. Right-click the zip, open Properties and select Unblock.
Then unpack the App archive and start borea.exe, or run .\borea.exe --help in PowerShell in the unpacked folder of either archive.
Without that step, Windows shows "Windows protected your PC". This is because the file might not be downloaded often and is not signed. Select "More info", then "Run anyway".
Linux. Unpack the App archive and run ./borea for the App, or run ./borea --help in the unpacked folder of either archive.
Both need the ICU and OpenSSL libraries of your distribution, and only the App also needs the X11, ICE, SM and fontconfig libraries. Most desktop installs already have them. See Readme.
macOS. Unpack and start Borea from Terminal, not from Finder: tar -xzf <file>, then run ./borea inside the new folder of the App archive for the App, or ./borea --help inside the new folder of either archive.
The macOS builds are for Apple silicon. Intel Macs are not supported.
Provenance
To check that a file came from this workflow:
gh attestation verify <file> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml
Borea-0.2.0-dev.5.cdx.json is the software bill of materials for the App archives, in CycloneDX JSON.
The App contains the command line, so this list includes the NuGet packages of the App and of the CLI.
Borea-Cli-0.2.0-dev.5.cdx.json is the software bill of materials for the CLI archives and includes only the packages of the CLI.
Each list includes the version, license and hash of every package.
Each list is attested only to the archives that it describes, and you can use this command to prove that it belongs to one.
With --format json, the output includes the attested list.
gh attestation verify <archive> --repo KSAModding/Borea \
--signer-workflow KSAModding/Borea/.github/workflows/release.yml \
--predicate-type https://cyclonedx.org/bom
Signing will come in the future and is tracked in #76.
What's Changed
- Record the game data changes instead of reading the rows during the load by @Maximilian-Nesslauer in #524
- Pack the release archives under a folder without the version by @Maximilian-Nesslauer in #526
- Add the introduction for v0.2.0-dev.5 by @Maximilian-Nesslauer in #528
Full Changelog: v0.2.0-dev.4...v0.2.0-dev.5