#Morning all,
1 messages · Page 1 of 1 (latest)
Log snippet
00:32:54 [WARNING] Error loading plugin Geyser-Spigot
mcb-bungee | java.lang.NoClassDefFoundError: org/bukkit/plugin/java/JavaPlugin
mcb-bungee | at java.base/java.lang.ClassLoader.defineClass1(Native Method)
mcb-bungee | at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017)
mcb-bungee | at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
mcb-bungee | at net.md_5.bungee.api.plugin.PluginClassloader.findClass(PluginClassloader.java:152)
mcb-bungee | at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:592)
mcb-bungee | at net.md_5.bungee.api.plugin.PluginClassloader.loadClass0(PluginClassloader.java:66)
mcb-bungee | at net.md_5.bungee.api.plugin.PluginClassloader.loadClass(PluginClassloader.java:59)
mcb-bungee | at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
mcb-bungee | at net.md_5.bungee.api.plugin.PluginManager.enablePlugin(PluginManager.java:341)
mcb-bungee | at net.md_5.bungee.api.plugin.PluginManager.loadPlugins(PluginManager.java:251)
mcb-bungee | at net.md_5.bungee.BungeeCord.start(BungeeCord.java:284)
mcb-bungee | at net.md_5.bungee.BungeeCordLauncher.main(BungeeCordLauncher.java:67)
mcb-bungee | at net.md_5.bungee.Bootstrap.main(Bootstrap.java:15)
mcb-bungee | Caused by: java.lang.ClassNotFoundException: org.bukkit.plugin.java.JavaPlugin
mcb-bungee | at net.md_5.bungee.api.plugin.PluginClassloader.loadClass0(PluginClassloader.java:103)
mcb-bungee | at net.md_5.bungee.api.plugin.PluginClassloader.loadClass(PluginClassloader.java:59)
mcb-bungee | at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
mcb-bungee | ... 13 more
Geyser-Spigot goes in your instance's (i.e. spigot) plugins folder; not the proxy's (i.e. bungee) plugin folder.
Would that be the same for floodgate as well?
Yes.
So under the hood the instances will forward the reformatted network messages to the proxy which would then just be onforwarded to the client without modifcation?
I believe so, but I am not entirely sure since I haven't looked at geyser in quite a while (the geyser discord would know for sure).
In your case, it would probably be better to use the geyser-Bungee, which moves the translation in front of the proxy.
I think trying Geyser-bungee would be the best bet as well. As I am not sure how the Bedrock clients would connect to bungee if bungee wasn't listening on port 19132.
I imagine setting this up is as simple as replacing BungeeCorrd-lastStableBuild.jar with Geyser-BungeeCord.jar and restart the server?
Thanks for your help
I believe geyser bungee pretends to be a bedrock server on the 19132, translates the bedrock traffic to java packets, then forwards it to the bungee proxy on 25565.
I believe that Geyser-BungeeCord.jar is a bungee plugin, and as such, goes in your bungeecord/plugins folder
From the geyser page:
Waterfall / BungeeCord is a proxy that sits in front of multiple servers. If you are running a network with Waterfall or BungeeCord, this is the version to install.
Setup Instructions:
- Download Geyser using the download button.
- Stop your server (if it is running) and place Geyser in the plugins folder.
- Start up your server and Geyser should be installed.
That looks like it has worked well. Still need to do a little more testing, but I think I am on the right track now. Thank you very much
It works!
I see where I went wrong now, I didn't notice the waterfalkl/bungee tab on the downloads page and was just downloading the spigot one. Again, thank you very much for helping me. My kids will be ecstatic when they get home from school today
w mom
Fr
Regarding floodgate (which is required for direct bedrock login), you have to install floodgate bungee on the bungeecord instance and install floodgate spigot on all the backend servers connected via bungee
Then you have to copy the key.pem generated in the bungee server's floodgate config folder to all the backend servers' config folders (replace the existing ones in the backends)