5 commits

Author	SHA1	Message	Date
Jason Penilla	062733b903	Updated Upstream (CraftBukkit/Spigot) ... Doesn't compile yet. CraftBukkit Changes: 90d6905b Repackage NMS 69cf961d Repackage patches Spigot Changes: 79d53c28 Repackage NMS	2021-03-16 00:19:45 -07:00
Riley Park	727e71ad0f	bug #5362 - correctly pass "render type" when registering a new scoreboard objective ... fixes #5362	2021-03-14 12:04:49 -07:00
Jason Penilla	9cf511130f	Replace usages of LegacyComponentSerializer.legacySection() in Paper-Server with PaperAdventure.LEGACY_SECTION_UXRC (#5233)	2021-02-23 05:45:09 -08:00
Riley Park	2e419805ad	We're going on an Adventure! (#4842) ... Co-authored-by: Jake Potrebic <jake.m.potrebic@gmail.com> Co-authored-by: zml <zml@stellardrift.ca> Co-authored-by: Mariell Hoversholm <proximyst@proximyst.com>	2021-02-21 11:45:33 -08:00
Andrew Steinborn	ac051139a8	Lazily track plugin scoreboards by default ... On servers with plugins that constantly churn through scoreboards, there is a risk of degraded GC performance due to the number of scoreboards held on by weak references. Most plugins don't even need the (vanilla) functionality that requires all plugin scoreboards to be tracked by the server. Instead, only track scoreboards when an objective is added with a non-dummy criteria. This is a breaking change, however the change is a much more sensible default. In case this breaks your workflow you can always force all scoreboards to be tracked with settings.track-plugin-scoreboards in paper.yml.	2020-10-03 04:47:01 -04:00