adjust for 1.17

Common-Issues.md

@@ -1,5 +1,8 @@
 Commonly, people may have issues with Geyser not showing up in their server list or run into similar issues. This page contains a few common issues people may encounter that you might have as well as potential fixes for them. If you still can't make it work, join [our Discord](https://discord.geysermc.org) for support.
 
+# Floodgate
+For Floodgate issues see: [Floodgate: Known Issues/Caveats](https://github.com/GeyserMC/Floodgate/wiki/Issues).
+
 # I can't connect! (Either the server doesn't show up in the friends list or I get "Unable to connect to world")
 
 ## If the server doesn't show up in the friends list
@@ -41,19 +44,19 @@ This option will most likely not help if you are getting "Unable to Connect to W
 
 ***If you are using a plugin version:*** in your Geyser config, set your remote address to `127.0.0.1`. If that does not work, check your startup log for a message about Docker, and use that address in the remote address
 
-## Server is in Online Mode while Geyser is in Offline Mode (Access token can not be null or empty)
+### Server is in Online Mode while Geyser is in Offline Mode (Access token can not be null or empty)
 If you have your configuration set up like this, put simply, it won't work. If authentication for the Java server is set to online, it is expected Geyser is configured the same way. The server requires a valid Minecraft: Java Edition account, and if you aren't logging into one with Geyser, then you will be unable to join the server. If your configuration is set up properly and you're still getting this issue, it could be that your credentials are invalid.
 
-## Connection Refused: <INSERT IP AND/OR DOMAIN>
+### Connection Refused: <INSERT IP AND/OR DOMAIN>
 
 Connection Refused usually means that a Java server could not be found on that port, or the server denied access to the connection on a network level. The latter can happen with anti-DDOS plugins such as TCPShield, but otherwise ensure that the server you're trying to connect to is spelled correctly in the config, is up and is port forwarded correctly.
 
 If you're updating from an old build of Geyser, set your remote address to `auto` and try again.
 
-## Floodgate Misconfiguration
-See [this page](Floodgate) for more information.
+### Floodgate Misconfiguration
+See [this page](https://github.com/GeyserMC/Floodgate/wiki/Issues) for more information.
 
-## Mojang Resetting Account Credentials
+### Mojang Resetting Account Credentials
 This is unfortunately something we have no control over, and is most likely the case when you're running Geyser as a plugin on a server host or joining a friend far away from your location. If you're running Geyser locally, this should not happen to you, but what we recommend for servers is a plugin we make called [Floodgate](https://github.com/GeyserMC/Floodgate), which allows for Bedrock clients to join your server without needing a Java Edition account. Take a look [here](Floodgate) for more information. 
 
 # "Invalid IP address!" from Bedrock
@@ -78,9 +81,4 @@ Update the server or ask them to install ViaVersion.
 
 # Query: Incorrect Magic!
 
-See here: https://www.spigotmc.org/threads/query-incorrect-magic-and-high-cpu-usage.159386/#post-2709057
-
-# Floodgate
-For most floodgate issues see: [Floodgate: Known Issues/Caveats](Floodgate#known-issuescaveats).
-## If you wish to use IP forwarding, please enable it in your BungeeCord config as well!
-It is likely you have enabled `send-floodgate-data` in your Floodgate config but either Floodgate isn't installed on the target server or you floodgate keys aren't the same between the installs of the plugin, please copy them so they all use the same set.
+See here: https://www.spigotmc.org/threads/query-incorrect-magic-and-high-cpu-usage.159386/#post-2709057

Floodgate.md

@@ -1,3 +1,9 @@
+# This is an archive of the old Floodgate 1.0 wiki. Please refer to the new [Floodgate wiki](https://github.com/GeyserMC/Floodgate/wiki) for documentation on the latest version of Floodgate.
+
+<br>
+<br>
+<br>
+
 Floodgate is a hybrid mode plugin which allows for **Minecraft: Bedrock Accounts** to join **Minecraft: Java Edition** servers without needing a Minecraft: Java Edition account. This is something you install **in addition** to Geyser. Unlike Geyser, Floodgate can **only** be installed as a plugin on Spigot (including Paper and forks), Bungeecord, and Velocity, and can only be utilized on servers that have it installed. 
 
 [Download](https://ci.opencollab.dev/job/GeyserMC/job/Floodgate/job/master/)

Setup.md

@@ -9,7 +9,7 @@ And if you still have questions, feel free to join the [Discord](https://discord
 ## Prerequisites
 
 - The server you are connecting to has to support the latest version of Minecraft Java Edition (at this time this is Minecraft 1.16.5). The server itself does not have to be the latest version but does have to allow connections. If you're running the server on an older version, you can use the plugin [ViaVersion](https://www.spigotmc.org/resources/viaversion.19254/), but do note that only **1.12.2 and any version above is officially supported**.
-- If you are connecting to an online mode Java server, a paid Java account is required. If you are running the server, you can bypass this requirement for your server with [Floodgate](https://github.com/GeyserMC/Geyser/wiki/Floodgate).
+- If you are connecting to an online mode Java server, a paid Java account is required. If you are running the server, you can bypass this requirement for your server with [Floodgate](https://github.com/GeyserMC/Floodgate/wiki).
 - Your Bedrock client has to be a supported version - at this time that is any Bedrock 1.16 stable version from 1.16.100 to 1.16.220.
 - If you are running the server, you need to have a UDP port opened. See below for more instructions.
 
@@ -44,7 +44,7 @@ Once you're done, open up Minecraft: Bedrock Edition and in the **Friends** tab,
 ### Standalone Setup (Geyser and Floodgate are not on the same server)
 If you want to offload Geyser's processing you can host Geyser (Standalone) somewhere else and make it redirect to your server. 
 **Warning:** Do not forget to edit the remote section of your Geyser config.
-See the [Floodgate](https://github.com/GeyserMC/Geyser/wiki/Floodgate) wiki page for more details.
+See the [Floodgate](https://github.com/GeyserMC/Floodgate/wiki/) wiki page for more details.
 
 ## Port Forwarding
 

Supported-Java-Software-Versions.md

@@ -1,9 +1,5 @@
 While Geyser aims to support all Java program versions, not every version will fully support Geyser.
 
-### Java 16
-
-Java 16 currently does not support encrypting Bedrock client connections - any information from Geyser to the client can theoretically be seen by others! This will be fixed before Minecraft 1.17.
-
 ### Older Java 8 versions
 
 Older Java 8 versions do not properly support the type of encryption Bedrock requires, including the one bundled in with Minecraft: Java Edition by default. Update your Java version if you're unsure.

Understanding-the-Config.md

@@ -26,7 +26,7 @@ Options for the remote (java) server.
 
 **`auth-type`**: The authentication type of the Minecraft: Java Edition server. Valid options are `online`, `offline`, and `floodgate`.
 
-**Please keep in mind, what you specify in the Geyser `auth-type` option MUST be the same as what the remote server has (with the exception of Geyser being in online mode and remote being in offline mode). You simply cannot join an online mode server without a genuine account. If you want to allow Minecraft: Bedrock Edition accounts to join without a Minecraft: Java Edition account, see the [Floodgate](Floodgate) page.**
+**Please keep in mind, what you specify in the Geyser `auth-type` option MUST be the same as what the remote server has (with the exception of Geyser being in online mode and remote being in offline mode). You simply cannot join an online mode server without a genuine account. If you want to allow Minecraft: Bedrock Edition accounts to join without a Minecraft: Java Edition account, see the [Floodgate](https://github.com/GeyserMC/Floodgate/wiki/) wiki page.**
 
 **`use-proxy-protocol`**: Whether to enable PROXY/HAProxy protocol or not while connecting to the server. This is useful only when:
 - Your server supports PROXY protocol (it probably doesn't)
@@ -37,7 +37,7 @@ Options for the remote (java) server.
 ## General Options
 General Geyser options that are mostly specific to Geyser itself.
 
-**`floodgate-key-file`**: The key file path for Floodgate. Requires that you have [Floodgate](https://github.com/GeyserMC/Floodgate) installed and the `auth-type` set to `floodgate`.
+**`floodgate-key-file`**: The key file path for Floodgate. Requires that you have [Floodgate](https://github.com/GeyserMC/Floodgate/wiki/) installed and the `auth-type` set to `floodgate`.
 
 **`userAuths`**: A section where you can put the authentication information for your Minecraft: Java Edition account for immediate login when joining Geyser. **It is advised you ONLY use this option if you are running Geyser locally and that ONLY you have access to the config as it requires you put your Minecraft: Java Edition credentials in plain text!**
 
@@ -154,7 +154,7 @@ remote:
   # The port of the remote (Java Edition) server
   # For plugin versions, if address has been set to "auto", the port will also follow the server's listening port.
   port: 25565
-  # Authentication type. Can be offline, online, or floodgate (see https://github.com/GeyserMC/Geyser/wiki/Floodgate).
+  # Authentication type. Can be offline, online, or floodgate (see https://github.com/GeyserMC/Floodgate/wiki).
   auth-type: online
   # Allow for password-based authentication methods through Geyser. Only useful in online mode.
   # If this is false, users must authenticate to Microsoft using a code provided by Geyser on their desktop.