/TP & /TPHere
Send and accept safe teleport requests with click-to-accept prompts.
Accept Command: /tp accept <player>
Default Request Timeout: 30 seconds
Default Cooldown: 6 seconds between requests
What It Does
Teleport Requests provides consent-based teleporting so one player cannot force instant movement on another.
Targets receive a clickable accept button and the teleport only happens after approval.
Command Flow
| Command | Result |
|---|---|
/tp playername |
Requests teleporting yourself to that player |
/tphere playername |
Requests that player teleport to you |
/tp accept playername |
Approves the pending request from that requester |
Request Rules
- Target must be online.
- You cannot request yourself.
- A target can only hold one pending teleport request at a time.
- Requests expire after timeout if not accepted.
- Request sending has a short anti-spam cooldown.
Acceptance Behavior
| Request Type | Who Teleports On Accept |
|---|---|
| /tp request | Requester teleports to target |
| /tphere request | Target teleports to requester |
Notifications And Feedback
Both players get confirmation messages on send, accept, or expiry events.
Acceptable requests include a clickable accept button in chat for faster approvals.
Frequently Asked Questions
Q: Why did my request fail immediately?
A: Most often target offline, self-targeting, active cooldown, or target already has a pending request.
Q: Why does /tp accept fail sometimes?
A: The request may have expired, the requester went offline, or the name did not match the pending request.
Q: Is there a deny command?
A: This flow is built around acceptance and timeout; expired requests close automatically.