{"version":"2.1.233","anchor":"slash-command-arguments-can-no-longer-be-expanded-as-placeho","canonical_anchor":"slash-command-arguments-can-no-longer-be-expanded-as-placeho","heading":"Slash-command arguments can no longer be expanded as placeholders","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/slash-command-arguments-can-no-longer-be-expanded-as-placeho","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Slash-command arguments can no longer be expanded as placeholders\n\nText you supply to a slash command can no longer be re-read as another placeholder.\n\n**What**\n\nWhen a custom slash command's body is filled in with `$1`, `$ARGUMENTS`, `$ARGUMENTS[n]` or named arguments, the text you supply is now protected so it cannot itself be read as another placeholder and expanded a second time.\n\n**Details**\n\n- Each substituted value is fenced with internal marker characters and its `$` escaped; the markers are stripped once expansion finishes.\n- The template and every value are first scrubbed of those marker characters (U+FFFF and U+FFFE), which are replaced with the replacement character, so argument text cannot forge a fence.\n\n**Evidence**\n\n`e.replaceAll(vLr, \"\\uFFFD\")`\n\n- Area: Slash Commands\n- Names: `$ARGUMENTS`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}