Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't connect to a server #290

Open
stantios opened this issue Mar 24, 2023 · 6 comments
Open

Can't connect to a server #290

stantios opened this issue Mar 24, 2023 · 6 comments
Labels
bug Something isn't working library: core Related to the core library.

Comments

@stantios
Copy link

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

This was also transferred from the Quilted Fabric API gituub since I think it is an issue with QSL having a different registry system to match mods whereas Fabric doesn't really care at all

Screenshots:
image

@Patbox
Copy link
Contributor

Patbox commented Mar 25, 2023

This is issue with you trying to join 1.19.3 server with 1.19.2. Because of experimental content (in this case camel), registries aren't matching required (vanilla) entries. It's pretty much intended behaviour.

@stantios
Copy link
Author

But experimental features was not enabled on the server so I don't understand how that works?

@Patbox
Copy link
Contributor

Patbox commented Mar 25, 2023

Even if they aren't enabled, they are still registered/present in game's registries (so technically you could place 1.20 blocks with some extra mod/tool and they would be preserved without enabling experimental features)

@stantios
Copy link
Author

Oh, I didn't know that. I guess it's this issue can't be resolved due to registries missing on 1.19.2, the server uses ViaVersion with ViaBackwards to allow older clients and newer clients to join so how would that work?

@Patbox
Copy link
Contributor

Patbox commented Mar 25, 2023

ViaFabric could mark every vanilla entry as optional (with qsl api), which would allow it to bypass registry sync

@stantios
Copy link
Author

stantios commented Mar 25, 2023

The thing is they don't support old versions and adding new features to them as they only support the latest version of each major version like 1.19.4, 1.18.2, 1.17.1 and morr. So someone would probably need to make an addon of some sort to allow ViaFabric to mark every vanilla registry as optional to bypass the registry sync.

@ix0rai ix0rai added bug Something isn't working library: core Related to the core library. labels May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working library: core Related to the core library.
Projects
None yet
Development

No branches or pull requests

3 participants