Some co-op runs end up in a state the session cannot get itself out of. A boss that will not spawn even though everything before it is done. Progress that does not stick. One player seeing a different world to the other. A crash on load that repeats every time you come back to the same point.
This post is what to do about it.
The honest part first
Not all of these are our bug. Multiplayer adds plenty of ways to break things, but the game keeps its own state on the host’s machine, and once that state is wrong it follows the save rather than the session. You can rejoin, restart the server, rebuild the room, and land in the same broken spot, because the save is the thing that is broken.
That is why the fastest way out is usually to replace the save instead of retrying.
The Shrine saves
We keep a pack of saves for exactly this. One from every Shrine in the game, sorted by chapter, all captured in WukongMP co-op. Each save carries full progression up to that Shrine: quests, items and spells. The only thing missing is challenge completion rewards, which do not exist in co-op.
https://www.nexusmods.com/blackmythwukong/mods/1367
How to use it:
- Pick the Shrine closest to where you are stuck, ideally the one just before it.
- The room owner uploads it through the ReadyM launcher into the room. Only the room owner can do this.
- Nobody can be in game while the upload runs.
Then carry on from that Shrine.
Two checks before you replace anything
Update first. Run the latest launcher and SDK and try the broken thing once more. A fair number of stuck reports turn out to be something already fixed in a release the player had not taken yet.
Check the known issues. Every release lists them. If yours is on that list, you have your answer without doing anything else. ReadyM Release Notes | ReadyM Docs
If you want us to chase it
Replacing the save unblocks you, it does not tell us anything. If you have five minutes, open a thread in WukongMP Support with:
- Launcher and SDK version
- Game version and store (Steam, Epic, HeyBox)
- Which server: one of ours or self-hosted, and the region
- How many players were in the session, and whether all of them saw it
- Every time, or sometimes
- What you were doing in the ten minutes before it broke
- Your client log, and the server log too if you host
The last two are what turn a report into something a developer can act on. Strip tokens and passwords out of configs before you paste them.
One thing we will not do
Promise a fix date for this class of problem. Some of it is ours and gets fixed in a release. Some of it is the game’s own state and we work around it. When we know which one you hit, we will say so in your thread.