Pressing Enter could interrupt a running turn and send your queued messages immediately, decided by server config.
The instant-send shortcut sits behind tengu_jiggly_mochi, whose in-source fallback is off.
tengu_jiggly_mochi Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.234: on
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new gate, tengu_jiggly_mochi, adds a shortcut that sends queued messages right away: while a turn is running in prompt mode, submitting interrupts the turn and flushes the queue. With it on, the input hint changes to "Press up to edit queued messages, Enter to send them immediately". Its in-source fallback is off, so whether it runs is decided by server configuration.
- The interruption is recorded with the source
queued_send_now, and the outcome under aninput_send_queued_nowcounter, withno_live_controlleras the failure reason when there is nothing running to interrupt. - Without the gate the hint stays at "Press up to edit queued messages".
- Neither the gate nor the counter existed in v2.1.233.
Press up to edit queued messages, Enter to send them immediately
Strings lifted out of the shipped bundle, so the claim above can be checked against them.