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

Crash - Block Statistics: If Player breaks Technical Blocks, Statistics are getting corrupted

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: Minecraft 13w37a, Minecraft 13w37b
    • Fix Version/s: Minecraft 13w41a
    • Environment:
      Windows 8.1 Pro Preview
      Java 1.7.0_40
      Nvidia GT 650M
    • Confirmation Status:
      Confirmed

      Description

      I'm currently crashing in version 13w37a when I try to get to the bottom of the "Blocks" statistics. I think it's caused by a block, maybe a special flower. Crashlog is in the attachment, I was already waiting for an automated Hopper Issue, but that might take a while. As I said, I have no idea which block caused this, might be carpet or one of the new flowers, or it's even another Issue.

      I looked for possible duplicates, haven't found any (also looked for hopper-reports: none). If you need more information, please tell me.

      Steps to reproduce (I'm not 100% sure, but this should work):
      -Create a new world
      -Copy the Galaxy_2Alex.json into the /world/stats folder
      -Rename the file to your name
      -Start the game
      -Try to look at the bottom of your Block statistics

      Attachement Nr. 2: I think it might be a good idea to attach the statistics. That might help to fix the problem. The file has never been edited, and it was created in 13w36a, together with the world.

      MOD EDIT
      It appears that any technical block stat crashes the game because it can't be rendered. Examples:

      stat.mineBlock.34
      stat.mineBlock.75
      stat.mineBlock.105 <- This is what the original reporter had.
      stat.mineBlock.117
      stat.mineBlock.132
      stat.mineBlock.140
      stat.mineBlock.144
      

      EDIT Galaxy_2Alex 15/09/2013:
      The block that crashes the game is the Melon stem, the same goes with Pumpkin Stem I guess. Currently, the only way to fix it is to delete the stat.mineBlock.104(/105) in the json file.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                galaxy_2alex [Mod] Galaxy_2Alex
              • Votes:
                2 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  CHK: