Text your client already composed is sent as written, even if it starts with a slash.
What's wrong with this entry?
Messages arriving with client_composed set are now enqueued with slash-command parsing skipped, so a message that happens to start with / is sent as written. Messages with either client_composed or seeded_summon also skip attachment expansion, so @file references are not materialised a second time.
- Applies in the stdin and remote-IO inbound message loop.
- No flag; the behaviour follows entirely from the flags on the incoming message.
...(r.client_composed === !0 && { skipSlashCommands: !0 }),
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