Stronghold timelimit and anti-camp mechanics #303
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
|
Woops this should be a draft PR! I'll edit the title to reflect |
…if over limit, extract some logic outside of transaction scope
MikeJeffers
changed the title
…t expose, do player.save in transaction
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.
Closes: #279
Requires: OpenPerpetuum/OPDB#277
Introduces a timelimit for any configured stronghold to automatically despawn a player back to their homebase if they remain on the zone.
Update: Figured out how to augment the player entities DynamicProperties. Adding a timestamp of the expiration time will persist the despawn timer between logins to deal with disconnects and timer resetting.