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
Description
Details
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- Settings
Event Timeline
Comment Actions
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");Comment Actions
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.
Comment Actions
This issue still continues to persist in version 1.66.139279 RC1 (11-11-2016). Come on, guys.
Comment Actions
disableChannels settings cease to work when leaving/rejoining mission in version 1.76.142872.