Machine issue reports

Share machine issues and check their current status together.

From a report to the next visitor’s decision

Record severity and details for a game machine and attach photos. Other visitors can react to reports to indicate whether the issue persists or has been fixed.

The user journey

Vote on an existing fault report, see another visitor oppose, then follow level-weighted voting through to final resolution.

Try the flow

The same feature components used in the service, with sample data. Inputs and verification results stay in this demo.

Press Fixed as a level 12 member. This demo compresses the real waiting period to 10 seconds; a level 3 visitor opposes after 5 seconds.

1 existing fault report · Your level: 12

Fault reportMajor issue

The left button is not responding.

Initial report

하루

October 1, 2026 12:00

How the experience works

The first fixed vote starts a round. Each member has one fixed or opposing vote per round, weighted by their level captured when voting. Score = fixed level total − opposing level total. Delays: 30+ → 15 minutes; 20–29 → 3 hours; 10–19 → 24 hours; 5–9 → 48 hours; 0–4 → 72 hours. A negative score or no fixed voters cancels the round. New votes may bring the deadline forward but cannot postpone it. The backend marks the report resolved when the deadline is reached.

Before you use it

Report only issues you have confirmed. Reporting and reacting require sign-in; submitting a report does not mean the machine has been repaired.

Where do I start?

Expand the game card in an arcade document and choose “Report issue.” Enter severity and details, then attach photos if needed.

Open the feature

Back to developer guide

Musecat

All About Arcades