fix: Avoid possible crashes with getCorpseFromItem and playerRewardChestCollect #514
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
getCorpseFromItem
item->getParent()->getContainer()chain by checkingparentbefore dereferencing, preserving special handling forITEM_BROWSEFIELDwithout risking anullptrdereference.playerRewardChestCollect
item->getContainer()->getParent()->getTile()access chain by validatingcontainer,parent, andtilebefore use. If any component is null, the code avoids a crash and proceeds by directing rewards toplayerRewardChest.