Fix TODOs in setup.md

Co-authored-by: Olivia <chew@chew.pw>

i18n/en/code.json

@@ -784,7 +784,7 @@
     "description": "The unlisted content banner message"
   },
   "providers.provider.not_listed.description": {
-    "message": "If your hosting provider is not listed, try enabling the `clone-remote-port` option in the config. Then, restart the server, and try connecting with the same IP and port as on Java Edition. <br> If this does not work, ask your server hosting provider for a UDP port, and use that. For VPS/KVM servers please follow the self-hosting steps."
+    "message": "If your hosting provider is not listed, try using [Warden Signalling](/wiki/geyser/nethernet/setup#warden-signalling). If this doesn't work, ask your hosting provider for a TCP and UDP port and use that. For VPS/KVM servers please follow the self-hosting steps."
   },
   "providers.provider.wasabihosting.description": {
     "message": "Install Geyser with the plugin installer. Use the same port as your Java server in the Geyser config. Connect with the same address and port as your Java server."
@@ -868,5 +868,11 @@
   },
   "pages.dumpviewer.extensions.helptext": {
     "message": "Click on an extension to view more information."
+  },
+  "providers.provider.consulhosting.description": {
+    "message": "GeyserMC can be installed with a single click on ConsulHosting's Minecraft server hosting. Head to your server panel, find the GeyserMC option at Software, and install it automatically — no manual configuration needed. For step-by-step instructions, see [ConsulHosting's GeyserMC installation tutorial](https://consulhosting.com/help/install-geysermc/)."
+  },
+  "pages.download.description.floodgatedatabases": {
+    "message": "Database extension jars for Floodgate local linking."
   }
 }

i18n/en/docusaurus-plugin-content-docs/current.json

@@ -186,5 +186,21 @@
   "sidebar.geyserSidebar.category.Custom Resource Packs": {
     "message": "Custom Resource Packs",
     "description": "The label for category Custom Resource Packs in sidebar geyserSidebar"
+  },
+  "sidebar.geyserSidebar.category.Nethernet": {
+    "message": "Nethernet",
+    "description": "The label for category Nethernet in sidebar geyserSidebar"
+  },
+  "sidebar.geyserSidebar.category.Nethernet.link.generated-index.title": {
+    "message": "Nethernet",
+    "description": "The generated-index page title for category Nethernet in sidebar geyserSidebar"
+  },
+  "sidebar.geyserSidebar.category.Nethernet.link.generated-index.description": {
+    "message": "An explanation of Nethernet",
+    "description": "The generated-index page description for category Nethernet in sidebar geyserSidebar"
+  },
+  "sidebar.geyserSidebar.category.Custom Content": {
+    "message": "Custom Content",
+    "description": "The label for category Custom Content in sidebar geyserSidebar"
   }
 }

sidebars.ts

@@ -54,6 +54,19 @@ const sidebars: SidebarsConfig = {
                 'geyser/port-forwarding'
             ]
         },
+        {
+            type: 'category',
+            label: 'Nethernet',
+            link: {
+                type: "generated-index",
+                title: "Nethernet",
+                description: "An explanation of Nethernet",
+                slug: "/geyser/nethernet",
+            },
+            items: [
+                'geyser/nethernet/setup'
+            ],
+        },
         {
             type: 'category',
             label: 'Common Issues',

src/components/Provider.tsx

@@ -52,7 +52,7 @@ export const ProviderSelector = () => {
         name: 'Not listed',
         description: translate({
             id: 'providers.provider.not_listed.description',
-            message: "If your hosting provider is not listed, try enabling the `clone-remote-port` option in the config. Then, restart the server, and try connecting with the same IP and port as on Java Edition. <br> If this does not work, ask your server hosting provider for a UDP port, and use that. For VPS/KVM servers please follow the self-hosting steps."
+            message: "If your hosting provider is not listed, try using [Warden Signalling](/wiki/geyser/nethernet/setup#warden-signalling). If this doesn't work, ask your hosting provider for a TCP and UDP port and use that. For VPS/KVM servers please follow the self-hosting steps.",
         })
     } as HostingProvider);
 

