[Bug] Death by suffocation needs config in safe placement. Graves drop to ground below wall.

[Crosis47]

Minecraft Server Version

This server is running Paper version 1.21.11-130-ver/1.21.11@c5a2736 (2026-04-11T11:14:19Z) (Implementing API version 1.21.11-R0.1-SNAPSHOT)

GravesX Version

GravesX-4.9.11.1-366.jar

/graves dump output

https://mclo.gs/J9rLS28

Spark Profile / Performance Dump

No response

Summary of the bug

When dying by suffocation in a wall, the safe-placement system places the grave on the first safe block it finds below the suffocation location. Most of the time this puts the grave in places that make little sense or that are really far away from the actual death location. I don't remember this happening in previous versions prior to MC v1.21.11. A few examples:

1.) A player rode a horse into a 2-block tall opening on the surface which killed them by suffocation and the grave was placed 20 blocks down in the caves below.
2.) A player had died by suffocating in a gravel pit and the grave ended up in an Ancient City location about 50 blocks below where they had actually died, effectively making that grave extremely difficult for the player to retrieve and way farther away than it should be.

Steps to Reproduce

Die by suffocation with safe-placement enabled

Expected Result

The grave should be placed above where the player suffocated or if possible the plugin should be able to do a radius search and place on the first viable block found in the X or Z direction. This would allow for adjacent placement in the same Y level which would make far more sense than the current implementation.

Actual Result

Grave ends up nowhere near player death location and in most cases is far more difficult to retrieve than if it were just placed at the death location.

Screenshots / Videos

No response

Additional Information / Full Stack Trace

N/A

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.

[Legoman99573]

There isn't a suffocation check. That would be a feature request. Graves 4.9 didnt offer this either.