* only tabcomplete for commands the sender has permission for
* set permission defaults for spigot
* Make velocity autocomplete on arg length 0 and 1
* fix advancements perm in spigot plugin.yml and add settings perm
(whoops)
* don't show bedrock commands to java players
* modify spigot perm defaults
* censor help menu, abstract tab complete code
* Bedrock players don't get cmd argument suggestions
* update spigot plugin.yml
Errors that are a result of online mode and offline mode clashes are now clarified.
Users will now get a clearer message stating that the server is offline.
Resolves#2501
The Minecraft Java client doesn't appear to use any specific locale function in its translating. Just passing a string saves computational time in parsing a locale that will be the same result every time.
Should this be invalid behavior, we should instead cache the Locale class for a player so it doesn't have to be repeatedly calculated.
* 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.