Closed Lamby777 closed 1 year ago
github-actions[bot]
commented
1 year ago This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.
Issues should be closed if:
Lamby777
commented
1 year ago This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.
Issues should be closed if:
- They are duplicates of other issues
- There is not enough demand
- They are no longer relevant
- There are not enough details
amogus
Lamby777
commented
1 year ago Is there even something Wurst can do to detect this? I found that changing that one property in server.properties (forgot which one exactly) will make Wurst recognize that chat signing is off, but...?
Alexander01998
commented
1 year ago I don't think there is anything that Wurst can do about this. As long as the enforce-secure-profile option is enabled in server.properties, the server forces all clients to send reportable messages.
The NoEncryption plugin works by preventing the server from passing the message reporting data on to other clients, so that players can't report each other. But as long as enforce-secure-profile stays enabled, clients are still forced to send the reporting data and they simply have to trust that the server won't give it to other players.
Lamby777
commented
1 year ago I don't think there is anything that Wurst can do about this. As long as the
enforce-secure-profileoption is enabled in server.properties, the server forces all clients to send reportable messages.The NoEncryption plugin works by preventing the server from passing the message reporting data on to other clients, so that players can't report each other. But as long as
enforce-secure-profilestays enabled, clients are still forced to send the reporting data and they simply have to trust that the server won't give it to other players.
Oof. In that case, the error is kinda misleading but it's still good to see just in case the server might be conditionally sending unencrypted messages (so you don't have to just trust them). Closing.
Description
I can't talk on my 1.20.1 server even though I installed the NoEncryption plugin. If I disable this Wurst feature, my chat messages show up as not being reportable, so I don't see why it won't let me talk.
(pirate language > english ofc)
Steps To Reproduce
Please make a list of steps to reproduce the problem (ideally from a fresh Wurst installation):
Crash Report
Please find your crash report file at "%appdata%/.minecraft/crash-reports", open the file in a text editor and copy-paste its content below.
Please note: If the game did not crash, please hold down F3+C for 10 seconds to generate a crash report. Even when a bug doesn't cause the game to crash, this file still contains useful information that can help us to find and fix the problem. Because of this, please always include a crash report.