Multiplayer sessions in WARFRAME are hosted peer-to-peer (P2P), meaning a single person is selected by the game to be the host of a particular session. Any additional players who join that session will be connected to the host player's machine. Host migration is the consequence of a drop in connection from the host, forcing the game to choose another player in the same session to be the host instead. If a host migration is successful, the remaining players will continue the session, retaining rewards and progress made (to a certain extent). However, if a host migration fails, all players will be taken back to the Orbiter, potentially losing rewards gained in that session.
Players in Solo matchmaking will not experience host migration as they host the sessions themselves.
Items were dropped during your extraction and have been retrieved for you.
Diagnostic repairs are now underway, Ordis is certain this probably won't happen again.
These items have been delivered to your inventory.
(Attachments: Lost rewards)
Any picked-up Resources, Mods, and Ayatan Treasures and Affinity earned by equipment will be lost upon a failed host migration since these rewards are determined client-side, not server-side, which means that the game's servers cannot verify their existence, leading to the loss of these.
The host player will always be denoted by a "1" next to their name in the player list sidebar (default key to toggle Z ).
Rarely, host migrations would result in joining a completely different session from the one the player was currently in, across different missions types even.
“Ah, have you come to make a donation to my newest 'enterprise'...?”
Patch history is needed. Click here for instructions.
General stability changes towards Railjack missions when a Host migration occurs. This touches on issues related to Crewships not spawning after a Host migration, and crashing when a Crewship spawning triggers a Host migration.
Fixed progression stopping bug if a Host migration occurred after the first radiator has been exposed on a Pulse Turbine POI, and players then proceed to destroy the exposed radiators.
After the Host migration, both radiators would be visible and vulnerable, at which destroying both of them would leave the mission broken due to having nothing to destroy after hacking the second console for the second radiator.
Fixed script error with host migration after exiting Railjack.
Fixed Kuva Larvling not spawning Kuva Lich if downed before Host migration and captured after Host migration.