Lodestone Compass not working properly with unloaded chunks
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
When destroying Lodestone linked compasses stops pointing to lodestone location
Observed/Actual behavior
Compass in some situation still points out towards lodestone location even if Lodestone is destroyed
Steps/models to reproduce
- Place Lodestone and link a compass to it
- Put linked compass to your enderchest
- Destroy the Lodestone
- Unload the chunk the Lodestone was placed (i teleported away)
- Remove linked compass from your enderchest (right now it will still point towards former direction)
- Load the chunk lodestone was placed (i teleported back)
- Upon loading compass, acknowledges lodestone removal and start pointing in random direction
Plugin and Datapack List
[21:31:13 INFO]: Server Plugins (14):
[21:31:13 INFO]: Bukkit Plugins:
[21:31:13 INFO]: - ICraft2.0-Special, *JoinFullServer, Multiverse-Core, Multiverse-Inventories, Multiverse-Portals, NoChatReports, *PermissionsEx, PexTabCompleter, ProtocolLib, *SimplePrefix-Reloaded
[21:31:13 INFO]: TreasureChestX, *VoidWorld, WorldEdit, WorldGuard
[21:31:24 INFO]: There are 3 data pack(s) enabled: [vanilla (built-in)], [file/bukkit (world)], [paper (built-in)]
[21:31:24 INFO]: There are no more data packs available
Paper version
[21:35:54 INFO]: Checking version, please wait...
[21:35:54 INFO]: This server is running Paper version 1.21-119-master@100d75a (2024-07-29T16:00:13Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21-109-5a5035b (MC: 1.21)
Other
There is also breakage in my custom plugin behaviour regarding storing serialazed linked compass in PersistentDataContainer, but I believe resolving shown issue will also fix that issue, so I'm not providing data at this moment for the plugin
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported sequence with a Lodestone-linked compass, an unloaded chunk, and an ender chest on Paper 1.21-119. The issue names no source files, tests, or entry points, so trace the Lodestone compass behavior and identify where unloaded or destroyed targets are resolved. Done means the compass no longer points to a destroyed Lodestone before its chunk is reloaded, with regression coverage for the sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100