{"version":"2.1.238","anchor":"slash-command-output-no-longer-lands-in-the-wrong-place-afte","canonical_anchor":"slash-command-output-no-longer-lands-in-the-wrong-place-afte","heading":"Slash command output no longer lands in the wrong place after a clear","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/slash-command-output-no-longer-lands-in-the-wrong-place-afte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Slash command output no longer lands in the wrong place after a clear\n\nClearing the conversation while a slash command runs no longer dumps its output in the wrong spot.\n\n**What**\n\nWhen a slash command is still running and you clear the conversation, its output is now discarded rather than appended to whatever is on screen. Output that still has its originating row is inserted directly after it.\n\n**Details**\n\n- The discarded case logs a line and returns the command with an empty message list, leaving the transcript untouched.\n\n**Evidence**\n\n`settled after its transcript row was cleared`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}