Skip to content
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

feat: Add BungeeGuard Compatible mode #97

Open
kubo6472 opened this issue Oct 4, 2022 · 2 comments · May be fixed by #338
Open

feat: Add BungeeGuard Compatible mode #97

kubo6472 opened this issue Oct 4, 2022 · 2 comments · May be fixed by #338
Labels
enhancement New feature or request (not a bug) priority/medium Medium priority task

Comments

@kubo6472
Copy link

kubo6472 commented Oct 4, 2022

Like Velocity 3.x, add mode where it will still support 1.7-1.19.x but use the token for something like BungeeGuard.

@robinbraemer robinbraemer added the enhancement New feature or request (not a bug) label Oct 5, 2022
@robinbraemer
Copy link
Member

Are you using BungeeGuard?

@kubo6472
Copy link
Author

Yes, I was using it with velocity. Wanted to do some testing with gate. As velocity has almost, if not larger memory consumption than a full minecraft server. Truth be told, I'm "hosting" an auth server directly from proxy, using LimboAPI velocity plugin, but still, I tried it without all of that and it still has enormous memory footprint. With versions below 1.13.x I will have to use something like bungeeguard instead of the modern velocity style forwarding.

@robinbraemer robinbraemer added the priority/medium Medium priority task label Mar 17, 2023
@kubo6472 kubo6472 changed the title [FR] Add BungeeGuard Compatible mode feat: Add BungeeGuard Compatible mode May 18, 2023
@Git-Fal7 Git-Fal7 linked a pull request May 8, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request (not a bug) priority/medium Medium priority task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants