You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: