When a match is interrupted by a technical problem or disputed behaviour, the most useful message is often the calmest one. A clear report helps an organiser understand what happened, locate the relevant evidence and explain the next step. A rushed accusation can make the same situation harder to resolve, even if your concern is legitimate.
For a MegerSkill-related community session, use the reporting route in the current event instructions. This guide is a method for preparing information; it does not promise an outcome, a response time or a particular disciplinary process.
Deal with the immediate situation first
If play is still running, follow the approved pause or contact procedure. Do not invent a new rule because you feel a pause should be allowed. Keep the urgent message factual and short: who needs help, what stopped working and whether the problem is continuing. Avoid filling the main channel with several versions of the same complaint.
If the issue involves immediate personal safety, prioritise safety and the appropriate support route rather than trying to finish a competition.
Build a small factual timeline
Record the event name, match or session identifier if available, approximate time and the sequence of events. Separate what you directly observed from what you inferred. “The client disconnected at this point” is an observation. “The other team caused it” is a different claim that requires evidence.
A practical structure is: expected procedure, observed problem, effect on the session, action already taken. This lets someone new to the situation follow the report without first reading a long argument.
Preserve relevant evidence carefully
Keep the original clip, screenshot or log that the organiser asks for. Include enough surrounding context to make it understandable. A tiny crop might hide the timing or the message that explains the event. Do not edit material to make it appear more certain than it is, and do not repeatedly repost someone’s personal details.
Before sending a screenshot, check for private chats, email addresses, account information or recovery codes in the background. Use the official private reporting route when sensitive information is genuinely required.
Ask for a decision, not a public pile-on
State what you need clarified: whether play should resume, how a result should be recorded or whether an alleged conduct issue should be reviewed. You can be firm without threatening the organiser or encouraging people to target another participant. Public speculation is not a substitute for the event’s process.
General resources such as the ESIC Integrity Program demonstrate that conduct and integrity have formal treatment in parts of esports. They do not make every community disagreement an ESIC case. Use the rules and authority that apply to your actual event.
Keep a concise report template
- Session: the official event or match reference.
- When: time and time zone, or the relevant round.
- Observed: a neutral description of the incident.
- Evidence: original material through the approved channel.
- Request: the specific clarification or review needed.
For example, “Our player disconnected before the restart instruction, and we need to confirm which procedure applies” is easier to act on than “the whole match was unfair.” Keep a copy of what you submitted, allow the stated process to work and use any available review or appeal route respectfully. A good report protects the usefulness of your concern by making it understandable.





Join the conversation.
Ask a question, share what worked, or add your take.
No comments yet. Bring a useful question or a tip from your own experience.