What to check when co-op battles slow down
In Idle King: Loot Together, check for the November 18 update, which PcZ Games says improved multiplayer battle performance. If everyone is updated and can join, compare one familiar encounter solo and in a small co-op group to narrow down the slowdown.
Full Steam release unless a source specifies the demo. Evidence checked . Guide updated .
Steps
- Establish that the issue starts after everyone enters a battle successfully. If someone never reaches the battle, start with the version and join checks.
- Use the same hero and a familiar stage for a short solo run. Note when the slowdown starts and whether it goes away between fights.
- Try the equivalent encounter with a friend on the same version. Record whether both clients see the problem and whether it begins at the same point. Include those details and the build in a developer report if it persists.
How to tell it worked
You can tell whether the slowdown is present in solo play, appears only in a multiplayer battle, or affects one player.
If you are still stuck
The performance note does not promise a particular frame rate or fix for every stall. A repeatable example from the current build is more useful than assuming the patch should solve every similar symptom.
Record the moment slowing begins
Ask each participant whether the game slows before they join, while the expected stage loads or after fighting begins. The November 18 patch mentions improved multiplayer battle performance. A failed join raises the version prerequisite first. A battle that starts normally and then visibly slows down is a stronger sample for testing the change the publisher described.
Choose a familiar encounter the character can usually clear. Record the selected stage, difficulty, character and game version. Finish a short solo test and note where the action pauses or catches up. Then run the same encounter with another player on a matching build. Ask both people when they first observe the slowdown. If only one client sees it, note which client and when the others still see normal output.
Compare the important difference without changing the build
Use the same stage and equipment through the comparison. If several players change gear and choose a different fight at the same time, the result is no longer useful for locating the slowdown. Observe whether the behavior repeats at a specific part of the battle. A regular delay before the same action gives a better example for a report than a general impression of lower speed.
If solo runs slow down as well, keep the timing for both modes. If the same fight is stable solo and slows after all participants join, record the group composition and whether that result repeats with a small group. If one participant never reaches the fight, keep that version or join result separate so it does not get mistaken for a battle performance observation.
Give the developer a repeatable scene if the issue persists
Record the updated build, a reproducible stage, whether the problem happened alone or with others and the moment it starts. Include which participants observed it. The publisher's note reports an improvement and sets no expected frame rate. A specific post-update comparison is more useful than relying on that note as a promise about your own session. Keep the working test and the failing test together so you can compare them again after another update.
Retest with the same participants after an update
Keep one reproducible encounter in your notes. The next time both clients update, you can run that same encounter and compare the first visible slowdown. If the symptom moved to a different part of the battle, record the new moment separately.