When the host leaves, the match doesn't. The best-connected player takes over, everyone reconnects, and the world comes back exactly as it was — same positions, same inventories, same camera angles.

| 🧩 Blueprint Accessible | 🚀 Optimized | 🤝 Full Support |

🎥Video Presentation: >>> HERE <<<

🛠️Support (Discord): >>> HERE <<<

📄Documentation: >>> HERE <<<

👑 The problem it solves 👑

In a listen-server game, the host is a player like any other — and when that player rage-quits, crashes, or simply loses Wi-Fi, everyone else is dropped back to the main menu. Hours of co-op progress, gone because one person closed a laptop.

Host Migration X keeps the session alive. It continuously records the state of your world, works out who would make the best host, and when the current one disappears it promotes the successor, brings everybody across, and puts the world back together. Players see a loading screen for a few seconds; they do not see a disconnect.

✅Features:

• Ping-based election

• Directed handover

• State that survives

• References that survive

• Nothing visibly respawns

• Built for large worlds

• A migration screen you design

• Steam, EOS or your own
  

___________

Keep co-op sessions alive when the host quits or crashes. The best-connected player takes over, everyone reconnects, and the world comes back exactly as it was.

Before you buy

_______________________

Listen-server sessions. The plugin promotes a player to host. It is not for dedicated-server games, where migration is not the problem being solved.

Online subsystems need your session code. Direct IP works immediately. With Steam or EOS, the plugin tells your game when to create and find a session and travels the address you hand back — the platform calls stay in your project, where your lobby logic already lives.

Soft object pointers to runtime-spawned actors are not carried across. Hard references are.