Please remember this category is for features inside the latest pre-release only. To make a new suggestion for Java (like a block or gameplay suggestion), please use the appropriate category for your suggestion.

← Minecraft: Java Edition Snapshots
104
Follow

Make Confirm Command Execution to an Option

Make the "Confirm Command Execution" (that's the message (since 25w20a) you have to click yes, if you want to execute a command over your permission level by clicking a message or dialog) to be off switchable by an option in the Accessebility Settings

Avatar
Registered User shared this idea

12 Comments

Please sign in to leave a comment.

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

    Yes, because it's too ennoying

  • 12
    Registered User commented
    Comment actions Permalink

    I genuinely don't understand how this oversight was made by the team.

    I've been making an adventure map for over a year now, almost completely finished it, been working hard the past few weeks...

    Just to find now that the dialogue prompts that you click on in chat to choose your response or continue the story are completely unusable now.

    Nobody is going to want to click yes every time they have to do that.

    Come onnn guys.

  • 10
    Registered User commented
    Comment actions Permalink

    Seriously, I'm making a server and interactive books are a huge part of it. Having to click a pop-up to confirm something that is supposed to make the process of initiating the command *faster* is just plain stupid.

    This being "for security" is not a valid reason. We've been fine without it for the past 16 years why do I need to do an in-game captcha to run a command all of a sudden??

     

  • 6
    Registered User commented
    Comment actions Permalink

    Please! So many adventure maps are ruined by this extra prompt! Have mercy! You have turned thousands of hours of my work into nothing because with this prompt, my maps are unplayable!

  • 5
    Registered User commented
    Comment actions Permalink

    All my command books got messed up because of this feature. Mojang, PLEASE

  • 6
    Registered User commented
    Comment actions Permalink

    Wenn das nicht auszuschalten ist, werde ich wohl immer auf 1.21.5 bleiben müssen. Ich habe Minecraft seit 11 Jahren. Jetzt bin ich frustriert

    If I can't turn this off, I'll probably have to stay on 1.21.5 forever. I've had Minecraft for 11 years. Now I'm frustrated.

  • 5
    Registered User commented
    Comment actions Permalink

    Hey, I've been working on an adventure map for about 4 years now with an NPC dialogue mechanic utilizing this feature. This really throws a wrench in the immersion and convenience of command input in the game by the player. 
    If we could reconsider this and potentially make it toggleable at the very least, that would be absolutely beneficial to many other map developers everywhere. Thank you. 

  • 1
    Registered User commented
    Comment actions Permalink

    ill quit the game if they dont fix this

  • 7
    Registered User commented
    Comment actions Permalink

    As a mapmaker, it's annoying that anytime I want to run a command in a certain way (clickable chat message, dialog, sign, etc.), players will be prompted with a confirmation box. This is going to be confusing for a lot of players, adding another layer of friction to an interaction.

    There's an easy workaround by moving the command you want to run to a ticking function and replacing the original command with a /trigger command. The original command then runs when it detects that the trigger command was run. This makes it useless as a safety feature, as anybody who wants to run commands maliciously can just do this to avoid it.

    So what's the problem if there's an easy workaround? The biggest problem is that it adds unnecessary ticking (a small performance hit) and it makes data pack organization a little bit more annoying. Instead of being able to see the command immediately, you have to look in a separate file and reference the scoreboard value that your trigger command sets.

    The warning itself is also not particularly useful. Any command can be obfuscated by putting it into a function. Instead of seeing the actual command, players will just see "/function foo:bar". Beyond that, it's clear the warning was added to prevent malicious use of commands, but anybody with bad intentions has dozens of other options, so adding a warning to one method isn't going to stop anybody.

    Overall, the feature is annoying for mapmakers, unhelpful for players, and ineffective at stopping bad actors.

  • 2
    Registered User commented
    Comment actions Permalink

    yup this broke my command books as well

  • 0
    Registered User commented
    Comment actions Permalink

    Thought this was an oversight at first but the fact that this hasn't been fixed for months is ridiculous. 

  • 3
    Registered User commented
    Comment actions Permalink

    Since dialogs are often used in custom content maps or servers, this screen is USELESS.