{"version":"2.1.295","anchor":"config-rows-commit-through-a-shared-writer-output-style-an","canonical_anchor":"config-rows-commit-through-a-shared-writer-output-style-an","heading":"Setting changes from slash commands now go through plugin hooks","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/config-rows-commit-through-a-shared-writer-output-style-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Setting changes from slash commands now go through plugin hooks\n\nCommands such as the output style command now save settings the same way `\/config` does, so plugin hooks can change or refuse them\n\n**What**\n\nSome slash commands change a setting directly, such as the command for choosing an output style or picking a model. They now save through the same path as `\/config`, so plugin hooks (code a plugin runs when something happens) can step in. New messages cover what can happen:\n\n- A plugin's hook changed the value. The command writes only what you picked, and points you to `\/config`.\n\n- The model changed while a plugin's hook was deciding, so you are asked to pick again.\n\n- The setting could not be saved.\n\nThe output style command can now report a different style from the one you picked.\n\n**Why**\n\nPlugins can now refuse or rewrite settings changes made from slash commands, so what ends up saved may not be exactly what you chose.\n\n- Area: Plugins\n- Names: `\/config`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}