{"version":"2.1.234","anchor":"a-command-can-decide-from-its-arguments-whether-it-counts-as","canonical_anchor":"a-command-can-decide-from-its-arguments-whether-it-counts-as","heading":"A command can decide from its arguments whether it counts as sensitive","tier":"internal","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/a-command-can-decide-from-its-arguments-whether-it-counts-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### A command can decide from its arguments whether it counts as sensitive\n\nCommands can now decide from their arguments whether to be treated as sensitive; nothing shipped uses it yet.\n\n**What**\n\nA slash command's sensitivity can now be a function of the text typed after it, not just a fixed yes or no, and the same check is used by both the transcript and the input handler. The \"isn't available over Remote Control\" rejection now echoes the command as `\/name ***` when it is sensitive instead of repeating what you typed. No command shipped in this build uses the function form.\n\n**Evidence**\n\n`isn't available over Remote Control.`\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}