A collective is a group of players with a shared identity and collective server. Create one through the Collective app or accept an invitation. Review the name, tag, cost and membership requirements before confirming.
Members and roles
The leadership manages membership and roles. The available controls depend on your role, so being a member does not make every destructive server action available. Members can view the collective's security state; leadership, co-owners and authorized admins can operate its protection. Emergency shutdown remains a leadership action.
Coordinate before changing shared software or hardware. A collective server has shared resources and protection cooldowns, not a fresh set for each member.
Pay for shared protection
An authorized member can fund a security subscription from their own bank account. The paid period belongs to the collective server. If that member loses permission, their future debit authorization ends; a successor needs to select an eligible account. Paid time already purchased remains available.
Where offered during virus installation, an authorized member can select the collective server as controller. That assignment stays fixed. Earnings still belong to the installing player, but a collective emergency shutdown sacrifices income viruses assigned to that controller.
Conflict
Collectives can become involved in DDoS conflicts and wars. The collective view shows the current state, score and duration. Attacks and retaliation can escalate beyond one member, so coordinate with your team before treating an attack as a private matter. For the attack itself, see DDoS.