fix: crash related to getName methods with deleted creature #1080
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.
Description
Because they are classes with virtual implementations, after the creature is deleted it crashes when trying to access the wrong getName methods. Doing the manual implementations of each class solves the problem of crashing in an addEvent lua.
Resolves #513
Behaviour
Actual
Crashes when trying to access a monster/player that has already been deleted from memory through the lua Creature(name or id) method.
Expected
No more crash.
Type of change