Skip to content

Schematic with invalid blockentity data #850

Description

@kezmodius

Is there an existing issue for this?

  • I have searched the existing issues.

Are you using the latest Structurize Version?

  • I am running the latest beta/release version of Structurize for my Minecraft version.
    I am also running the latest versions of other mods that are part of my problem.

Did you check on the Wiki? or ask on Discord?

  • I checked the MineColonies/Structurize Wiki or I asked on discord.

Minecraft Version

1.21

Structurize Version

1.0.832-1.21.1

MineColonies Version (if related bug)

1.1.1374-1.21.1

Related Mods and their Versions

Error showed up on both Wolfcraft server and clean instance.

Current Behavior

[19Aug2026 20:14:04.860] [Server thread/WARN] [minecolonies/]: Schematic with invalid blockentity data for block:Block{minecraft:dark_oak_log}[axis=y] in pack:Medieval Dark Oak schematic:minerx2top.blueprint blockentitydata:{}

I posted this line from our console log in discord today. Moobien asked me to test in a clean instance. It showed up there too, with even more named schematics.

Discord convo: https://discord.com/channels/139070364159311872/724810039281451028/1539921090405732433

He checked and posted these:

Image Image

Expected Behavior

Not to do that? I don't even understand what's happening.

Reproduction Steps

To test I made a basic instance,
Found a Medieval Dark Oak abandoned village and claimed it,
Pasted in a level one mine and house and let a citizen spawn.
Checked the logs once they reached the shaft bottom and started digging outwards.
Profit.

Logs

https://gist.github.com/kezmodius/46e4b72a04f23fee0d25fe95176e9cdd

Anything else?

Train said:
It seems to be a log, which somehow got NBT data
Not sure whether it is the tag anchor, if so, this is indeed a bug. It feels like it tries to apply the empty NBT in “entity” to a block which doesn’t have NBT (not sure whether entity should have been omitted, or whether it should not have tried applying it)

Footer


Viewers

  • Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
  • Add a comment if you have any insights or background information that isn't already part of the conversation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions