feature: serve plugins' workshop addons through AddonsManager - #211
Merged
Merged
Conversation
This was referenced Oct 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AddonsManager is no longer practice-only: any SwiftlyS2 server whose plugins list workshop addons (
WORKSHOP_ADDONS, sent by the API) turns it on and serves exactly those, along with the practice HUD's addon.workshop_addon_idsin util.sh: dedupes, keeps order, drops anything that is not a bare numeric id with a warning (AddonsManager drops its whole config over one bad entry)enable_addons_managerin util.sh: links the image's AddonsManager and writes its config throughmaterialize_for_write, same as the practice HUD did, now sharedTogether with 5stackgg/plugin-registry#6, 5stackgg/api#498, #211 and 5stackgg/web#680.