From 1b25702c6b19744f19302ddd91d1555273efa044 Mon Sep 17 00:00:00 2001 From: Adrian Bergqvist <52883522+adde0109@users.noreply.github.com> Date: Mon, 12 Jun 2023 20:36:16 +0200 Subject: [PATCH] Update README.md --- README.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index abaae7c..2656d10 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ Unlike other solutions, this plugin does not require any special modifications t 1. Download and install this plugin to your proxy. 2. After starting the server, configure the plugin it to your liking using the config file found in the folder "Ambassador". 3. If you want to use player-information forwarding you can use any of these mods on the 1.13+ forge server: -- https://github.com/adde0109/Proxy-Compatible-Forge (Modern forwarding) +- https://github.com/adde0109/Proxy-Compatible-Forge (Modern forwarding) (Magma 1.18.2 and higher includes this) - https://github.com/caunt/BungeeForge (Legacy forwarding) @@ -20,11 +20,7 @@ https://github.com/Just-Chaldea/Forge-Client-Reset-Packet https://github.com/adde0109/Forge-Client-Reset-Packet ## Stuck on "Negotiating": -Why: This is happening because the client finishes the reset after the reset-timeout time has passed and thus, the proxy disconnects the client and the screen. Usually because to the client took too long to reset the forge registries. - -Fix: Increase the "reset-timeout" in the config. -If you know that everyone who is connecting to the server is using the packet client reset packet mod (Pixelmon include this mod), you can set this value to the max (Velocity's timout found in Velocity.toml). -This timout is meant to allow for people that doesn't have the mod to get disconnected more quickly. +This is an issue with Client Reset Packet Mod being partly incompatible with certain mods on the client. Please remove incompatible mods on the client if you have this issue. (Yes, this also includes client-side only mods.) ## Discord https://discord.gg/Vusz9pBNyJ