Fix a multiplayer version mismatch
In Idle King: Loot Together, put everyone on matching versions before retrying the lobby. PcZ pinned a notice that multiplayer requires matching game versions. Start by checking the game each player is running and the update offered by their client.
Full Steam release unless a source specifies the demo. Evidence checked . Guide updated .
Steps
- Have each person exit the game and check which Steam product they launched. Compare the exact version shown in the current client. A team member using the demo is on a different release from the full game.
- Apply the available official updates and launch the intended product again, rather than testing an invite while one player is still running the previous build.
- Once everyone on the team can confirm matching versions, try a fresh multiplayer invitation. Verify the version on both ends if the result is unchanged.
- The developer’s note about an occasional Mac delay described demo updates. The same note said the full release would keep Windows and Mac synchronized. Verify exact current builds if you are troubleshooting a real mismatch across platforms.
How to tell it worked
All players report the same game version and can test joining the same session.
If you are still stuck
If the error persists with matching versions, save the exact message and platform pair. The pinned notice establishes a required condition and does not diagnose all possible connection errors.
Compare versions before testing a second invitation
Have each player close the running game. Ask them to check the Steam entry they launch and the actual version reported by the game when they reopen it. The developer's pinned notice requires matching versions for multiplayer. Two people can both say Steam is up to date while one player is still using a different release. Read the exact version on both sides before changing the lobby or replacing an invite.
If a Steam update is available, apply it and launch the intended product again. Read back the new version number. Ask the host to do the same. A useful comparison comes from the running clients after any update, because a download or download-complete message alone does not show what the open game is running.
Diagnose a cross-platform mismatch using current builds
The developer described an occasional lag between Mac and Windows in an older demo note. Keep that timing tied to the demo. The full-release plan said the versions would remain in sync. When diagnosing a current failure, record the actual platform and version each person is using. Look for an offered update on the lagging client and compare again once both have restarted. Use the version you can actually read as the prerequisite for the next test.
Retry one join after the versions agree
Have the same players try a fresh invitation on the agreed build. Record whether the joining player reaches the same lobby or stage. If another friend can enter and the original player still cannot, compare exact error messages and note which stage of the join fails. A request to join a party for which both clients report matching versions points to a case beyond that known version rule.
If the UI reports a ban rather than a version message, read the official appeal guidance instead of restarting the same invitation. If the join works and the fight later slows down, use a familiar short battle to test the performance issue. Keep the earlier versions and the exact warning available if you report the original problem. This helps distinguish a compatible build with a separate failure from a version mismatch.