Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Items in lazy chunks continue to age until they despawn #11404

Closed
Kroojel opened this issue Sep 15, 2024 · 1 comment · Fixed by #11412
Closed

Items in lazy chunks continue to age until they despawn #11404

Kroojel opened this issue Sep 15, 2024 · 1 comment · Fixed by #11412
Labels
status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. type: bug Something doesn't work as it was intended to. version: 1.21.1

Comments

@Kroojel
Copy link

Kroojel commented Sep 15, 2024

Expected behavior

Items in lazy chunks should not age

Observed/Actual behavior

The item age stays consistent until the chunks are fully loaded, then increases by how many ticks passed since the item last ticked

Steps/models to reproduce

  • Go into a non-spawn chunk
  • /forceload add ~ ~
  • throw an item 2 chunks away
    • If you would like to track the item do /data modify entity @n[type=minecraft:item] Health set value 10s
    • And to see the age /data get entity @n[type=minecraft:item,nbt={Health:10s}] Age
  • go in the nether to unload the chunks (or far away)
  • wait (or tick warp) 2000 ticks
  • return to see the age update to be 2000 higher than it was 1 tick ago (if over 6000 the item will despawn as expected)

Plugin and Datapack List

No plugins

No datapacks

Paper version

This server is running Paper version 1.21.1-77-master@4ff58c4 (2024-09-12T18:05:09Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
You are running the latest version

Other

No response

@Kroojel Kroojel added status: needs triage type: bug Something doesn't work as it was intended to. labels Sep 15, 2024
@lynxplay
Copy link
Contributor

lynxplay commented Sep 16, 2024

Replicable and apparently an "intentional change done by craftbukkit a long long time ago.
Does not mean that this behaviour is correct, but changes from 2013 are a bit before my time so will need some more team inputs. (see 1c18834)

@lynxplay lynxplay added status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. and removed status: needs triage labels Sep 17, 2024
@Machine-Maker Machine-Maker linked a pull request Sep 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. type: bug Something doesn't work as it was intended to. version: 1.21.1
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants