Jump to content

Easter Holiday SALE 40% OFF ends in:

Thank you for support!

HOTKartoffel

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by HOTKartoffel

  1. Your Name: HOTKartoffel
    Claim Owner Name: Was claimed by HOTKartoffel, but abandoned while trying to solve the issue myself first
    Coordiantes: 4909,103,-2300 (from crash report)
    Screenshots (Optional): no screenshot, minecraft crashes when i look in the direction of the block

    The Block in question is a pattern replicator from cyclic or one of its preview blocks. Removing the 5x5x5 space centered on the block (4907,101,-2298 to 4911,105,-2302) would be a good idea.

    Thanks in advance.

  2. Minecraft name: HOTKartoffel
    Server: Dungeons Dragons and Space Shuttles

    Me and two other players are stuck in a region wich causes our game to crash as soon as we login, wich would not be a problem, if its was not our home with everything we build.

    The crash report reads:

    ...

    Description: Rendering Block Entity

    java.lang.NullPointerException
    ...

    It happened after placing and using a pattern_replicator from cyclic and the crash report mentions it(or its preview blocks) as the cause:
    ...
     Block type: ID #5255 (tile.builder_pattern // com.lothrazar.cyclicmagic.block.builderpattern.BlockPatternBuilder // cyclicmagic:builder_pattern)
     Block data value: 0 / 0x0 / 0b0000
     Block location: World: (4909,103,-2300), Chunk: (at 13,6,4 in 306,-144; contains blocks 4896,0,-2304 to 4911,255,-2289), Region: (9,-5; contains chunks 288,-160 to 319,-129, blocks 4608,0,-2560 to  5119,255,-2049)
    ...

    I have used the unstuck package and returned to spawn, just to crash again as i returned to our home.
    I would be grateful if this can be solved. Thanks in advance.

×
×
  • Create New...

Important Information

By using this site you agree to the following Terms of Use, Guidelines and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.