Skip to content

feature: Add the Cookies plugin, which Retakes keeps preferences in - #10

Draft
Flegma wants to merge 1 commit into
mainfrom
feature/cookies-plugin
Draft

Flegma wants to merge 1 commit into
mainfrom
feature/cookies-plugin

Conversation

@Flegma

@Flegma Flegma commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator

Adds Cookies (SwiftlyS2-Plugins/Cookies, MIT), the per-player and per-server key-value store other SwiftlyS2 plugins share.

Why

The Retakes entry already says "Loadout preferences persist when the Cookies plugin is installed", but Cookies isn't in the registry, so a 5Stack server can't install it. Without it Retakes logs "Cookies shared interface is not registered. Player preferences will not be persisted." Its own database code is not used; everything goes through Cookies.

The entry

  • Cookies-v*.zip is the plugin. The release also ships Cookies.Contract-v*.zip (the interface for plugin developers), which the glob doesn't match.
  • layout: plugin, installed to addons/swiftlys2/plugins (the zip has a Cookies/ folder at its root, like Retakes).
  • It asks SwiftlyS2 for a connection named cookies. SwiftlyS2 falls back to the default connection when none has that name, so a server with one database from the Databases page needs nothing more.
  • pairs_with: ["retakes"].

Tests

  • npm run validate and npm test pass; a local npm run build resolves 1.0.14 (published 2026-11-02).
  • On our panel: not yet. This stays a draft until Retakes keeps a player's preferences across a reconnect there.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant