-
Notifications
You must be signed in to change notification settings - Fork 565
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
Code maintenace of Stats Entities #4750
Conversation
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.
Code changes appear fine. Only thing that may come up in testing is if something is nulled that something still tries to access.
It is mostly a safety net due to GC errors in death statistics being deleted, otherwise entities are very rarely deleted |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself |
Conflicts have been resolved. A maintainer will review the pull request shortly. |
About the pull request
= null
Destroy
with proper clearing to all entitiesExplain why it's good for the game
Code maintenance
Testing Photographs and Procedure
Didn't see anything wrong but best tested in TM
Changelog
Nothing player facing