-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Fix MC-125757 #3859
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
Fix MC-125757 #3859
Conversation
|
(minor) 20 ticks == 1 second. Should be 200 ticks :) |
Tried to get that typo fix in before anyone could comment :P |
|
This really should have a config option which allows one to restore the normal behavior as this is a breaking mechanic change for some redstone maps using the despawning as a timer (e.g. with arrows falling through cobweb) |
|
phoenix, maybe I don't understand what you mean. The pr doesn't make arrows despawn in 10 seconds. It starts their natural despawn counter after 10 seconds. Natural despawn for arrows is 5 minutes, iirc, so these "cobweb timers" still have 5 minutes (plus 10 seconds) to work.. What this fixes is the cases where arrows literally get stuck in a state where the despawn counter never starts counting. Bubble columns, being the most notable scenario. If a server requires more than 5 minutes of arrow life, they already have that option to set a higher despawn time. |
|
Apparently arrow cobweb timers aren't a thing (anymore? I swear they were in the past) so I guess this doesn't hurt too much beyond some TNT-Arrow-cannons |
Just out of curiosity, would dropper+item+cobweb timer be different? Because until now you could have them be delayed more than 5 minutes? Or would they provide a sufficient alternative? |
|
@lerokko This patch only affects shot arrows, no other entity. |
|
Need this for Llama spit too. |
MC-125757 has been marked as works-as-intended, meaning paper's changes to forcefully despawn arrows are breaking vanilla behaviour. Given paper also now implements entity-based time to live options, this kind of behaviour can be replicated by server admins anyway. See: PaperMC#3859
Change PaperMC#3859 forces all arrows to despawn after 10 seconds to fix MC-125757, but this was marks as works-as-intended. This change allows admins to configure this value (or disable with -1) while keeping the existing behaviour
This forces the despawn counter to start ticking regardless of
state after the arrow has been alive for 200 ticks (10 seconds)
instead of getting stuck in a never despawn state (bubble columns,
etc).
https://bugs.mojang.com/browse/MC-125757