Team Combat Zones - Chdata's OSRS PvP Proposal

The Problem With Multi

Multi-combat zones are effectively clan-only content. A solo player or a small team entering a multi zone against an organised clan faces a guaranteed loss. It is 100% risk with 0% reward. There is no meaningful counter-play when 30+ players can pile you simultaneously.

PKers have told me that even small teams of experienced players avoid multi zones specifically because they know they will get completely overwhelmed by clans. This means an entire half of the Wilderness map is functionally inaccessible to anyone who is not a large PvP clan.

How do you balance a PvP encounter where anywhere from 1 to 2,000 players could join in at any moment? You don't. You change the zone type so the number of combatants is predictable and fair from the start.

What Is a Team Combat Zone?

A Team Combat Zone (TCZ) sits between singles and multi. The core rule is simple:

Any one group can be attacked by a maximum of 6 other players at a time.

Every Wilderness Team counts as one group. Every solo player counts as their own group. The cap of 6 applies regardless of how the opposing players are organised.

Rule	Singles	Team Combat Zone	Multi
Max attackers on one target	1	Up to 6	Unlimited
Solo player viable?	Yes	Yes	Against clans: No
Small team viable?	Partially	Yes - capped at 6v6	Against clans: No
Clan viable?	Partially	Can engage in parallel	Yes - unrestricted
Designed for	1v1 / PvM	Small groups (2-6)	Large clans only

How the 6-Player Cap Works

Every Wilderness Team counts as one group. Every solo player counts as their own group of one.
If a team of 6 attacks a solo player, 5 more players can still join in against the team of 6, but cannot attack the solo player. The solo is not ganked.
If a solo player attacks a team of 6, the solo player has used their one slot. No additional players can pile the team of 6 while that solo is engaging.
A team of 6 vs a team of 6: the cap is immediately reached as soon as both teams engage. No third party can join either side.
6 separate solo players could each attack one member of a team of 6. 6 individual groups fills the cap of 6.
Combatant enemy players are marked orange on the minimap and show an orange highlight as soon as any member of their team hits any member of yours.
Attack options for combatant enemies are prioritised at the top of the right-click menu to reduce misclick frustration.
Your team cannot attack NPCs while another team is actively targeting yours, preventing one member from boxing an extra enemy team member using an NPC.

Solo vs Team of 6

Fair

Solo uses 1 slot. 5 more can still contest the team of 6.

Team 6 vs Team 6

Capped

Cap immediately reached. No third parties can pile either team.

Clan vs Small Team

Protected

Clan can only send 6 players at once. Others must wait or find a different target.

The New Three-Zone System

The intention is for different content to be designed around each zone type, with appropriate activities matched to each combat format.

Singles

For solo PvM, solo PKing, and 1v1 content. Unchanged from today. The Wilderness entry zones and most single-way areas remain as they are.

Team Combat Zone

For small groups of 2-6. Wilderness bosses, the Rev Caves, and contested mid-Wilderness areas. No more 30v1 clanbangs on PvMers. The content these zones contain becomes viable for non-clan players.

Multi

Reserved for content specifically designed for large clan warfare. Deep Wilderness clan areas, the Forinthry Castle zone, and eventually Wilderness Expansion 2.0 territory beyond the Bridge of Fate.

Visual Zone Indicators

The dividing lines between zone types must be visually obvious. Changed floor tile colours near every zone boundary. This has been commonly requested for years and becomes essential once a third zone type is added. Fairness requires that players always know exactly which zone they are in.

Starting Small - A Proof of Concept

A full restructure of multi and singles zones across the entire Wilderness is a significant undertaking, and it is reasonable for Jagex to want evidence it works before committing to that scope.

The right approach is to trial it in one isolated location first. Choose a single area, convert it to a Team Combat Zone, and observe what happens to player activity there.

Potential Proposed Trial Locations

I'm open to ideas for where we might test the concept first. It's important to note that Team Combat Zones on its own will not increase activity, because it also depends on the reward incentive of the area.

Scorpio comes to mind. It's not a place many people really go to, so it could do with some kind of drop buff, along with testing this out.

Or a portion of the Rev Caves could be made into Team Combat Zones, in the more dangerous, deeper level areas.

I would avoid Wilderness Bosses for this, because they already see a lot of multi and clan activity.

If activity increases and feedback is positive, that's a good sign to consider expanding Team Combat Zones to more areas of the Wilderness.

If it needs adjustment, the change is contained to one area.

If it outright just doesn't seem to work, then it's much easier to remove from the game in retrospect when it's isolated to one spot.

However, we'd have to be sure that it's the Team Combat Zone we don't like and not a different problem like poor reward incentive of the content in the area or some other kind of design flaw.

Important: The upper-right Wilderness, currently the most actively used area by Wilderness clans, should remain multi for now. TCZs are not about removing clan content. They are about adding content that works without clans.

Why This Helps Jagex

Solves an unsolvable balancing problem. It is impossible to balance content for both 1 player and 2,000 players simultaneously. Team Combat Zones give Jagex a predictable player count to design around.
Unlocks new content design space. Jagex can now design Wilderness content for groups of 2-6 without it being immediately trivialised by clans. A category of content that has never viably existed in the Wilderness before.
Mostly background code. No new art assets, no new loot tables, no new areas of the map, no weapon or armour stat changes required. The dev cost is primarily code. Likely far lower than a new boss or Wilderness area.
Unpolled adjustments post-release. Like Sailing or raids balancing, Jagex can fine-tune the specific cap numbers and zone boundaries after release without needing a new poll for each tweak.
Turning a problem into gameplay. Clans "protecting" areas and crashing other players is currently an uncontrolled annoyance. TCZs create a structured framework where that same behaviour has rules, consequences, and counterplay.