What the current report addresses
- A co-op time check after the game window is hidden or another screen is active.
- Team Survival rejections labelled “Inconsistent bosses”.
- A finished run being rejected after Save & Quit and resume.
- Clearer Rainbow Wing revive feedback.
The same report lists 146 permanent bans and says 18 runs rejected by co-op or save bugs were restored. Those are patch-note totals. They are not a promise that every older rejection, timeout or moderation decision will be rolled back.
Before you report the next rejection
- Confirm the visible client version. The final Oct 30 official endpoint reads v0.8.80; if the client still reads v0.8.79, record that mismatch.
- Write down the mode, account state, team size and whether the game window was hidden or backgrounded.
- Copy the exact rejection text, including capitalization and punctuation.
- Record whether the run was paused, saved, resumed or matched through a public room.
- Keep the UTC date and time, plus a screenshot or short recording if the result screen is still visible.
What not to infer
A rejection after the v0.8.79 fixes—or on the current v0.8.80 client—does not by itself prove cheating, and a patch note mentioning restored runs does not prove your account will be restored automatically. Avoid deleting the run record or changing accounts before you have captured the evidence.
Use the co-op guide for the pause and window checks, then return here with the exact error. The live game and its support route remain the authority for an individual account decision.
Source trail
Version check: the official version endpoint. Reported fixes and totals: the dated v0.8.79 patch notes. EarlyWiki does not promise score restoration or give moderation advice beyond preserving a reproducible record.