-
-
Notifications
You must be signed in to change notification settings - Fork 691
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
clone-remote-port option #798
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would also add a check for this on Sponge's end too, just for consistency.
Updated config.yml to include a better description of the clone-remote-port option
An incorrect port was being edited before (remote instead of bedrock)
Done |
Please update this PR to support 1.16. |
Looks like you have a merge conflict that needs to be resolved. Once that is taken care of, I can merge this 🙂 |
Superseded by #944. |
Reopening since #944 does not include this commit history. Closed before realizing this was the case; sorry for the confusion! |
Due to the lack of response from OP, this has been superseded by #1061. Commit history from this PR has been kept however. Regardless, thanks for the contribution! |
Added a clone-remote-port option which makes the bedrock's port the same as the java's port if geyser is running as a plugin