[Flegma]

Points the Retakes entry at EsportAdria/SwiftlyS2-Retakes, our fork of a2Labs-cc/SwiftlyS2-Retakes. The fixes are offered upstream as a2Labs-cc/SwiftlyS2-Retakes#28 and #29; if they are merged and released there, this entry can go back.

Why

With Cookies 1.0.14 installed next to Retakes, Cookies can fail to load (Could not load type 'Cookies.Contract.IPlayerCookiesAPIv2' from assembly 'Cookies.Contract, Version=1.0.0.0'), and then Retakes cannot save player loadouts. Seen on our Retakes server on 2026-11-02. Retakes bundles an old Cookies.Contract.dll with only the v1 interfaces, and SwiftlyS2 keeps one export per assembly name (the last folder scanned wins, no version check), so the old copy can replace the one Cookies needs. Our fork's v1.5.2 ships the Cookies 1.0.14 contract.

Upstream master also does not build with current SwiftlyS2.CS2 (BeamType_t.BEAM_HOSE was renamed), which is why it says 1.5.2 but its last release is 1.5.1. The fork fixes that too.

What changes

• variants.swiftlys2.repo, homepage and author move to EsportAdria; the description says whose fork it is.
• The asset name (Retakes-v*.zip), layout and install path stay. Our release workflow is upstream's own, so it publishes Retakes-v1.5.2.zip (matched) and Retakes-no-maps-v1.5.2.zip (not matched), with the same layout as before.
• The versions list restarts at v1.5.2: GitHub doesn't copy releases into a fork, so the 1.5.1 and older builds drop out of the catalog. A panel with 1.5.1 installed sees 1.5.2 as the update.

Tests

• npm run validate and npm test pass.
• Our fork's v1.5.2 release: not yet made. In game on our Retakes server: not yet. This stays a draft until both are done.