PlayerTeleportEvent does not fire for most teleports
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the PlayerTeleportEvent behavior for ender pearls, nether portals, and end portals using the listener shown in the issue, then trace where those teleport causes dispatch the event. Done means PlayerTeleportEvent fires for all listed teleportations while preserving the existing behavior for consumable effects, dismounts, and exiting beds.
Written by the indexing model from the issue text.
Description
Expected behavior
PlayerTeleportEvent to fire for all teleportations
Observed/Actual behavior
PlayerTeleportEvent only fires for causes:
CONSUMABLE_EFFECT: tested eating chorus fruitDISMOUNT: tested getting off a camelEXIT_BED: tested getting out of bed
It does not fire for causes:
ENDER_PEARL: tested by throwing an ender pearlNETHER_PORTAL: tested by walking through nether portalEND_PORTAL: tested by walking through an end portal
Steps/models to reproduce
final class PortalListener implements Listener {
@EventHandler(priority = EventPriority.MONITOR)
public void onTeleport(PlayerTeleportEvent event) {
logger.debug("onTeleport");
}
}
And
public final class MyPlugin extends JavaPlugin {
@Override
public void onEnable() {
getServer().getPluginManager().registerEvents(
new PortalListener()
);
}
}
Plugin and Datapack List
Just MyPlugin for testing
Folia version
This server is running Folia version 26.1.2-8-ver/26.1.x@62dc0f2 (2026-05-06T13:45:28Z) (Implementing API version 26.1.2.build.8-stable)
You are running the latest version
Other
No response
- Dominant language
- Shell
- Stars
- 4.7k
- Forks
- 651
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PaperMC/Folia
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
status: needs triage type: bug
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
status: needs triage type: performance
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
status: needs triage type: bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
status: needs triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
cicd
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nolte/kamerplanter-appliance#53 ·
Maintainers usually reply within 1 day
-
area:scripts priority:P2 status:backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
KD5UJC-XYZ/scarab#1170 ·
Maintainers usually reply within 1 day
-
SETUP: nothing verifies the decider code was ever set, so a skipped step leaves approvals token-onlyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mattabate/life-distributable#229 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
bug fixed good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
sdetweil/MagicMirror-backup-restore#20 · 1 comment ·