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.
This issue occurs under a very specific scenario: if the server removes a monster, and it is saved, except in the player's database. In this case, the monster type will cease to exist, and there may be an attempt to access memory that has already been freed, leading to a crash.
Even though this situation should not occur in a production environment (unless it's due to an error on the part of the server owner), I have decided to take preventive measures to avoid further complications.
Now, instead of causing a crash, the system will simply log a message informing that the monster must be removed from the player's prey list. This change enhances stability and provides clear information for troubleshooting if the issue ever arises.