![]() I usually had the two side buttons on my mouse set to push-to-talk, one that for talking up the hierarchy, one for talking downward. You can set up overlapping rooms where team leads hear their team member's voice chatter and their superior's voice chatter, and have the option of communicating in either direction. This is invaluable when you need to coordinate dozens or hundreds of players in real time. The hierarchy can be set up to affect what people hear, and where they can speak. Nowadays I use my Mumble server for cooperative remote work, a job which it works perfectly for. Mumble's use case is exclusively on the team voice chats but it lacks any direct support for anything else which is likely why we never used it, even after I provided a server for free. Each combination above solved those problems, each with its own unique benefits and drawbacks. They wanted persistent chat for text and images, put up announcements to guide new players, have votes/elections, and use team voice chats during play sessions. The needs of the community didn't really change. In the beginning it was all Skype, then we switched to Ventrilo and PhpBB, then many went to FB for text, then to Teamspeak for voice, then to Slack for text again, and now Discord for both text and voice. ![]() ![]() ![]() Therefore what I have seen is people leaving both Slack and Ventrilo in order to put it all on Discord.Īs someone who managed a gaming guild since 2005, I have seen many iterations. Discord merged the voice channels of Teamspeak/Ventrilo with the text chat system of Slack. ![]()
0 Comments
Leave a Reply. |