Skip to content

feature: plugin settings read from servers, plugin config files written to every server that loads them - #489

Merged
lukepolo merged 1 commit into
mainfrom
feature/plugin-settings
Oct 2, 2026
Merged

lukepolo merged 1 commit into
mainfrom
feature/plugin-settings

Conversation

@lukepolo

@lukepolo lukepolo commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Plugin pages get real settings: servers report what each plugin cvar is for and defaults to, and a plugin's config file is managed in the panel and written to every server that loads it.

  • game_plugin_cvars, filled over RCON Cvarlist when a server running the plugin comes up; a value only counts as the default where no panel config sets it, and secret-looking cvars never get one
  • game_plugin_installs.config is written to the catalog's config_path on every server loading the plugin (a mode's or rotation's file at that path wins), and config_cvar is pointed at it
  • Registry sync stores config_cvar, config_default, config_shipped and forced_cvars
  • parseCvarList splits columns on :, so a URL value is no longer cut at https
  • Migration 1889000001700_plugin_settings plus Hasura metadata for the new table and columns

@lukepolo
lukepolo merged commit 4983783 into main Oct 2, 2026
2 checks passed
@lukepolo
lukepolo deleted the feature/plugin-settings branch October 2, 2026 18:48
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