NMRiH2 Crossplay Guide

Prepare every platform

The official store and release snapshot confirms cross-platform multiplayer across PC, PlayStation 5, and Xbox Series X|S. That is the platform boundary recorded on 2026-08-20, not a promise about an unlisted device, a future port, or permanent compatibility after later patches. Start with the current listing for every device in the party instead of extending the confirmed set by analogy.

Install the current game update on each device before rebuilding the group. Console players need the online multiplayer access shown by their regional store and account, while the Steam PC requirements list broadband internet. Keep the console access check, PC network requirement, game version, and crossplay setting separate so one missing prerequisite is not mislabeled as a server failure.

Use one comparison point for the whole squad. Have every player open the current in-game party surface, read the displayed build if one is available, and confirm the intended platform account is active. The source snapshot does not document one permanent menu path for all three platform families, so this guide does not invent button names or platform-specific invite steps.

Check the crossplay boundary

The launch-window issue list says the crossplay toggle was being adjusted to improve matchmaking time for players who disable it. That dated note makes the toggle a real diagnostic boundary: a same-platform-only pool can be smaller than the cross-platform pool. It does not prove that every long queue is caused by the toggle, and it does not convert a missing party member into a matchmaking problem.

For a mixed PC and console party, crossplay must remain enabled wherever the current client exposes the setting. For a same-platform test, the group may compare enabled and disabled states, but change only that one variable and rebuild the party after the change. If the current build no longer presents the setting in the same place, follow the label visible in that build rather than an old screenshot or an undocumented sequence.

Build the party deliberately

Choose one party leader and send invitations from the current in-game interface. Each invited player should be visible in the roster before the leader selects a mode or starts matchmaking. Crossplay availability and party formation are different stages: a platform can be eligible for crossplay while a specific invite, account, or roster state is still incomplete.

If a player disappears, stop at the party screen. Ask that player to return to the same surface, confirm the correct account and current client, and then recreate the group under the same leader. Repeatedly starting and canceling a queue adds another state change without proving whether the missing player ever joined the roster.

Separate invite, party, and queue failures

Use the earliest failing stage to choose the next guide. An invitation that never reaches the other account belongs to the matchmaking and invite checks. A player who accepts but does not appear in the roster calls for a clean party rebuild. A complete mixed-platform roster that cannot enter a match is the point to compare the crossplay toggle, region, and the dated server-status boundary.

Do not change console multiplayer access, the PC network path, party leadership, and crossplay at the same time. One controlled retry produces useful evidence; several simultaneous changes only show that something differed. Record the platform pair, whether every member was visible, the selected crossplay state, and the first error text.

Verify the crossplay result

After changing the toggle or rebuilding the party, enter one queue and wait for a clear result. Record which platforms joined successfully; that distinguishes a crossplay configuration issue from a wider server or account problem.

A successful check means the intended mixed-platform roster stayed together through the queue and reached the session. It does not certify every region, future patch, account combination, or platform service. This page is bounded to version 1.0.3.1 Armageddon and the official sources captured on 2026-08-20; compare newer official notes before treating a changed result as permanent support or permanent failure.