testserver

4,095 Commits 1 Branch 0 Tags 60 MiB

Author	SHA1	Message	Date
Zach Brown	70ce6ce831	Move version command update checking to the implementation This makes it easier for downstream projects (forks) to replace the version fetching system with their own. It is as simple as implementing an interface and overriding the default implementation of org.bukkit.UnsafeValues#getVersionFetcher() It also makes it easier for us to organize things like the version history feature. Lastly I have updated the paper implementation to check against the site API rather than against jenkins.	2019-05-27 04:13:41 -05:00
Zach Brown	27c7749f42	More compile fixes - Re-removes Bukkit#getServerName - This was (hopefully?) only added back for Timings v2. It should be kept in that scope. - Intend to let PlayerViewDistance API slip. Given the scope of the changes in this area it seems best to let this slip past initial release. It can be re-added when there is additional time to focus on it and the changed systems it relies on. If it is fixed prior to release this is implemented as a single shim patch that can be dropped.	2019-05-06 03:20:16 -04:00
Spottedleaf	36873bf2d6	More 1.14 updates (#1995 )	2019-04-26 23:05:36 -04:00

Author

SHA1

Message

Date

Zach Brown

70ce6ce831

Move version command update checking to the implementation

This makes it easier for downstream projects (forks) to replace the
version fetching system with their own. It is as simple as implementing
an interface and overriding the default implementation of
org.bukkit.UnsafeValues#getVersionFetcher()

It also makes it easier for us to organize things like the version
history feature.

Lastly I have updated the paper implementation to check against the site
API rather than against jenkins.

2019-05-27 04:13:41 -05:00

Zach Brown

27c7749f42

More compile fixes

- Re-removes Bukkit#getServerName - This was (hopefully?) only added back
  for Timings v2. It should be kept in that scope.

- Intend to let PlayerViewDistance API slip. Given the scope of the
  changes in this area it seems best to let this slip past initial
  release. It can be re-added when there is additional time to focus on it
  and the changed systems it relies on. If it is fixed prior to release
  this is implemented as a single shim patch that can be dropped.

2019-05-06 03:20:16 -04:00

Spottedleaf

36873bf2d6

More 1.14 updates (#1995 )

2019-04-26 23:05:36 -04:00

Renamed from Spigot-Server-Patches/0113-Don-t-save-empty-scoreboard-teams-to-scoreboard.dat.patch (Browse further)

3 Commits