Skip to content

[Bug] 2026.4.9.1 : MC 26.2 : Pistons can break the grave player head block but not the grave itself #261

Description

@Limeen

Minecraft Server Version

Purpur 26.2-2609-6726940 (MC: 26.2)

GravesX Version

GravesX-2026.4.9.1.jar

/graves dump output

https://venstone.xyz/share/gravesx-dump-1785177503091.txt

Spark Profile / Performance Dump

No response

Summary of the bug

When the option piston-extend: false is set in grave.yml, the grave is protected from the piston break but not the block itself.

Steps to Reproduce

  1. Make graves to be a player head block
  2. Create a grave by dying in-game
  3. Place a piston and actionnate it to break the grave
  4. The grave container and holograms are not deleted but the player head is broken

Expected Result

The piston should be blocked and unable to broke the player head block (as if the piston was trying to push a bedrock block)

Actual Result

The piston is able to push the player head block (grave) and players can literally take the grave in their inventory, however the container and holograms are staying in place and the hitbox to open the grave is really small

Screenshots / Videos

https://venstone.xyz/share/graves.mp4

Additional Information / Full Stack Trace

The console doesn't show any error

Environment & Support Confirmation

  • I confirm this issue occurs on the latest GravesX release or development build, not an outdated version.
  • I understand that if I use development builds in a production environment and lose data, I will not receive support for that data loss.
  • I understand that issues caused by other forks or Graves 4.9 are not supported here and may be closed.
  • I am not running an outdated version of GravesX for this report.
  • I am not using a Plugin Manager/Management plugin to load/unload GravesX. I understand these cause many behavioral issues and are not supported.
  • I have checked existing issues and confirmed this is not a duplicate.
  • I understand that reports with insufficient information or using outdated versions may be closed. I may open a new report after updating and providing full details.
  • I am running a supported server type (Spigot, Paper, Folia, etc.) and not a hybrid jar (e.g. Mohist), which is not supported.
  • I have tested with only GravesX installed (or with minimal plugins) to rule out plugin conflicts where possible.
  • I am not just clicking checkboxes at random; I have read and understood the above.

Activity

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions