Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (โ‹ฎ) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Leaderboard

Popular Content

Showing content with the highest reputation on 08/05/22 in all areas

  1. Neither of those logs contains the "DecoderExceptions (incorrect header check, invalid distance too far back, etc.)" error message? The server does have a message saying you disconnected as you say. And the client has a message saying JEI is responding to a disconnect event, but no error message. The "DecoderException" error message says there is a problem with the decompression of the network packet. One thing I notice is you have the following on the client: but on the server it is So it looks like the server is trying to use ipv6. If you look at the changelog for forge 1.18.2 https://maven.minecraftforge.net/net/minecraftforge/forge/1.18.2-40.1.69/forge-1.18.2-40.1.69-changelog.txt It says So one option would be try the latest release of forge, 40.1.69 which has this change. Another would be to configure the server to use ipv4 like the client? -Djava.net.preferIPv4Stack=true NOTE: I don't know if this really the cause of the DecoderException, it could be caused by one of the mods and the ip version is just a red herring. ๐Ÿ™‚

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions โ†’ Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.