QuiltMC / quilted-fabric-api

Re-implementation of the Fabric API using QSL as implementation instead.
Apache License 2.0
85 stars 32 forks source link

Can't connect to a server #82

Closed Imzxhir closed 1 year ago

Imzxhir commented 1 year ago

QFAPI / QSL Version: QFAPI 4.0.0-beta.28 and QSL 3.0.0-beta.29 Log: https://mclo.gs/ambk4hB

Description: I tried to join this whitelisted server that supports both 1.19.3 and 1.19.2 clients with the mods that I play and then I get an error message (shown in screenshots). I went through my mods list and found that this only happens when QFAPI / QSL is enabled, as when I have no mods in my instance / folder with just Quilt Loader 0.18.2, I can connect to the server with no issues

Screenshots: image

ix0rai commented 1 year ago

this is not a qfapi issue, the registry is mismatched

[19:30:05] [Netty Client IO #1/WARN]: Missing entries for registry "minecraft:entity_type":
- minecraft:camel
- polysit:seat
Imzxhir commented 1 year ago

So, this is an issue with the server?

ix0rai commented 1 year ago

it could be. could you try connecting from 1.19.3? that will solve the minecraft:camel issue, and possibly the polysit issue with it.

Imzxhir commented 1 year ago

Joining with 1.19.3 solves the issue but that's expected since the server itself is 1.19.3 and has ViaFabric to allow older versions to join the server.

Imzxhir commented 1 year ago

Also, this doesn't happen when only having Fabric Loader and Fabric API.

ix0rai commented 1 year ago

Strange, I'll look into this when I have time

Imzxhir commented 1 year ago

This could be an issue with QSL as I think uses a different a registry system to match mods whereas Fabric doesn't really care at all.

codegoose commented 1 year ago

I had this issue yesterday. I was able to get past it by copying the config folder from the client to the server. My thought was to ensure that both folders had exactly the same content.

Is Quilt just checking all the files in that folder for the same hash or is it more complex?

Imzxhir commented 1 year ago

This could be an issue with QSL as I think uses a different a registry system to match mods whereas Fabric doesn't really care at all.

I think it has something to with this so I think it's a QSL issue, I'm going to close this and reopen it on the QSL Github.