forked from GeyserMC/Floodgate
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sync relevant changes Jun 3 2024 #14
Draft
robinbraemer
wants to merge
118
commits into
minekube:connect
Choose a base branch
from
GeyserMC:master
base: connect
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix typos * Fix another typo * Fix error log message (#275) Co-authored-by: Tim203 <[email protected]>
# Conflicts: # build-logic/src/main/kotlin/Versions.kt
Since everyone generally updates their proxy this doesn't provide backwards compatibility with BungeeCord versions that don't support 1.19 clients.
Metrics showed that more than 33% of the BungeeCord platform users still use a 1.18.x version
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.
* Update Geyser version * Update Versions.kt
…ncy so the project builds (#498)
* Update build process * Ensure BUILD_JSON env is init * Fallback to GH run number * Use tmp file for metadata.json Signed-off-by: Joshua Castle <[email protected]> --------- Signed-off-by: Joshua Castle <[email protected]>
* - 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 <[email protected]>
* Temporary fix for #510, bump cloud to rc candidate * apparently it is supposed to be nullable. okay then.
* fix: add default skin to gameprofiles * fix: add signatures by default to prevent issues * cleanup * no longer apply empty textures * revert formatting change * fix(spigot): linked player textures * fix(velocity): linked player textures * fix(bungeecord): apply linked textures * Made the MojangUtils class instance based, removed some unneeded code * Don't block Velocity event threads, made the Bungee variant work * Add some comments --------- Co-authored-by: bridge <[email protected]> Co-authored-by: Tim203 <[email protected]>
* Switch to centralized GitHub actions * Build number is in env for PR
See #536 for more information
* update bungee injector * add backwards compatibility
* 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 <[email protected]>
* 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 <[email protected]>
* Update README.md * Correct CI link
* feat: added #closeForm method to FloodgateApi * feat: implementation of the closeForm method * Update Floodgate API version --------- Co-authored-by: Roch Blonndiaux <[email protected]> Co-authored-by: onebeastchris <[email protected]>
* Update BungeeInjector.java * Update bungee version * Add a message when running an outdated Bungee version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.