kickPlayer does not take effect immediately

[faosucvwabscvbw]

Expected behavior

java
@OverRide
public void onDisable()
{
for (World world : Bukkit.getWorlds())
{
for (Player player : world.getPlayers())
{
player.kickPlayer("Server closed");
}
Bukkit.unloadWorld(world, false); //return true
}
}

Observed/Actual behavior

java
@OverRide
public void onDisable()
{
for (World world : Bukkit.getWorlds())
{
for (Player player : world.getPlayers())
{
player.kickPlayer("Server closed");
}
Bukkit.unloadWorld(world, false); //return false
}
}

Steps/models to reproduce

void

Plugin and Datapack List

void

Paper version

This server is running Paper version 26.2-84-main@26e81c4 (2026-07-26T18:11:33Z) (Implementing API version 26.2.build.84-stable)
You are 3 version(s) behind

Other

After kickPlayer is called, the player is not immediately removed from the player list within the same tick. As a result, the world cannot be directly unloaded within that same tick in the plugin. The player list update occurs at the end of the server tick, which is after Bukkit.unloadWorld is executed

[NonSwag]

A potential solution to this would be to schedule the unload one tick later
Not sure if updating the entire kick logic is feasible just to remove the player immediately

[faosucvwabscvbw]

A potential solution to this would be to schedule the unload one tick later Not sure if updating the entire kick logic is feasible just to remove the player immediately

Before the plugin's onDisable method is invoked, it is no longer permitted for the plugin to schedule any delayed tasks, because creating a delayed task while the server is shutting down serves no meaningful purpose.
The old function implementation did not suffer from this issue; it would immediately update the player list within the NMS (Net Minecraft Server) layer by executing:
this.getHandle().transferCookieConnection.kickPlayer(CraftChatMessage.fromStringOrEmpty(message, true), org.bukkit.event.player.PlayerKickEvent.Cause.PLUGIN); // Paper - kick event cause