Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-199034

Command Line Does Not Scroll with Selection in a Command Block

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.16.2
    • Mac Catalina, 2019
      Minecraft Java Edition 1.16.2
      Affects both singleplayer and multiplayer
    • Unconfirmed
    • (Unassigned)

      Summary

      Prior to the 1.14 update, if a long command string was placed in a command block, you could easily use Shift (+ Ctrl) + L/R Arrow to select a part of the command in the command line and the command would scroll with the selection if the selection went out of view. However, after 1.14, this no longer works. Tested in 1.16.2, the problem still persists.

      Example

      I have a string that lists numbers 1 - 27 typed into a command block. I place my cursor before the number 1, then use Shift + Right Arrow to select forward.

      Prior to 1.14:

      The command line scrolls to reveal what is being selected. The number 27 is visible.

      1.14 to Present:

      The command line does not scroll to reveal what is being selected. The number 27 is selected but is off-screen.

      This is only an example and I realize that Ctrl + A selects the entire string. This problem specifically hinders the selection of a segment of code, not the entire line.

      Reason

      Some may think this isn't much of a problem because mapmakers and coders should be using functions or some other method of typing long commands, but that isn't an excuse to make something less intuitive. What about beginners? Or people who do not prefer to switch over from command blocks? Or even those, like myself, who need this functionality for testing a specific line of code before implementing it in a function? It's very minor, but it's definitely infuriating.

            Unassigned Unassigned
            iGrantastic Grant Chapman
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: