-
Notifications
You must be signed in to change notification settings - Fork 289
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
ItemPhysic custom despawn time compatibility #2115
Comments
This would be an issue in 1.12, which is only getting critical bugfixes. |
I though this feature is part of 1.15 as well? |
This feature isn't in 1.15, no.
…On Tue, May 12, 2020 at 2:55 PM CreativeMD ***@***.***> wrote:
I though this feature is part of 1.15 as well?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2115 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANWFL5YYEQOCJKVN62N7ZLRRFILHANCNFSM4MYCTG2A>
.
|
Oh ok, sorry, I thought it was. Thanks for your help anyway! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there,
I'm the author of ItemPhysic. Looks like Quark's feature of flashing items before they despawn doesn't work with a custom set despawn time. I'm not 100% sure how to add compatibility. The lifespan of an item is not synchronized with the client, I could add that. This would require some changes on your end as well, because you get the despawn time from the item if it's not default.
Would love to hear your thoughts about it.
In Regards
CreativeMD
The text was updated successfully, but these errors were encountered: