* Moved check of channel open of #547. In previous point was always true and it did not solve problem.
* Moved check of channel open of #547. In previous point was always true and it did not solve problem.
* Make the comment more compact
---------
Co-authored-by: Tim203 <mctim203@gmail.com>
* Check if channel is open before injecting
Some forks like FlameCord have integrated anti-bot features to block connections early.
By default, Floodgate runs anyways, which not only makes bot attacks affect the server when Floodgate is instaled, but also generate an exception.
This fixes the issue.
* Add note about why it's added
---------
Co-authored-by: Tim203 <mctim203@gmail.com>
* - Update to cloud 2.0
- bump floodgate version to 2.2.3
- fix publishing setup - don't publish shadow jars, ensure api/core artifacts aren't shaded jars
* - update bstats
- fix alias -> description
* tiny cleanup, fix whitelisting bedrock players when the linked java account is online (and shares the same name)
* Update build process
* Ensure BUILD_JSON env is init
* Fallback to GH run number
* update guice to 6.0.0 to be compatible with java 21
* update languages module
* Support 1.20.5 spigot, update languages module, update Bungee dependency so the project builds
* remove codemc repo, update cloud-paper to snapshot build for 1.20.5 support
---------
Co-authored-by: Kas-tle <26531652+Kas-tle@users.noreply.github.com>
* SkinApplier now only applies a skin if a player doesn't already have one
* add `hasSkin` method to SkinApplier and check for exising skins before overwriting
* remove the use of Streams and Optionals
* correct delay in SpigotSkinApplier to use ticks instead of milliseconds
* Minor changes
Co-authored-by: Tim203 <mctim203@gmail.com>
The config updater didn't re-add the quotes that strings with special characters (or no characters) should have, which resulted in the usernamePrefix becoming invalid or null. While this has been fixed for people that use the config updater with the latest version, people that already updated can't update again, and would have to edit the config manually.
This check has caused more harm than good (with needing to use an external NTP source and some providers not allowing Cloudflare's NTP server), and is also a technical vulnerability in BungeeGuard. In order to exploit this, you would need to capture traffic between the Geyser server and the Floodgate instance.
