

Most players will listen to other players when they're asked to talk on the local frequency/channel or the channel not using a repeater. But leaving them with a spoon within the game probably isn't a great idea either. Most players are not amateur radio enthusiasts or have ever worked a job using radios within the real world. Short range communications (or local transmissions not utilizing a repeater), of course, should be strongly condoned and made the default. In the past, long range communications were limited due to equipment size. Should clarify players, whether beginners or squad leaders, should all have access to both short and long range communications when possible. (I should mention, all of this information I provided within this post is easily obtained by reading your local national Amateur Radio public guides. I fret since this is such a current mess, when the larger map is released on final release, communications will be futile! (The final map is suppose to be 20x's the size of Stratis?) The only real way of managing 100+ players will be to ensure communications are limited by range as they are within the real world, and Groups are effectively implemented within the maps.

This additional scripting, players can not easily utilize at most times. Hence, keeping pilots all to one group, as with other operations!Ĭurrently, the maps I've seen poorly implement the groups, making Group Channel useless unless the map integrates a "move to another group" scripting. Keep all specialized unit groups to a minimum, or integrate your Special Unit slots into the previously mentioned groups. Maybe an additional for special sea ops moving to ground ops.

Should be no more than two ground ops groups. Should be one sea group, containing all sea ops.

Should be one pilot group containing all pilots. All pilots should be placed into one group within maps, so they can all communicate as main air traffic control frequency and not clutter the ground ops channels. It gets a little irritating with people using TeamSpeak, usually those boasting of it's features, always transmit assuming everybody knows who they are! -)Ībout the only benefit of TeamSpeak is it's adjustable quality of record and playback.Īlso, the map makers are still separating pilots and/or implementing too many multiple groups, effectively making Group Chat channel useless. Ditto concerning names not showing with TeamSpeak.
