No Chat Reports

No Chat Reports

43M Downloads

No Chat Reports kicks player on first join

Kichura opened this issue ยท 5 comments

commented

Modloader

Fabric

Minecraft Version

1.19.3

Modloader Version

Fabric Loader 0.14.17 + API 0.75.1+1.19.3

No Chat Reports Version

1.19.3-v2.0.0

Modpack Info

No response

The latest.log File

No response

Bug Description

When entering servers that the player has never logged on to before, Typing anything into chat puts Server refused to deliver unsigned message. You can enable chat signing by changing your signing mode or through prompt screen. and other times kicks the player for Received chat packet with missing or invalid signature. instead.

Steps to Reproduce

  1. Make a clean 1.19.3 aternos/whatever server that has no player data on it,
  2. Join the server after applying it,
  3. Try typing anything,
  4. Possibly get one of those things to happen.

Other Information

The commit before the defaultSigningMode config implementation seems to solve it from what i can tell.

commented

I've heard the claims but have not been able to reproduce it myself on a fresh Paper server. Any more specific criteria you've noticed that results in this?

commented

I've heard the claims but have not been able to reproduce it myself on a fresh Paper server. Any more specific criteria you've noticed that results in this?

My only figures would be to check if it was then ViaFabric combined or something else causing it because i literally have no clue what i have done wrong and what mod is truly causing issues but i can provide the full mod list i used before testing with only alternate account and only required mods. (Mods list can be found btw)

commented

Please check whether it happen on Forge.

commented

Please check whether it happen on Forge.

i cannot do forge because it actually tends to break during install compiling, in short i am basically unable to do your request as desired.

commented

Please note that Server refused to deliver unsigned message. You can enable chat signing by changing your signing mode or through prompt screen. is typically an intended behavior, this message appears if server doesn't accept unsigned messages and current/default signing mode isn't set to immediately start signing in such case. Kicks shouldn't happen though.
I couldn't reproduce the issue either, so I guess I'll let this hang until someone gives us more info.