The unexpected behavior of getBedSpawnLocation causes Anchor's charging to be consumed

[404Setup]

Expected behavior

When calling player.getBedSpawnLocation(), if the player's respawn block is Anchor, the API will run normally as usual

Observed/Actual behavior

Anchor's charging is abnormally reduced

Steps/models to reproduce

1. Go to nether
2. Place an Anchor and charge it, then right-click to set the respawn point.
3. Call API: player.getBedSpawnLocation()
4. Observe the problem to occur

Plugin and Datapack List

[17:46:08 INFO]: ℹ Server Plugins (3):
[17:46:08 INFO]: Bukkit Plugins:
[17:46:08 INFO]: - LetsExpand, PlugManX, spark

Paper version

version
[17:46:28 INFO]: Checking version, please wait...
[17:46:30 INFO]: This server is running Paper version 1.21.4-221-main@c467df9 (2025-03-24T00:18:41Z) (Implementing API version 1.21.4-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.4-DEV-bc157c7 (MC: 1.21.4)

Other

No response