Missing BlockEntity (Piston_Extension, ...)

This Block Entity is a Sticky Piston.

– BlockEntity missing instance data –
Details:
BlockState: minecraft:piston_extension[facing=up,type=sticky]
Block coordinates: World: (-167,70,69), Chunk: (at 9,4,5 in -11,4; contains blocks -176,0,64 to -161,255,79), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)

It should be worth noting that in other tickets, some of these had to do with chests, and one actually had to do with an Ender Portal block. However, I cannot remember if they were vanilla or not.

Has to do with flower pots in my case.

Seems to be the 1.10.1 client that has the bug. (Mac in my case).

I upgraded my server to 1.10.1 (from 1.10) and still get this crash on the client. No errors appear on the server.

Setting my client Profile to 1.10 (Minecraft Launcher -> Edit Profile -> Use version) lets me log into the server with no problems.

Setting the client Profile back to "use latest version" (i.e. 1.10.1) and reconnecting to my server causes the crash.

Now there's a popup saying "If you were trying to play on a multiplayer server, please contact the server administrators." That's not much help, seeing as it's nothing to do with the server. 😞 Or are server admins expected to search the world for every sticky piston manually?!? :o)

Probably not a surprise, but this happens on my Linux client as well. Gentoo client on JRE 1.8u92, Ubuntu server on JRE 1.8.73, issue started on upgrade to 1.10.1, upgrading server didn't help, relaunching client as 1.10 seems stable.

Getting the same issue. Says:

– BlockEntity missing instance data – Details: BlockState: minecraft:flower_pot[contents=cactus,legacy_data=2] Block coordinates: World: (291,70,582), Chunk: (at 3,4,6 in 18,36; contains blocks 288,0,576 to 303,255,591), Region: (0,1; contains chunks 0,32 to 31,63, blocks 0,0,512 to 511,255,1023)

Downgrading from 1.10.1 to 1.10 fixed this issue for now, but not sure if its going to be an issue going forward.

My minecraft just crashed and directed me to this JIRA issue. I think this must be the first time I've had a crash direct me like this. I had an identical crash earlier, except that time it didn't give me an error message directing me to this JIRA isue.

Anyway, running a vanilla client connecting to a locally hosted vanilla server (both 1.10.1).

I'd like to note that this issue does not seem to be consistent. I've been building in an area away from my main base, and the game works just fine out there for hours on end. I come back to my main base to drop off mined material and pick up other stuff, then head back out. So I've been back to my main base 5 or 6 times in the past few hours, and I've only crashed twice. Both times it said it was due to a piston. While I have quite a few pistons around my base, only a single set activates in an automatic mechanism, and tracing the co-ordinates of the piston listed in the crash report goes to one of these pistons (used in a pumpkin auto-harvesting machine).

But I can't use Realms on 1.10...

The issue seems to be caused by looking at extending/retracting pistons from far away, in creative mode in my case (I was building a redstone printer with pistons).

I believe it's long distance usable blocks in general, considering I've seen crashes that involved chests and even an Ender Portal block.

Hello everyone!
Had the same thing happen to me on both a newly created 1.10.1 single player file as well as a 1.10.1 realms file in vanilla. Installing a command block creation would cause it to crash, and on realms, would give the same error to both me and my friend on the server. Got the error codes MC-103978 and MC-103981. Changing your client to 1.10 rather than 1.10.1 resolves the issue, both for single player and for realms servers. Allowing the world to render prior to installing the one command creations did not resolve the issue in 1.10.1. Crash report always reported a missing BlockEntity.

Did a test where my friend was able to be on the server with the working command creation in a 1.10 client (on realms) and it worked perfectly fine but when I went and changed back from 1.10 to 1.10.1 and got on, it would crash. Something in the 1.10.1 update is causing the issue, preventing people from getting onto their personal servers as well as multiplayer servers. ONLY WAY TO RESOLVE CURRENTLY IS TO CHANGE CLIENT TO OLDER VERSION OF 1.10. Hope this helps!

Time: 6/22/16 6:57 PM
Description: Server forgot to send required information to construct BlockEntity

java.lang.RuntimeException: Missing BlockEntity
at bqy.b(SourceFile:162)
at bqu.a(SourceFile:100)
at bqu.run(SourceFile:43)
at java.lang.Thread.run(Thread.java:745)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

– BlockEntity missing instance data –
Details:
BlockState: minecraft:repeating_command_block[conditional=false,facing=east]
Block coordinates: World: (155,68,241), Chunk: (at 11,4,1 in 9,15; contains blocks 144,0,240 to 159,255,255), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)

A (Repeating) Command Block this time?

I am most certainly convinced this is from usable blocks.

– BlockEntity missing instance data –
Details:
BlockState: minecraft:repeating_command_block[conditional=false,facing=east]
Block coordinates: World: (155,68,241), Chunk: (at 11,4,1 in 9,15; contains blocks 144,0,240 to 159,255,255), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)

It seems to be block/tile entities generally.
In my case it's so far CommandBlocks, Beacon, Chest, Sign, Flowerpots, Comparator, Dispenser, Jukebox, Piston extensions (also with no pistons present, just the technical block itself).

Everything was already placed in pre-1.10.1 worldsaves. I did not try yet to reproduce a crash with newly placed block entities.

Note: If the crash causing block entity is a CB, then (at least in my case) if it contained data such as a command inside, then this command will be erased, not the commands inside the other non-faulty CBs in the same worldsave though.
I went from 1.10.1 back to 1.10 to delete a faulty CB (to see if it fixes it or if there are more faulty CB), and when I checked the faulty CB in 1.10, the commandline was empty.
This happened to all CB, and I'm 100% sure there were commands in them before.

I'm not sure yet if this applies to all faulty block entities.

Possible crash candidates = Block entities, ✔ =crash occurred according to this bugpost, :blue_star:=crash occurs continuously in my own worldsaves (links to currently 15 partially large worldsaves will be passed to the Devs):

Banner
:blue_star: Beacon
Brewing stand
:blue_star: Chest+Trapped Chest | Chest
:blue_star: Comparator
✔ :blue_star: Command Block | ICB + CCB + RCB
Daylight Sensor
✔ :blue_star: Dispenser
Dropper
Enchantment Table
Ender Chest
End Gateway
End Portal
✔ :blue_star: Flower Pot
Furnace
:blue_star: Jukebox
Hopper
Mob Head
Monster Spawner
Note Block
✔ :blue_star: Piston extensions
:blue_star: Sign
Structure Block

If you have a setup that causes this issue for command blocks please attach it to this ticket.

Sign: https://bugs.mojang.com/browse/MC-104429