Spigot 1.9

You can fix this by using reflection to re-set the rider's reference to the vehicle that gets lost during the cancelled event. For 1.13 this field is Entity#ax, to 1.12 it's Entity#au. For older versions you can look that up yourself.

public class TestPlugin extends JavaPlugin implements Listener {
    @Override
    public void onEnable() {
        getServer().getPluginManager().registerEvents(this, this);
    }

    @EventHandler
    public void on(VehicleExitEvent event) {
        event.setCancelled(true);
        setVehicleBack(event.getExited(), event.getVehicle());
    }

    private void setVehicleBack(Entity rider, Entity vehicle) {
        try {
            Field ax = net.minecraft.server.v1_13_R1.Entity.class.getDeclaredField("ax");
            ax.setAccessible(true);
            ax.set(((CraftEntity) rider).getHandle(), ((CraftEntity) vehicle).getHandle());
        } catch (NoSuchFieldException | IllegalAccessException e) {
            e.printStackTrace();
        }
    }
}

See these for more information:

https://hub.spigotmc.org/jira/browse/SPIGOT-4113

https://hub.spigotmc.org/jira/browse/SPIGOT-4163

Nope. The client no longer waits for a response from the server before dismounting. It's basically client-driven now.

I thought it was a server side issue. Not a client one.

This issue is due to client changes, there is nothing that can be done server side and I would not expect a fix.

That's my understanding of the problem, anyway.

Not being able to cancel the VehicleExitEvent properly impacts plugins like WorldGuard for example. I really don't mean to sound impatient, but this issue was created in 1.9. And it's still here in 1.10.2.

Bump