Skip to content

Plonk mod compatibility issue. Wrong orientation when turning blueprint. #811

@SpatzAufGit

Description

@SpatzAufGit

Is there an existing compatibility issue for this mod?

  • I have searched the existing issues.

Are you using the latest Structurize and your mod 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 ask on Discord?

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

Minecraft Version

1.21

Structurize Version

1.0.799

Your Mod Name and Version

Plonk

Related Mods and their Versions

  1. NeoForge 21.1.217
  2. Structurize 1.0.799
  3. Plonk 10.0.6 (https://www.curseforge.com/minecraft/mc-mods/plonk)

Others if needed:

  • BlockUI 1.0.205
  • Domum Ornamentum 1.0.227
  • MineColonies 1.1.1231
  • Multi-Piston 1.2.58

Current Behavior

When placing a Plonk item into the world and capturing it inside a Structurize blueprint, the item is copied correctly. However, when rotating the blueprint (e.g., turning it 90°), only the position of the Plonk item rotates.
The orientation of the Plonk item does not rotate and remains fixed to its original direction (e.g., always facing north).
This results in incorrect blueprint rotations and misaligned decorative items.

Image

I have attached a screenshot that illustrates the issue.
In the upper left, you can see the original setup in its default orientation. On the pink wool, there are vanilla items (a redstone torch and a ladder), and on the yellow wool, there are three Plonk‑placed items.

In front of that, the screenshot shows the same blueprint rotated 90° using Structurize. The positions of the Plonk items rotate correctly, but their orientation/facing direction does not change. They continue to face the original direction (e.g., north), resulting in incorrect placement after rotation.

On the right side, the screenshot shows the Structurize Builder’s Tool preview. Plonk items appear as a “P” in the template, but again, their orientation does not rotate when the blueprint is turned.

This is also the case for items placed with plonk on the ground as the second screenshot shows.

Image

Expected Behavior

When rotating a Structurize blueprint that contains Plonk items, both the position and the orientation of the Plonk items should rotate consistently.
The rotated blueprint should preserve the intended facing direction of each Plonk item, just like vanilla blocks that support rotation.

Reproduction Steps

  1. Place any Plonk item into the world (e.g., an item placed on the ground or on a surface).
    (default key to place is "P" with the item in hand and looking at the block to place on.)
  2. Use Structurize to create a blueprint that includes the Plonk item.
  3. Load the blueprint into the Builder’s Tool.
  4. Rotate the blueprint (90°, 180°, etc.).
  5. Observe that the Plonk item’s position rotates correctly, but its orientation/facing direction does not change.

Logs

No relevant log output. The issue is visual.

Anything else?

Using Plonk inside MineColonies buildings adds a lot of value to interior design. Many profession‑related rooms (e.g., bakeries, smelteries, libraries, guard towers) look much more alive and functional when decorated with Plonk items that visually match the building’s purpose. Without them, interiors often feel empty compared to what they could be.

Because the orientation of Plonk items does not rotate with Structurize blueprints, it becomes impractical to include them in larger building sets. Creating separate blueprint variants for every rotation and mirror state is not feasible, so Plonk items end up being avoided entirely despite their usefulness.

I also tested this behavior on Minecraft 1.19 and 1.20 using Forge, and the same orientation issue occurs in both versions.

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.

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