Skip to content

Per-Platform Configuration Options #2291

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

Open
Camotoy opened this issue Jun 17, 2021 · 0 comments · May be fixed by #5010
Open

Per-Platform Configuration Options #2291

Camotoy opened this issue Jun 17, 2021 · 0 comments · May be fixed by #5010
Labels
Feature Request A feature request.

Comments

@Camotoy
Copy link
Member

Camotoy commented Jun 17, 2021

What feature do you want to see added?

As Geyser becomes more feature-intensive and tied to plugin implementations, there are a couple of options that are less relevant or should be toggled, depending on the platform.

The main idea is that, on plugin platforms with the upcoming injection options, we hide away the remote address and port, as those will be obsolete (more details upcoming on that - the important part is remote address and port do nothing and would only serve as a legacy option or confuse users). The BungeeCord platform presents another hurdle/opportunity - the way it's designed, we need to essentially reimplement their listener config to create a "new" listener, or add an option to select which listener to mirror.

Another option is "forward-hostname", which should be true on plugin platforms but false on standalone (we don't want to trigger incorrect behavior by providing an interesting IP as the origin address).

Are there any alternatives?

  • Cry
  • Stuff everything into the same config file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request A feature request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant