How the Rust team system works, how to communicate, manage group access, and coordinate effectively with teammates.
Rust is fundamentally a multiplayer game where coordination with teammates determines success far more than individual skill. The team system, combined with external communication tools and proper base management, allows groups to compete against larger teams and defend against raids effectively.
Any player can create a team by opening the inventory and selecting the create team button at the bottom left. The creator becomes the team leader. The default maximum team size on vanilla servers is 8 players, though individual servers can increase or decrease this limit. Members are added through leader invitation or by the leader pressing E on a target player to add them.
Once teammates are in a team, they appear as green dots on your map when online and alive, grey when offline, and red when dead. Teammate names display above their heads, making it simple to distinguish your group from enemies in chaotic fights. The team chat channel provides text communication visible only to team members.
The clan system extends team functionality for larger groups. A clan table can be crafted or found at Outposts. Clans allow members beyond the standard 8-player team limit and provide a unified identifier for your group. Clan members appear on the map only when within three grid squares of your position, unlike regular teams where all online members are visible. Clans are essential if your group exceeds 8 players or if you want organized hierarchy and permissions management.
Rust has built-in proximity voice chat. Pressing and holding V broadcasts your voice to all players within a certain radius, including enemies. This is useful for quick interactions with strangers in safe zones but dangerous for team communication. Anyone nearby can hear what you say, compromising security and tactical information.
Use Discord or TeamSpeak for team communication instead. External voice chat keeps conversations private and prevents enemies from hearing your plans. Push-to-talk is essential. Configure Discord with push-to-mute so you do not accidentally broadcast in-game proximity audio to your team.
Enable voice chat disable in your Rust client when using Discord. This prevents your teammates from hearing both your Discord voice and the in-game proximity audio doubled, which is distracting and unprofessional.
Code lock codes must be agreed upon before building. All team members need the code for rapid base entry. Code raiding is a real threat, so some teams use separate codes for outer doors versus inner loot rooms. This layered approach means even if raiders guess the outer code, they cannot access valuable storage.
Authorization on the Tool Cupboard is critical. Hold E on the TC and add all teammates who need building rights. Removing a single player requires clearing all authorization, which removes everyone. You then need to re-authorize remaining members. Plan your authorization strategy before wiping, as the TC is your most important structure. If the TC decays or gets destroyed during a raid, your entire base can decay in response.
Name sleeping bags clearly with each teammate's name. This prevents confusion during respawns and makes it obvious which bags belong to departed team members who should be removed. When someone leaves your group, removing their sleeping bag prevents them from respawning in your base and disrupting operations.
Designate one or two players to research main blueprints like weapons and armor. Other teammates focus on specialized items like syringes, ammo types, and tools. This prevents duplicate research and accelerates your tech tree progression. Assign specific researchers to specific tech paths early wipe and maintain that organization throughout.
During raids, communication is essential. Assign roles before the raid: one player scouts the target and calls positions, others gather explosives, another manages logistics. Assign a raid leader who makes tactical decisions on the fly. Avoid argument during execution. A decisive call made quickly beats a perfect decision made too late. Debrief after raids to discuss what worked and what could improve.
Assign defensive positions before a raid starts. One player covers the north approach, another covers south, etc. Ensure all defending players can hear each other in Discord. Coordinate rotations so you are not all in one location. When raiders breach a wall, immediately reseal if possible. The player nearest the breach focuses on repair while others maintain defense. Teamwork stops raids more effectively than any base design.
For base design considerations related to team coordination, see the base design guide. For details on defending during raids, check raid defense fundamentals and advanced raid defense. Understanding map navigation helps your team coordinate faster across the server.