Do not start KSA while the Ahwoo client updates it

Open
  • Is something wrong?
#771 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Maximilian-Nesslauer is already working on this.

Since Oct 16, 2026.

Assessment

This issue has not been assessed yet.

Description

area:app area:storage
what

The Ahwoo client updates KSA by itself with delta patches.
If Borea starts KSA while the client patches it, the game can start half updated, and a running game can get in the way of the patch.
Ahwoo will look into a lock or marker that shows an update is running (Discord, 2026-10-16).

Today Should be
Borea checks only whether KSA or StarMap already runs before a start. Borea also sees that the client updates KSA, does not start the game, and says that an update is running.

Before we build this, check against the real client how the sign is implemented: a lock file, a marker in the manifest, or something else, and when it appears and goes away.

Tests
  • With the update sign present, a start is refused with a message, and without it the start runs.
  • A sign that is left behind by a crashed client does not block starts forever (the rule follows what the client does).
Depends on

A lock or marker of the Ahwoo client during an update.

Dominant language
C#
Stars
29
Forks
3
Avg merge
17h 21m
Merged PRs (30d)
291

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KSAModding/Borea

All issues in KSAModding/Borea

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.