Cherry Pick: Monster overspawn #4328
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-Authored-By: Marcin Michalski <57528542+marmichalski@users.noreply.github.com>
EPuncker
reviewed
Feb 18, 2023
EPuncker
approved these changes
Feb 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Prelude
Changes Proposed
Allow for monster overspawn instead of teleport/remove.
When the monster goes out of defined deSpawn* range and the feature is enabled, instead of it being removed/teleported, the respawn process will start, eventually creating another instance of the monster, thus overspawn.
Cherry-pick: #4294
PR Author: @marmichalski , this PR was made in order to implement the said change on master branch