MultiPilot maps a complete party across explicit client pairs.

MultiPilot keeps each configured client as an ordinary visible PoE 2 window and assigns one couch co-op pair to each. Two copies of the same client workflow are not treated as interchangeable.

The selected topology controls which client profiles launch, which player routes are paired and which unused outputs remain neutral.

Protected pairing creates only the required player slots and verifies independent movement before normal play. Smart Focus hands direct control to a chosen character, while follow and action routing handle only what the user configures.

If two characters move together during an independent movement check, MultiPilot treats it as a pairing problem instead of accepting the result.

MultiPilot stages a separate PoE 2 configuration profile immediately before each configured client launches. Client 1 can use a clarity-first filter and higher foreground target while Client 2 and Client 3 use lighter graphics, quieter audio or different item filters.

Automatic saving attributes a confident in-game config change to the foreground client. Unknown writes are skipped instead of risking another profile.

• Separate FPS and graphics choices for Client 1–3.
• Separate resolution and window settings.
• Separate audio, UI and gameplay options.
• Separate item-filter selection without moving or deleting filter files.

1. 01

   Prepare Client 1

   Stage its profile, launch the configured client and identify the game window.

2. 02

   Prepare Client 2

   Stage the second profile only after Client 1 reaches its reliable ready point.

3. 03

   Prepare Client 3 when selected

   The local 5P/6P workflow repeats the guarded sequence for the third profile.

4. 04

   Pair the active slots

   Certify P1/P2, P3/P4 and, when selected, P5/P6 in client order.

5. 05

   Verify focus and movement

   Every active player must move independently before play continues.

The point is not merely having more game windows. It is creating explicit player slots for a carry, amplifier, controller, utility specialist, recovery role and boss specialist while keeping the group in practical proximity.

Choose the smallest topology that fits the build plan. MultiPilot keeps unused slots disconnected and neutral instead of forcing a full 6P layout.

MultiPilot keeps the topology explicit: 2P–4P use Client 1 and Client 2 as configured, while 5P/6P add Client 3 for P5/P6.

Unused player slots remain disconnected and neutral, and pairing must verify every active route before normal play.

• Choose 2P, 3P, 4P, 5P or 6P before launch.
• Keep every active client visible and identifiable.
• Keep inactive outputs disconnected and neutral.
• Use protected player pairing and movement verification.