-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
DespawnOnExit / DespawnOnEnter fix log spam #21864
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
base: main
Are you sure you want to change the base?
Conversation
|
CI has found a couple of spelling errors for you :) |
Typo fixes
Fixed! |
mgi388
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I left suggestions for nits on doc comment formatting for consistency with what is there. Feel free to apply the suggestions yourself, I just did it with the PR reviewer so hopefully I got the suggestions right.
Co-authored-by: mgi388 <[email protected]>
Thank you changes applied. |
janhohenheim
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes, I've run into this plenty of times. Thanks!
if entity was despawned such as in a hierachy
Objective
Most if not all use cases don't care if the item is already despawned.
The user is typically saying "Ensure it is despawned" rather then "You should be the one to despawn"
DespawnOnExit/DespawnOnEntercauses log spam when despawning hierarchies #21832Solution
Testing