Support to accept multiple simultaneous /tpa requests #3769
Labels
type: enhancement
Features and feature requests.
Milestone
Comments
|
+ |
mdcfe
added a commit
that referenced
this issue
Dec 4, 2021
This PR adds support for players to receive multiple teleport requests, which are queued and can be managed independently of one another. All commands should retain their current behavior but have some new additions; * `/tpaccept`: now allows you to specify a player or `*` to accept a specific player's or all players' teleport request(s) respectively. - Using a wildcard will only accept all tpahere requests, as players can't teleport to multiple places simultaneously. * `/tpdeny`: now allows you to specify a player or `*` to deny a specific player's or all players' teleport request(s) respectively. This PR also adds a new setting for the maximum amount of pending TPA requests a user can have at once. ```yml # The maximum amount of simultaneous tpa requests that can be pending for any given user. # Once at this threshold, any new tpa requests will bump the oldest tpa requests out of queue. # Defaults to 5. tpa-max-amount: 5 ``` Closes #3769 Closes #1550 Co-authored-by: Mariell Hoversholm <proximyst@proximy.st> Co-authored-by: MD <1917406+mdcfe@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
Currently the player to player teleport system only holds one pending value for a receiving player even if multiple teleport requests are made.
Feature description:
The system should hold more than one pending teleport.
The
/tpaccept <PlayerName>argument should be able to select for valid pending teleport requests from<PlayerName>Subsequent uses of
/tpacceptshould iterate through pending teleports until there are no more left.How the feature is useful:
This prevents confusion to Player A who currently gets no feedback that their teleport request to Player C was overwritten by Player B
The text was updated successfully, but these errors were encountered: