core
/
testserver
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
testserver/Spigot-Server-Patches/0268-Properly-remove-entiti...

52 lines
2.4 KiB
Diff
Raw Normal View History

Updated Upstream (Bukkit/CraftBukkit/Spigot) Upstream has released updates that appears to apply and compile correctly. This update has been tested to ensure that World Conversion still occurs correctly. Bukkit Changes: 0812ce2c SPIGOT-4397: isChunkGenerated API CraftBukkit Changes: 4824655c SPIGOT-4398: Upgrade to ASM 6.2.1 for better Java 11 support eea43870 MC-134115: Fix issues converting tile entities 1a7f2d10 SPIGOT-4397: isChunkGenerated API 40aed54d SPIGOT-4396: Improve vehicle movement Spigot Changes: f6a273b1 Rebuild patches
2018-09-27 02:35:42 +00:00
From 9dbe03fbbbdd8e2474e9f3d4ffc0b9852cf4af53 Mon Sep 17 00:00:00 2001
Properly remove entities on dimension teleport To teleport an entity between dimensions, the server makes a copy and puts the copy in the new location, and marks the old one dead. If this method got called for the same world in the same tick, the entity would not have been removed from the UUID map, and the world readd would fail. This can be triggered even with a plugin if the entity is teleported twice in the same tick, from world A to B, then back from B to A. The re-add to A will fail to add the entity to the world. It will actually be there, but it will not be visible on the client until the server is restarted to re-try the add to world process again. This bug was unlikely to be seen by many due to the double teleport requirement, but plugins (such as my own) use this method to trigger a "reload" of the entity on the client.
2018-06-11 00:09:56 +00:00
From: Aikar <aikar@aikar.co>
Date: Sun, 10 Jun 2018 20:04:42 -0400
Subject: [PATCH] Properly remove entities on dimension teleport
To teleport an entity between dimensions, the server makes a copy
and puts the copy in the new location, and marks the old one dead.
If this method got called for the same world in the same tick,
the entity would not have been removed from the UUID map, and the
world readd would fail.
This can be triggered even with a plugin if the entity is teleported
twice in the same tick, from world A to B, then back from B to A.
The re-add to A will fail to add the entity to the world. It will
actually be there, but it will not be visible on the client until
the server is restarted to re-try the add to world process again.
This bug was unlikely to be seen by many due to the double teleport
requirement, but plugins (such as my own) use this method to
trigger a "reload" of the entity on the client.
diff --git a/src/main/java/net/minecraft/server/Entity.java b/src/main/java/net/minecraft/server/Entity.java
Updated Upstream (Bukkit/CraftBukkit/Spigot) Upstream has released updates that appears to apply and compile correctly. This update has been tested to ensure that World Conversion still occurs correctly. Bukkit Changes: 0812ce2c SPIGOT-4397: isChunkGenerated API CraftBukkit Changes: 4824655c SPIGOT-4398: Upgrade to ASM 6.2.1 for better Java 11 support eea43870 MC-134115: Fix issues converting tile entities 1a7f2d10 SPIGOT-4397: isChunkGenerated API 40aed54d SPIGOT-4396: Improve vehicle movement Spigot Changes: f6a273b1 Rebuild patches
2018-09-27 02:35:42 +00:00
index 8660387623..347aef07d5 100644
Properly remove entities on dimension teleport To teleport an entity between dimensions, the server makes a copy and puts the copy in the new location, and marks the old one dead. If this method got called for the same world in the same tick, the entity would not have been removed from the UUID map, and the world readd would fail. This can be triggered even with a plugin if the entity is teleported twice in the same tick, from world A to B, then back from B to A. The re-add to A will fail to add the entity to the world. It will actually be there, but it will not be visible on the client until the server is restarted to re-try the add to world process again. This bug was unlikely to be seen by many due to the double teleport requirement, but plugins (such as my own) use this method to trigger a "reload" of the entity on the client.
2018-06-11 00:09:56 +00:00
--- a/src/main/java/net/minecraft/server/Entity.java
+++ b/src/main/java/net/minecraft/server/Entity.java
Updated Upstream (Bukkit/CraftBukkit/Spigot) Upstream has released updates that appears to apply and compile correctly. This update has been tested to ensure that World Conversion still occurs correctly. Bukkit Changes: 0812ce2c SPIGOT-4397: isChunkGenerated API CraftBukkit Changes: 4824655c SPIGOT-4398: Upgrade to ASM 6.2.1 for better Java 11 support eea43870 MC-134115: Fix issues converting tile entities 1a7f2d10 SPIGOT-4397: isChunkGenerated API 40aed54d SPIGOT-4396: Improve vehicle movement Spigot Changes: f6a273b1 Rebuild patches
2018-09-27 02:35:42 +00:00
@@ -2594,7 +2594,7 @@ public abstract class Entity implements INamableTileEntity, ICommandListener, Ke
Properly remove entities on dimension teleport To teleport an entity between dimensions, the server makes a copy and puts the copy in the new location, and marks the old one dead. If this method got called for the same world in the same tick, the entity would not have been removed from the UUID map, and the world readd would fail. This can be triggered even with a plugin if the entity is teleported twice in the same tick, from world A to B, then back from B to A. The re-add to A will fail to add the entity to the world. It will actually be there, but it will not be visible on the client until the server is restarted to re-try the add to world process again. This bug was unlikely to be seen by many due to the double teleport requirement, but plugins (such as my own) use this method to trigger a "reload" of the entity on the client.
2018-06-11 00:09:56 +00:00
}
// CraftBukkit end */
- this.world.kill(this);
+ this.world.removeEntity(this); // Paper - Fully remove entity, can't have dupes in the UUID map
this.dead = false;
this.world.methodProfiler.a("reposition");
/* CraftBukkit start - Handled in calculateTarget
diff --git a/src/main/java/net/minecraft/server/WorldServer.java b/src/main/java/net/minecraft/server/WorldServer.java
Updated Upstream (Bukkit/CraftBukkit/Spigot) Upstream has released updates that appears to apply and compile correctly. This update has been tested to ensure that World Conversion still occurs correctly. Bukkit Changes: 0812ce2c SPIGOT-4397: isChunkGenerated API CraftBukkit Changes: 4824655c SPIGOT-4398: Upgrade to ASM 6.2.1 for better Java 11 support eea43870 MC-134115: Fix issues converting tile entities 1a7f2d10 SPIGOT-4397: isChunkGenerated API 40aed54d SPIGOT-4396: Improve vehicle movement Spigot Changes: f6a273b1 Rebuild patches
2018-09-27 02:35:42 +00:00
index ee06457653..b939c31b23 100644
Properly remove entities on dimension teleport To teleport an entity between dimensions, the server makes a copy and puts the copy in the new location, and marks the old one dead. If this method got called for the same world in the same tick, the entity would not have been removed from the UUID map, and the world readd would fail. This can be triggered even with a plugin if the entity is teleported twice in the same tick, from world A to B, then back from B to A. The re-add to A will fail to add the entity to the world. It will actually be there, but it will not be visible on the client until the server is restarted to re-try the add to world process again. This bug was unlikely to be seen by many due to the double teleport requirement, but plugins (such as my own) use this method to trigger a "reload" of the entity on the client.
2018-06-11 00:09:56 +00:00
--- a/src/main/java/net/minecraft/server/WorldServer.java
+++ b/src/main/java/net/minecraft/server/WorldServer.java
Paper 1.13.1 Update Updated Upstream (Bukkit/CraftBukkit/Spigot) Bukkit Changes: 2dcc44dc SPIGOT-4307: Fix hacky API for banners on shields e0fc6572 SPIGOT-4309: Add "forced" display of particles efeeab2f Add index to README.md for easier navigation f502bc6f Update to Minecraft 1.13.1 CraftBukkit Changes: d0bb0a1d Fix some tests randomly failing 997d378d Fix client stall in specific teleportation scenarios b3dc2366 SPIGOT-4307: Fix hacky API for banners on shields 2a271162 SPIGOT-4301: Fix more invalid enchants 5d0d83bb SPIGOT-4309: Add "forced" display of particles a6772578 Add additional tests for CraftBlockData ce1af0c3 Update to Minecraft 1.13.1 Spigot Changes: 2440e189 Rebuild patches 4ecffced Update to Minecraft 1.13.1
2018-08-26 18:11:49 +00:00
@@ -1020,6 +1020,7 @@ public class WorldServer extends World implements IAsyncTaskHandler {
Properly remove entities on dimension teleport To teleport an entity between dimensions, the server makes a copy and puts the copy in the new location, and marks the old one dead. If this method got called for the same world in the same tick, the entity would not have been removed from the UUID map, and the world readd would fail. This can be triggered even with a plugin if the entity is teleported twice in the same tick, from world A to B, then back from B to A. The re-add to A will fail to add the entity to the world. It will actually be there, but it will not be visible on the client until the server is restarted to re-try the add to world process again. This bug was unlikely to be seen by many due to the double teleport requirement, but plugins (such as my own) use this method to trigger a "reload" of the entity on the client.
2018-06-11 00:09:56 +00:00
}
protected void c(Entity entity) {
Guard the Entity.SHARED_RANDOM from seed changes I don't clearly see any, but as a protection for future changes.
2018-07-21 13:03:10 +00:00
+ if (!this.entitiesByUUID.containsKey(entity.getUniqueID()) && !entity.valid) return; // Paper - Already removed, dont fire twice - this looks like it can happen even without our changes
Properly remove entities on dimension teleport To teleport an entity between dimensions, the server makes a copy and puts the copy in the new location, and marks the old one dead. If this method got called for the same world in the same tick, the entity would not have been removed from the UUID map, and the world readd would fail. This can be triggered even with a plugin if the entity is teleported twice in the same tick, from world A to B, then back from B to A. The re-add to A will fail to add the entity to the world. It will actually be there, but it will not be visible on the client until the server is restarted to re-try the add to world process again. This bug was unlikely to be seen by many due to the double teleport requirement, but plugins (such as my own) use this method to trigger a "reload" of the entity on the client.
2018-06-11 00:09:56 +00:00
super.c(entity);
this.entitiesById.d(entity.getId());
this.entitiesByUUID.remove(entity.getUniqueID());
--
Updated Upstream (Bukkit/CraftBukkit/Spigot) Upstream has released updates that appears to apply and compile correctly. This update has been tested to ensure that World Conversion still occurs correctly. Bukkit Changes: 0812ce2c SPIGOT-4397: isChunkGenerated API CraftBukkit Changes: 4824655c SPIGOT-4398: Upgrade to ASM 6.2.1 for better Java 11 support eea43870 MC-134115: Fix issues converting tile entities 1a7f2d10 SPIGOT-4397: isChunkGenerated API 40aed54d SPIGOT-4396: Improve vehicle movement Spigot Changes: f6a273b1 Rebuild patches
2018-09-27 02:35:42 +00:00
2.19.0
Properly remove entities on dimension teleport To teleport an entity between dimensions, the server makes a copy and puts the copy in the new location, and marks the old one dead. If this method got called for the same world in the same tick, the entity would not have been removed from the UUID map, and the world readd would fail. This can be triggered even with a plugin if the entity is teleported twice in the same tick, from world A to B, then back from B to A. The re-add to A will fail to add the entity to the world. It will actually be there, but it will not be visible on the client until the server is restarted to re-try the add to world process again. This bug was unlikely to be seen by many due to the double teleport requirement, but plugins (such as my own) use this method to trigger a "reload" of the entity on the client.
2018-06-11 00:09:56 +00:00