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

In the debug world, the birth point is at Y=2 And after debugging kill in the world

XMLWordPrintable

    • Unconfirmed
    • Spectator

      the 7 report

      Be careful. This vulnerability report may be considered invalid. Please put a copy here.

      This question still made me somewhat "envious", so I saw a very low place.

      What I expected to happen was...:

      It will not be born under the barrier so that it can be quickly viewed after flight.

      What actually happened was...:

      The problem was seen, so I was born below the barrier, Y=2.

      Steps to Reproduce:

      1.Open the creation of the world option

      2. click more options

      3. select the optional mode, and then hold the shirt key

      4. click on the world type, and then you can see "debug mode".

      5. click create the world, and wait for the world to load

      6. after the load is loaded, open the debug screen

      And there's another way, kill
      1. ensure that you are above Y=60
      2. use killĀ ( /kill @p )
      3. press rebirth, you will be born at Y=2

        1. loophole_step_1.png
          loophole_step_1.png
          72 kB
        2. loophole_step_2.png
          loophole_step_2.png
          87 kB
        3. loophole_step_3.png
          loophole_step_3.png
          79 kB
        4. loophole_step_4.png
          loophole_step_4.png
          71 kB
        5. loophole_step_5.png
          loophole_step_5.png
          53 kB
        6. loophole_step_6.png
          loophole_step_6.png
          193 kB
        7. kill_step_1.png
          kill_step_1.png
          476 kB
        8. kill_step_2.png
          kill_step_2.png
          478 kB
        9. kill_step_3.png
          kill_step_3.png
          171 kB

            Unassigned Unassigned
            likemojang2 likemojang2 (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: