{"version":"2.1.228","anchor":"synced-skills-can-no-longer-take-a-slash-command-name-that-s","canonical_anchor":"synced-skills-can-no-longer-take-a-slash-command-name-that-s","heading":"Synced skills can no longer take a slash-command name that sometimes exists","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/synced-skills-can-no-longer-take-a-slash-command-name-that-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Synced skills can no longer take a slash-command name that sometimes exists\n\nSynced skills can no longer take over slash-command names that only exist in some states.\n\n**What**\n\nSlash commands that only appear in certain states (fleet fork, fleet background, daemon, skill doctor, logout) now reserve their names permanently. A skill synced from your account that collides with one of those names, or with a local or plugin command, is dropped and logged instead of shadowing it.\n\n**Details**\n\n- Each conditional command set now declares both the names it uses when open and the names it uses when closed, and every name from both lists is reserved.\n- If local or plugin skills fail to load at all, every synced skill is dropped, because there is no way to check its name for collisions.\n\n**Evidence**\n\n`a non-synced command or an earlier synced skill owns that name`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}