Six characters.
One designed formation.

A six-character Path of Exile 2 party is not just a larger version of a two-character couch co-op setup. It changes the design problem. You are no longer asking, “What should the second character do?” You are deciding how six separate builds share damage, defence, control, loot, movement and encounter responsibilities while one person remains the operator.

The 6P client and player layout

The conceptual six-player layout uses three client windows with two local player positions in each client: P1/P2, P3/P4 and P5/P6. The controller system sits above that layout and maintains an operator-facing view of which player has direct focus, which followers are linked and which supported actions are routed to each role.

This is a product topology, not a statement that every possible client count or multi-client configuration is permitted by the game publisher. Players should review current publisher rules and the current Findigo documentation before using any multi-client setup.

Give every player slot one obvious job

Six-player parties become difficult when every character is built as a generalist. The operator then has six sets of overlapping skills and no clear answer to which character should receive direct attention. A better design gives every slot one dominant purpose.

• P1 lead: route choice, ordinary clear and encounter initiation.
• P2 partner: close-range damage, bossing layer or defensive body.
• P3 amplifier: buffs, debuffs, shocks, exposure, curses or auras.
• P4 control: slows, freezes, stuns, knockback, distraction or area denial.
• P5 utility: pickup work, recovery, companions or a map-loop task.
• P6 specialist: rarity, culling, an unusual build interaction or whichever job is still missing.

The exact build choices will change between leagues and patches. The important part is the operating logic: when something goes wrong, you should know which player slot needs focus and why.

How one controller can remain understandable

A controller has limited buttons, but it also has a major advantage: it creates one consistent physical interface. MultiPilot can preserve that interface while changing the current target of direct control. The normal loop is lead, follow, focus, return.

1. Play P1 normally and establish the route.
2. Allow configured followers to maintain formation and contribute selected actions.
3. Move Smart Focus to a character that needs direct movement, inventory, menu or mechanic control.
4. Resolve the task, return focus to the lead and resume the formation.

This avoids the worst version of multibox play: repeatedly clicking through several windows, guessing which client has input and losing the party while trying to recover one character.

Movement is the real six-player difficulty

Damage numbers are easy to imagine. Keeping six characters close enough to contribute is the harder engineering problem. Terrain, collision, combat animation, load timing and transitions all create small gaps. Those gaps compound across a full party.

Smart Follow, breadcrumb-style route guidance, stopping distance, sprint catch-up and explicit transition handling are therefore more important than they first appear. A perfect build is not useful if two characters are one screen behind, another missed a stair and the pickup role is trapped on the wrong side of a doorway.

Design combat around complementary actions

Six builds give you room to separate jobs that would normally be combined. One character can apply a debuff. Another can exploit it. A third can improve survival. A fourth can control space. P5 and P6 can add rarity, utility, companions, culling or another damage type.

Selected routing matters here. The goal is not to indiscriminately send every button to every player. The goal is to define which repeated or supported actions belong to which characters, while retaining direct focus for mechanics and exceptions.

Plan the loot role before the first map

Full-party farming creates more collection decisions, not fewer. Decide which character should collect which visible item categories, how inventory limits will be handled and when the party will stop to stash. A pickup-oriented player slot can reduce how often the lead build abandons combat flow.

MultiPilot’s controller AutoLoot, per-player assignment and related Findigo inventory tools are intended to turn loot into an explicit workflow. They do not automatically transfer items between accounts or replace every inventory decision.

Hardware planning for three visible clients

Three client windows can place sustained load on CPU scheduling, system memory, VRAM and storage. Exact requirements depend on resolution, graphical settings, party effects, league content and the game build. Plan around stable frame pacing rather than one impressive peak frame-rate number.

• Use an SSD with adequate free space for every official client installation.
• Cap frame rates deliberately instead of allowing background clients to consume unlimited GPU time.
• Reduce visual load on secondary clients where practical.
• Watch VRAM use at your real desktop resolution, especially on ultrawide monitors.
• Test transitions, boss arenas and effect-heavy encounters rather than only an empty hideout.

Start smaller, then add roles

The fastest way to make a six-player setup frustrating is to configure all six characters at once. Begin with the lead and one follower. Confirm pairing, focus, movement and recovery. Add P3/P4, then add P5/P6 after the first four roles are predictable. This makes it much easier to distinguish a build problem from a controller, client or configuration problem.

Common questions