You'll notice
Useful3 Signal1
Text you supply to a slash command can no longer be re-read as another placeholder.
What's wrong with this entry?
Anonymous. No account, no email.
$ARGUMENTS
What
When 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.
Details
- Each substituted value is fenced with internal marker characters and its
$escaped; the markers are stripped once expansion finishes. - 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.
Evidence
e.replaceAll(vLr, "\uFFFD")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command