Started by an SCM change448c3dd1f281a589824f56e74f9efb55ba78c0aacb8c3dd1f281a589824f56e74f9efb55ba78c0aacbrefs/remotes/origin/master8c3dd1f281a589824f56e74f9efb55ba78c0aacb8c3dd1f281a589824f56e74f9efb55ba78c0aacbrefs/remotes/origin/master8c3dd1f281a589824f56e74f9efb55ba78c0aacb8c3dd1f281a589824f56e74f9efb55ba78c0aacbrefs/remotes/origin/masterhttps://hub.spigotmc.org/stash/scm/spigot/spigot.githttps://hub.spigotmc.org/jenkins/view/RSS/job/Bukkit-RSS/44/artifacthttps://hub.spigotmc.org/jenkins/view/RSS/job/Bukkit-RSS/changeshttps://hub.spigotmc.org/jenkins/view/RSS/job/Bukkit-RSS/44/https://hub.spigotmc.org/jenkins/view/RSS/job/Bukkit-RSS/44/testReportfalse#44737717Bukkit-RSS #4444falsefalse44-1SUCCESS1424568126439https://hub.spigotmc.org/jenkins/view/RSS/job/Bukkit-RSS/44/CraftBukkit-Patches/0161-Use-FastMatches-for-ItemStack-Dirty-Check.patch8c3dd1f281a589824f56e74f9efb55ba78c0aacb1424528878000https://hub.spigotmc.org/jenkins/user/md_5md_5git@md-5.netUse FastMatches for ItemStack Dirty Check The check to find dirty itemstacks and send update packets each tick can be very intensive as it checks the entire itemstack, including the entire NBT map. To save on this, 19/20 times we will simply compare the basic count/data/type. If for some strange reason the NBT of an item already existing in an inventory is changes, it will take up to 1 second to show, with an average time of half a second. This odd 0.5 second delay is far preferable to lag every tick, and shouldn't be noticed by anyone. 2015-02-22T01:27:58+11008c3dd1f281a589824f56e74f9efb55ba78c0aacbUse FastMatches for ItemStack Dirty CheckaddCraftBukkit-Patches/0161-Use-FastMatches-for-ItemStack-Dirty-Check.patchgithttps://hub.spigotmc.org/jenkins/user/md_5md_5md_5