How to appeal an incorrect multiplayer ban

In Idle King: Loot Together, check whether the game shows a ban or a connection error. If it is a ban and you think it was issued in error, PcZ Games lists an appeal email in its official Anti-Cheat Update.

Full Steam release unless a source specifies the demo. Evidence checked . Guide updated .

Steps

  1. Copy the exact notice, note the date and time, and record which part of multiplayer was affected. The wording helps distinguish a moderation issue from a version mismatch.
  2. Open the official Anti-Cheat Update and use the contact address listed there. Explain what happened and include only the account or session details the official contact needs to find the case.
  3. Wait for the developer’s response. Keep your exact notice available if they ask for more information about the session.

How to tell it worked

You sent the relevant facts once to the contact published by the developer and kept a record of the appeal.

If you are still stuck

If there is no ban notice and the error refers to a version mismatch, start with the version checks instead. The official note does not specify the appeal response time or promise an outcome.

Verify which notice blocks multiplayer

Copy the exact message and where it appeared. A notice about incompatible game versions points to a different problem than a ban under PcZ Games' published Anti-Cheat Update. Record the version you are running and the part of the game you were trying to use. If you only have a general failure to join, check the message and the matching-version guide before treating it as a moderation decision.

If the game does report a ban, keep the notification. Note the approximate time with the time zone and what you were doing just before it appeared. Describe what you observed separately from what you think caused it. A sequence such as opening a multiplayer session and receiving the displayed notice gives the developer a specific event. Speculation about rules the announcement does not describe will rarely help identify that event.

Use the developer's listed appeal channel

Open the linked Anti-Cheat Update and copy the current appeal contact from the publisher's announcement. Explain that you believe the restriction was applied in error. Provide the game or account identifier the developer needs to find the case, the exact notice, the build and the time. Keep credentials and unrelated account data out of the message. If a screenshot helps explain the problem, include only the relevant game screen and remove unrelated private details.

Keep a copy of what you sent. The published announcement provides a contact for mistaken bans, with no response time or guaranteed result. If the developer asks a follow-up question, use the original details and reply in the same conversation. Sending copies to other addresses can separate the original evidence from the request.

Check the outcome you actually receive

When you get a response, read what it says about the restriction before testing multiplayer again. If you retry, note what the game itself displays. A support reply and a successful return to the expected session are distinct observations. If the ban notice is absent and a matching-version error appears instead, handle the new error using the version checks. Maintain the original screenshot or message so you can describe the change accurately.

Use the first affected event as the reference

If you discover the restriction after switching devices or reconnecting, include the time you first saw it and the last session where multiplayer worked. Those are two observations. They make it easier to locate the affected session without asserting exactly when the restriction began.

Related tasks

Sources