Sign in
Skip to main content

Commands let players perform actions and customize gameplay using text-based instructions. Use this topic to share feedback and ideas for improving commands and related tools.

← Commands
16
Follow

A way to disable shared command feedback between operators

When an operator runs commands, the command output shows up in their chat, but it is also sent to other operators on the server as a gray message, like this:

[ExpertCoder14]: Changed the block at 0, 0, 0

This can get annoying when other operators run commands very often. To me, I find this quite a lot of junk messages in my chat, most of which I don't need to know about because I trust my fellow operators.

While the obvious way to turn off these grey messages is to use /gamerule sendCommandFeedback false, this also prevents players from seeing their own command feedback, which commands users find vital in knowing whether their commands succeed or not.

Therefore, I would like to propose a split of the two game rules for command feedback:

  • sendCommandFeedback: Whether the feedback from commands executed by a player should show up in their own chat. Also affects the default behavior of whether command blocks store their output text. 
  • sharedCommandFeedback: Whether the feedback from commands executed by a player should show up in other operators' chats.

The game rule commandBlockOutput already lets us disable operators from seeing outputs from command blocks. Why can't we have the ability to disable operators from seeing other player's command outputs too?

Avatar
Registered User shared this idea

1 Comments

Post a new comment:

Please sign in to leave a comment.

Date Votes
Sorted by oldest
  • 0
    Registered User commented
    Comment actions Permalink

    This would be great, I'm kind of surprised that it's not already a feature. Why on earth would would operators want to see EVERY command of every other operator in their chat window? That's what the console or log file is for.

    It irritated me so much, I did it myself. It's just a single tiny mixin. When the server calls broadcastToAdmins it asks for a list of users, forcing that response to an empty list prevents the broadcast. It preserves command feedback for the caller, preserves command logging to the log file and console, and everything else I tested.