Party Balancing

Party balancing occurs automatically when an activity's signup period closes. This system ensures optimal party composition based on roles, gear scores, and party types.

When Does Balancing Occur?

• When the activity reaches its Close Signup threshold (10 minutes to 24 hours before start)
• When a manual balance is requested by the activity manager (coming soon)

How Balancing Works

Gearscore Balancing

• Distributes players to achieve similar average gear scores across parties
• Swaps compatible players to minimize gearscore gaps
• Maintains role requirements while balancing

Role Distribution

• Maintains required roles per party type
• Matches weapon preferences
• Preserves static party compositions

Balancing Priority

1. Static Parties: Remain unchanged unless insufficient members; larger static groups have higher priority
2. Role Requirements: Ensures each party has necessary roles filled
3. Gearscore Distribution: Aims for similar average gearscore across parties (only players with gearscore ≥ 1000)

Balancing Rules

• Respects party type role requirements
• Maintains weapon preference matches
• Preserves static party assignments
• Players stay in their assigned roles
• Static party members stay together when possible

Best Practices

1. Set appropriate Close Signup threshold
2. Configure party types with clear role requirements
3. Define weapon preferences accurately
4. Keep player gearscores updated
5. Assign appropriate roles
6. Use unique party types for statics

Limitations

• Cannot break static party compositions
• Must maintain party type role requirements
• Limited by available player roles
• Only considers players with gearscore ≥ 1000

Troubleshooting

• Check role availability and gearscore distributions
• Review party type requirements
• Confirm static party attendance and configuration
• Adjust player assignments if needed

Related Guides

• Static Party Types
• Party Types
• Automatic Party Assignment
• Party Announcements