summaryrefslogtreecommitdiffstats
path: root/nms-patches/PlayerList.patch
Commit message (Collapse)AuthorAgeLines
* Update to Minecraft 1.13md_52018-07-22-26/+17
|
* Update to Minecraft 1.13-pre7md_52018-07-15-139/+119
|
* SPIGOT-3879: Make end->overworld spawning more consistent with vanillamd_52018-03-30-30/+33
|
* SPIGOT-3864: Protect against suffocation on world changemd_52018-03-22-1/+1
|
* SPIGOT-3845: Fix spawnRadius on respawnmd_52018-03-08-1/+1
| | | | Thanks senmori for the investigation in PR #431
* SPIGOT-3775: ghost player list entry if kicked on joinmd_52018-01-23-44/+48
|
* Send complete metadata update to joining playersmd_52018-01-08-28/+30
|
* Update to Minecraft 1.12.1md_52017-08-03-8/+6
|
* Fix memory leak in PlayerListmd_52017-07-17-35/+130
|
* SPIGOT-3377: Fix subspace bubble advancementmd_52017-06-26-1/+1
|
* Update to Minecraft 1.12-pre6md_52017-05-30-2/+2
|
* Update to Minecraft 1.12-pre5md_52017-05-19-1/+1
|
* Misc advancement / recipe reload fixes including SPIGOT-3240md_52017-05-16-12/+24
|
* Update to Minecraft 1.12-pre2md_52017-05-14-58/+64
|
* SPIGOT-3207: Fix hiding players in a BukkitRunnable after joiningPokechu222017-04-28-20/+21
| | | | | | This happened because "joining" wasn't cleared until the player was ticked. Runnables (presumably) ran _after_ the player list packet was sent, but before the player was ticked; thus, the player list packet was sent, but not cleared. The fix is to replace joining with hasSentListPacket, which is set immediately before sending any player list packets (thus, if hidePlayer is called after, it sees that the list packet has been sent and sends a new one to reset it). With this fix, the player is added to the list and then removed shortly afterwards. The reason why running /hideall in the example wouldn't fix the invisibility is because the server already thinks the player's been removed from the list (as they're hidden), and thus doesn't want to send another hide packet. This is correct behavior assuming that they get hidden correctly the first time, which they now do.
* Remove players from vehicle when changing world via NMS methods.md_52017-04-21-16/+17
|
* Re-enable the vanilla debug MethodProfiler and /debug commandPokechu222017-01-18-8/+8
| | | | | | | | | | This is highly useful for profiling vanilla code, and in some cases plugin code. It is somewhat expensive, though, which is why it was initially disabled. I chose to use a system property instead of a configuration setting because 1) the MethodProfiler is exclusive to CraftBukkit and not part of the general API (the timings system is the general API equivalent), and 2) using a static final boolean property _may_ allow the JITter to optimize out the methods when disabled (though I'm not sure of it). There are several changes to fix cases where the profiler code was broken slightly by other craftbukkit changes. All of cases have been fixed, except for the block entity ticking one, due to the cost of the getSimpleName call. For that, a ticking entry is used instead, so that time spent actually ticking the block entities can be compared with time processing the list. This (effectively) reverts 7dde6cc5663e1f6b84f549c54a47bc623b49fdf1.
* Update to Minecraft 1.11.1md_52016-12-21-42/+42
|
* Fix possible leaks in vanish APImd_52016-11-28-34/+54
|
* Update to Minecraft 1.11md_52016-11-17-28/+31
|
* SPIGOT-1903, MC-98153: Portal Location Sync Issuesmd_52016-10-23-1/+1
|
* SPIGOT-2622: Ensure all players are safely disconnected on shutdownmd_52016-08-23-8/+12
|
* SPIGOT-2501: Remove period from default quit messagemd_52016-07-07-1/+1
|
* SPIGOT-2461: Call player tick specificallymd_52016-06-28-1/+1
|
* SPIGOT-924: Compute attributes one last time after quittingmd_52016-06-25-23/+24
|
* Update to Minecraft 1.10md_52016-06-09-27/+27
|
* SPIGOT-2311: Cancelling PlayerPortalEvent causes invulnerability until relogmd_52016-05-25-14/+15
|
* Minecraft 1.9.4md_52016-05-10-31/+31
|
* SPIGOT-2115: Fix entities being added to the world multiple times when ↵Thinkofname2016-04-02-14/+16
| | | | teleported
* Fix player dimension change invulnerability never getting unset when certain ↵Zach Brown2016-03-24-13/+14
| | | | dimensions are disabled
* Remove redundant syncInventory on world changemd_52016-03-06-1/+2
|
* SPIGOT-1573: Fix command blocks after respawningmd_52016-03-06-24/+21
|
* Update to Minecraft 1.9md_52016-03-01-105/+112
|
* SPIGOT-1308: Fix typo in PlayerList#sendAllThinkofdeath2016-01-22-1/+1
|
* SPIGOT-1058: Fix lost player list capping to 60.md_52015-07-18-2/+4
| | | | Went missing in the 1.8 update.
* SPIGOT-954: Don't send block animations or gamemode updates to players can't ↵Thinkofdeath2015-06-07-21/+31
| | | | see the player
* [SPIGOT-946] Begin making use of access transforms to simplify patching.md_52015-06-06-17/+5
|
* Cut fluff from patch headers.md_52015-05-25-2/+2
|
* Update to 1.8.4Thinkofdeath2015-05-17-12/+12
|
* Fire PlayerTeleport event on portal travelThinkofdeath2015-03-21-33/+38
|
* Only double switch if the dimension is the sameThinkofdeath2015-03-08-15/+17
|
* Readd the double dimension switchThinkofdeath2015-03-08-14/+15
|
* Update to Minecraft 1.8.3Thinkofdeath2015-03-04-124/+121
|
* Remove the double dimension switch as the issue seems fixed, if it breaks ↵Thinkofdeath2015-02-18-15/+14
| | | | something blame SupaHam
* Handle new players correctlyThinkofdeath2015-02-04-3/+3
|
* Improve vanilla's rename detection by using bukkit's lastKnownName nbt tagThinkofdeath2015-02-04-35/+48
|
* Re-enable the vanilla feature of changing the join message if a player has ↵Thinkofdeath2015-02-03-34/+50
| | | | | | | changed name since their last join This uses the UserCache (like vanilla) and therefore is limited to whether they are still in the cache by the next join
* Rework the vanilla link fix so that hover/click events aren't lostThinkofdeath2014-12-13-15/+12
|
* SPIGOT-199: Default to white instead of black for chat messagesThinkofdeath2014-12-13-3/+3
|
* Use CraftChatMessage.fromComponent so that colors remain in sent messagesThinkofdeath2014-12-12-3/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 01:01:17 +0000