wiki/geyser/nethernet/setup.md

@@ -0,0 +1,73 @@
+---
+title: Nethernet Setup Guide
+description: A guide for setting Nethernet up with Geyser.
+---
+
+Geyser now supports the new Nethernet mode of transport used by default on Bedrock as of build #1237, this is preferred over Raknet which will be removed in the upcoming 26.60 update (Date TBA).
+
+## Differences between Nethernet and Raknet
+
+The important different between Nethernet and Raknet is that Nethernet requires a TCP port **and** a UDP port, compared to Raknet that only needed a UDP port. This makes Nethernet more difficult to setup on certain hosting providers/networking setups.
+
+Nethernet will do the following with a bedrock server:
+- Contact the "Signalling" server found on the TCP port in order to get the following:
+  - The MOTD, player count and ping
+  - The connection details with bedrock will use to connect via UDP (WebRTC)
+- The client then connects to the server via WebRTC which is where the UDP port is required
+
+Raknet will do the following with a bedrock server:
+- Make a small connection to the server to get the MOTD, player count and ping
+- The client then connects to the server properly and starts sending the join data
+
+This small difference shakes up the entire networking involved when connecting to a server on Bedrock. For this reason, the migration to Nethernet may be difficult for some users; but, we're hoping with the preparation time we've been given, we can make the transition smoother.
+
+## What does this mean for you?
+
+Depending on how you host your server, this could mean different things. Generally, you need to redo your network configurations if you made any previously for your server.
+
+:::caution
+
+If you used `clone-remote-port` when setting up your Geyser server, it is important to note this option **no longer works**! You must either change the port used, or setup [Nethernet External Signalling](#nethernet-external-signalling), if you do not, the Nethernet TCP port will collide with the Java server's port and the Nethernet signalling server will fail to boot, making it impossible to connect to your server.
+
+:::
+
+### Self-hosting
+
+Ensure you have port forwarded your bedrock port for TCP also, this will allow Geyser to run the signalling server and continue accepting connections successfully. If you cannot do this for some reason, there is another option in order to get Nethernet working, see [Nethernet External Signalling](#nethernet-external-signalling).
+
+### Hosting provider
+
+When using a hosting provider, the fix is variable depending on which provider you're using, but we can help a bit here.
+
+If you manually setup your network for Geyser by assigning a UDP port, good news! There's a good chance Nethernet should just work, as many providers will also allocate a TCP port with it. However, if this is not the case, allocate your UDP port for TCP also.
+
+If you did not manage the networking, odds are you should be fine, as your hosting provider will hopefully be prepared for Nethernet, as we've given them the tools in order to get Nethernet setup.
+
+If you only needed to enable `clone-remote-port`, see the caution above, with describes why this option **no longer works**.
+
+If after this, none of those options worked, you may want to look into [Nethernet External Signalling](#nethernet-external-signalling).
+
+## Nethernet External Signalling
+
+Nethernet External Signalling (or NXS for short) is an open standard developed by [Open Collaboration](https://opencollaboration.dev/) alongside [Ziax](https://ziax.com/)! This standard allows you to run the Nethernet signalling server (the TCP port part) away from your server, then have them connect to each other!
+
+This is good because:
+- The signalling server can handle multiple servers at once, under a single port, making the networking setup more simple
+- Any external provider can be used, not just your own, for example, [Warden](#warden-signalling)
+- A hosting provider can automatically setup a signalling server and tell Geyser to use it, making setup much simpler!
+
+### Warden Signalling
+
+Warden Signalling, or just Warden, is a free service offered by [Ziax](https://ziax.com/) which Geyser can connect to in order to be given an IP which can be used to connect to your server!
+
+What this means:
+- You do not need to forward a TCP port
+- You will not have a custom IP address, but something like `turquoisemango.wdn.gg` instead
+- You **still** need to forward a UDP port for Warden to connect to, otherwise Warden will send the client to an unconnectable address
+- You do not need any other signalling server, Warden is plug and play with Geyser
+
+:::info
+
+Warden is designed for smaller servers, if you own a big server, it is strongly advised you use your own signalling server or use Geyser's built in one.
+
+:::

wiki/geyser/setup/self/modded-servers.mdx

@@ -34,7 +34,9 @@ Geyser only works with **server-side** mods. Mods that require a client-side ins
       clone-remote-port: false
     ```
    The vital part is the port. This is the port that Bedrock players will use to connect to your server!
-   If you enable `clone-remote-port`, the port will be overridden and the Java port is used.
+   If you enable `clone-remote-port`, the port will be overridden and the Java port is used, but be careful,
+   as this only works when using [Nethernet External Signalling](/wiki/geyser/nethernet/setup#nethernet-external-signalling)
+   as the Nethernet TCP port cannot collide with the Java one.
    Since you are self-hosting, you can choose the port freely - the default port is 19132.   
    **Important**: Other services/mods that rely on ports with UDP, such as Voice Chats or Query, cannot share the port with Geyser.
 

wiki/geyser/setup/self/paper-spigot.mdx

@@ -29,7 +29,9 @@ See also [this page](/wiki/geyser/supported-versions/) on supported versions.
       clone-remote-port: false
     ```
     The vital part is the port. This is the port that Bedrock players will use to connect to your server!
-    If you enable `clone-remote-port`, the port will be overridden and the Java port is used.
+    If you enable `clone-remote-port`, the port will be overridden and the Java port is used, but be careful,
+    as this only works when using [Nethernet External Signalling](/wiki/geyser/nethernet/setup#nethernet-external-signalling)
+    as the Nethernet TCP port cannot collide with the Java one.
     Since you are self-hosting, you can choose the port freely - the default port is 19132.   
     **Important**: Other services/plugins that rely on ports with UDP, such as Voice Chats or Query, cannot share the port with Geyser.
      

wiki/geyser/setup/self/proxy-servers.mdx

@@ -31,7 +31,9 @@ import { Versions } from '@site/src/components/Versions'
        clone-remote-port: false
     ```
     The vital part is the port. This is the port that Bedrock players will use to connect to your server!
-    If you enable `clone-remote-port`, the port will be overridden and the Java port is used.
+    If you enable `clone-remote-port`, the port will be overridden and the Java port is used, but be careful,
+    as this only works when using [Nethernet External Signalling](/wiki/geyser/nethernet/setup#nethernet-external-signalling)
+    as the Nethernet TCP port cannot collide with the Java one.
     Since you are self-hosting, you can choose the port freely - the default port is 19132.   
    **Important**: Other services/plugins that rely on ports with UDP, such as Voice Chats or Query, cannot share the port with Geyser.
      

wiki/geyser/setup/self/viaproxy.mdx

@@ -23,7 +23,9 @@ description: Learn how to set up Geyser with ViaProxy.
       clone-remote-port: false
     ```
     The vital part is the port. This is the port that Bedrock players will use to connect to your server!
-    If you enable `clone-remote-port`, the port will be overridden and the ViaProxy port is used.
+    If you enable `clone-remote-port`, the port will be overridden and the ViaProxy port is used, but be careful,
+    as this only works when using [Nethernet External Signalling](/wiki/geyser/nethernet/setup#nethernet-external-signalling)
+    as the Nethernet TCP port cannot collide with the Java one.
     Since you are self-hosting, you can choose the port freely - the default port is 19132.
 
     **Important**: Other services/plugins that rely on ports with UDP, such as Voice Chats or Query, cannot share the port with Geyser.