* Fixed some Scoreboard bugs and ScoreboardUpdater is now global
* Begin implementing below name support and better name display
* Use final for classes
* Revert "Begin implementing below name support and better name display"
This reverts commit 01babd636a.
* Don't remove objective if we're showing it
* Prevent concurrency exceptions when switching servers
* Properly fix the concurrency issue
* Fix inconsistencies in update cycle
* Few minor changes
* Port over this fix
* Fixed a problem that was introduced yesterday
* Cleanup
* Scores don't have to be removed before removing the objective itself
* Moved away from the general thread pool and some more changes
* Small changes
* Converted switch statements
Co-authored-by: Camotoy <20743703+Camotoy@users.noreply.github.com>
`Registering bedrock skin for PLAYERNAME` is now just confusing as it implies something to do with Floodgate's skin system when it's just for Bedrock <-> Bedrock players.
* Update config.yml
Added commented clarifications on:
1. "remote: address: auto"
2. "remote: auth-type: online"
May need formatting checks to conform with correct annotation
* Update config.yml
See #2540 - not confirmed to be resolved as we weren't able to replicate a cause for this issue but this solved the issue from artifically invoking it.
By introducing fixed maps, we are able to reduce the overhead of needing to store arbitrary numbers; fixed maps start at one number and must be sequential. This commit also reduces some overhead of lecterns in block updating as we are able to utilize our own maps to reduce object boxing and removing the function of Map#compute of trying to re-insert a value.
As Bedrock does not have world border support, this PR translates what the Java server sends us for a world border into particles and fog, while also preventing the Bedrock client from moving outside of the world border.
Co-authored-by: Luke <32024335+lukeeey@users.noreply.github.com>
Co-authored-by: ofunny <play@ofunny.world>
- Most importantly, redesign lodestone caches to be per-player.
- Redesign lodestone caches with the expectation that a client will never re-request the same value.
- Re-use lodestone IDs in a WeakHashMap to be re-used but successfully garbage-collected.
