Closed c0wg0d closed 4 years ago
Thanks, tested on 1.8.8 and 1.16.2 and fixed the problem, please use the next version when it is ready.
I see in 8.7.12 you mention fixing the ProtocolLib issue and the error in question, and in 8.7.11 you mention fixing the issue of players not joining channels when using MySQL, but I'm not using MySQL, and as I said in this report, I don't always get this error. Are you saying that my issue is fixed in 8.7.12 in regards to players not auto-joining channels properly?
I am very confident that this got solved.
If not please set Debug to [channels] and let me know console log when it happens again.
This bug is reoccurring now in 8.9.0-BETA. Only 1.12.2 servers seem to be affected by this. 1.16.3 servers do not have this problem.
Any errors? Do you have both 1.12 and 1.16 on your network?
Yes I have both 1.12 and 1.16 servers on my network. There are no errors. The players just tell me they get an error from CHC "No channels to write to." There should always be a channel to write to because each server is given the permissions I listed above, and players do not have permission to use the /ch command. It should always be fully automatic.
https://www.loom.com/share/fe4021b557b44d3c9979bf85f3036518
Is it possible you start using MySQL? We're going to enforce this if one uses BungeeCord starting the next ChatControl anyways because of how data is transferred it makes sending much more efficient.
Regarding this problem here, please set Debug to [channels] on 8.9.1 and let me know the output when players rejoin back and lacks the channel
What is loom.com?
I can start using MySQL but I really wish there was an option to not use a database at all. ChatControl v7 didn't have a database and I never had these kinds of problems.
I recorded video for you, you can view it on that page.
There are so many benefits to using database over Bungee we could not make it effective enough without it. Literally would have to do ninja shit and split packets which could cause more problems than fix
I see the video--thanks for that. One player who experienced this problem today told me they changed their Minecraft name recently, and also they were logged in with MineChat. Maybe MineChat is doing something weird/irregular that Minecraft doesn't do? Maybe a name change will cause an issue if they don't exist in data.db before joining?
We don't actually support name changes in ChatControl 8, but that's already added to ChatControl 10 :)
I upgraded from BungeeControl 2.3.0 and ChatControl 8.7.1 to BungeeControl 2.3.4 and ChatControl 8.7.10.
I have many servers on Paper 1.8.8, 1.12.2, and 1.15.2.
When a player first joins, they can write in chat normally. When they switch to another server, they can write normally there also, but when they go back to the first server they were on, they get the error "You have no channel to write into. Type /ch for help."
There are no errors in the console most of the time, but I did see this one on occasion:
I have deleted all the ChatControl data.db files and restarted all the servers multiple times, and this issue always occurs with ChatControl 8.7.10. When I revert to ChatControl 8.7.1 and BungeeControl 2.3.0, without changing anything else, everything works as expected.
I do not give my players access to the /ch join command because I want chat to be automatically joined for whatever server they go into.
In my main hub/lobby server, I have the following permissions set automatically for all players:
In my adventure server, I have the following permissions:
This is replicated across all my servers, and each server has their own channel setup in ChatControl.
channels.yml
formatting.yml