-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Does not fetch signatures when installed clientside on Quilt #423
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Then I'd assume it is caused by EssentialsXChat, try disabling that. |
Let me reassure you that I am not unwilling to fix plugin compatibility issues, and in fact, I have done so in the past. However, I require a conclusive report that specifies exactly which plugin causes the issue and under what circurmstances, so that I may reproduce it myself and figure out what action would be appropriate on our side regarding this, if any. |
Sorry for accidental closure, misclicked. |
I don't think this is because of essentialsx chat. I have tried on a different server, and I have the same problem. As you can see in my server.properties, enforce-secure-profile is off, and here are my plugins, .minecraft.zip |
This comment was marked as outdated.
This comment was marked as outdated.
I think you should replace LiberatedChat with FreedomChat. My server also uses EssentialsXChat (and FreedomChat), but this issue did not occur. In addition, I am using the Forge 1.20.1 client and the server is Leaves. |
The reason I think it is my client is because it kicks even when I allow no chat reports to send reports. I will try freedomchat though. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Shouldn't this work with vanilla servers, though? It used to auto-disable, and this is an issue with Sodium Plus (the client), not the server. The server config shouldn't matter. Has this been tested on vanilla servers? The same thing happened to me. |
By the symptoms, this may be an issue with the way NCR interacts with the Quilt client, so the signatures may not be fetched in the first place. Aizistral has said he'll have a look at it. |
I'm having this issue as well.
Indeed, I was kicked off vanilla servers with |
Facing the same issue on my client while using the Quilt loader all the time. Can confirm. |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
I feel like new versions of NCR should not be tagged as compatible with Quilt on Modrinth until this is fixed, because it's currently not really usable on Quilt. |
Per request, 1.20+ versions no longer have the Quilt marking. If you can reproduce it in earlier versions, let us know. |
Temporarily, that works, but it would be better to have this issue sorted out in the future. Been using fabric for a couple months instead of quilt which isn't ideal, since there's some mods I simply cannot use. |
any updates on this one? i see this has the "3rd party" label now, is there anyone in particular this needs to be reported to? |
Modloader
Quilt
Minecraft Version
1.20.1
Modloader Version
0.19.2
No Chat Reports Version
1.20.1-v2.2.2
Modpack Info
https://modrinth.com/modpack/sodiumplus
The latest.log File
https://gist.github.com/NoSadBeHappy/43ea1b31f6fe58ce50e9578158ad7eab
Bug Description
When chatting in my server, the server kicks me even if I have it set to allow chat reports.
Steps to Reproduce
Other Information
The text was updated successfully, but these errors were encountered: