Skip to content

CTR Archipelago v0.1.4.1 (stability pre-release)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@dowlle dowlle released this 24 Jul 22:51
v0.1.4.1
f22eea3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

CTR Archipelago v0.1.4.1 (pre-release)

Pre-release / stability fix. This build adds crash protections for an in-race crash family reported since v0.1.4 shipped, plus new performance telemetry to help me chase reported stutters. It is marked pre-release because the crash fixes target rare paths that are hard to trigger on demand: the guards are code-reviewed, build-verified, and mirror a retail-verified sibling handler, but the exact averted-crash moments have not all been exercised in-game. If v0.1.4 is working fine for you, staying on it is a reasonable choice. If you have hit an in-race crash or feel stutters, this build is for you.

Fixed

  • Crash when an explosion catches a dropped TNT or Nitro sitting on a crate spot (reported twice within a day of the v0.1.4 release, both on Oxide Station, via the in-client crash reporter). The handler now checks the crate link the same way the game's own sibling handler does. (#136, part of the wider guard sweep tracked in #137)

  • Instance creation during thread-pool exhaustion now fails safely instead of crashing one frame later, and logs an [AP POOL] line so reports can tell me it happened. (#136)

  • Two more guards from the same family: the warped-burst weapon explosion and the spider shadow no longer crash if the instance pool is exhausted at their spawn moment. This exact guard content ran a full online multiplayer evening session without issues before release. (#139)

New: performance telemetry (please send me your stutters)

The client now watches its own frame timing and writes rate-limited [AP PERF] lines into ctr-ap.log when a frame stalls, attributing the stall to the network layer, the seed verifier, or the game engine itself. This costs nothing in normal play and exists purely so stutter reports become diagnosable.

If you feel stutters, lag spikes, or short hangs: please tell me. The most useful report is: your ctr-ap.log (or a support-bundle.bat archive), roughly when it happened, whether you were online in a multiworld or playing alone, and what was going on at that moment (race start, lots of weapons, a music or track change, connecting). Post in the Discord thread or open a GitHub issue.

Thanks to the players who sent crash bundles. The reporter upgrade from v0.1.4 is what made both crashes symbolizable, so if you crash, please do run support-bundle.bat and share the archive.

Compatibility

  • Client-only release. The v0.1.4 ctr.apworld stays current: keep your existing apworld, YAML, seeds, and saves. The guards are purely additive and change nothing in normal play.
  • Windows-only. Linux users stay on v0.1.4 for now; these fixes ship for Linux in the next full release.

Checksums

  • ctr-archipelago-v0.1.4.1-windows-x86.zip: df09310833cea540119c08d41159d595a4544ae8f5802f1bad7a0fe23c1a7728
Assets 7
Loading