Example: You have a mission with disableChannels[] = {{0,true,true}}; in description.ext to block global chat, and the mission is hosted on a persistent dedicated server. If a player joins and waits until spawned, goes back to lobby, and rejoins the mission, then the settings are ignored and he can still use global chat.
Description
Details
- Severity
- Minor
- Resolution
- No Bug
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- Settings
Event Timeline
Universal workaround for usage in a preInit function:
{ _x params [["_chan",-1,[0]], ["_noText","true",[""]], ["_noVoice","true",[""]]]; _chan enableChannel [(_noText != "true"), (_noVoice != "true")]; } forEach getArray (missionConfigFile >> "disableChannels");
This issue still persists in version 1.64.138310 RC (09-09-2016).
I will emphasise that this issue will only occur if the player aborts to the role selection screen/lobby and then rejoins. The issue will not occur they fully disconnect from the server and then reconnect.
This issue still continues to persist in version 1.66.139279 RC1 (11-11-2016). Come on, guys.
disableChannels settings cease to work when leaving/rejoining mission in version 1.76.142872.
Still not fixed.
Sometimes it works, sometimes doesn't, you even don't need to go back to lobby, and rejoin a mission.
Unfortunately, I can't provide a list of concrete steps to reproduce this bug. The only info I can provide is that I have a dedicated server with this piece of code in Description.ext:
disableChannels[] = { { 0, // global false, // enable text true // disable voice } };
And despite this, when I join to the server VoN is sometimes available through global channel.
The global channel is never disabled for admin or server host could you provide the steps to reproduce please
Thanks for the explanation! Probably I was wrong, at least I couldn't reproduce this "bug" by launching a dedicated server on my local PC and connecting to/disconnecting from it many times. I'll keep watching and let you know if I can reproduce it.
Well, after a week of testing I couldn't reproduce this "bug". Seems I was confused by the fact that when I logged in as admin global channel was available.
Again, thanks for the explanation, @BIS_fnc_KK (makes sense to update BIKI), and sorry for the false alarm.