Distant HorizonsDH
Distant Horizons•14mo ago•
70 replies
ecaphet

[Resolved] DHS plugin protocol mismatch bug - “the Forge byte”

Hey guys! So i'm using [DHS] 0.6.1 on my paper server which i believe does not support the latest nightly build for 1.21.1 client in #links-n-downloads.

I've also tried DH 2.3.0 RC1 in #announcements , but F3 also showed 
Server does not support DH
 message.

So i want to try a build that's actually supported by the server plugin, in the DHS 0.6.0 release notes:
Adds support for DH 2.3.0 nightlies built after 2024-10-18.

Does anyone still retain a nightly build from that time? gitlab artifacts only kept the recent builds.

Thanks in advance! Ping me if u need anything, configs, modlist, i'd be happy to provide!


UPDATE latest discussion reveals this as an underlying bug named “the Forge byte” with DH 2.3.0 RC1 and DHS 0.6.1 on MC version 1.21.1 for both client and server

UPDATE2 latest testing confirms it works for this setup:
Server(v1.21.1) PAPER with DHSv0.6.1-for-1.21.1
Server docker-compose.yml:
services:
  mc:
    image: itzg/minecraft-server
    container_name: mc
    tty: true
    stdin_open: true
    environment:
      EULA: "TRUE"
      TYPE: PAPER
      VERSION: "1.21.1"
      ONLINE_MODE: "TRUE"
      MEMORY: 4G
      MAX_MEMORY: 8G
    ports:
      - "25566:25566" # remapped port to 25566
      - "25049:25049"
    volumes:
      - ./data:/data
    restart: unless-stopped

Client(v1.21.1) fabric loader with DH2.3.0-RC1-for-1.21.1
(Along with Simply Optimized modpackv4.3-for-1.21.1)
Solution
Hehe, that's indeed great :) I suspect you accidentally used DHS for an older version of Minecraft when you tested before. I should output this info in the log
Jump to solution
Was this page helpful?
CommunitiesDocsAboutTermsPrivacy