VRC.LOL

Good-faith reporting

Report behaviour, not the scoreboard

A useful report gives Riot a short, factual description of something you observed. It does not need a courtroom argument, a diagnosis of motive or a campaign in chat.

Check the reportUse a template

Use League's built-in report first.No external recording is normally required.

Start with one question

What did you actually observe?

A report should point to conduct Riot can review. Choose the path that best matches what happened before writing anything.

Specific conduct

I saw or received something reportable

Note the clearest action, approximate time and whether it repeated.

Build the report
Score, pick or mistake only

I am frustrated, but only saw a difficult game

A bad KDA, unusual role, missed ability or disputed build is not enough by itself.

Check what is not enough
Protect your space

I need the contact to stop now

Mute or block first, make a brief note if useful and use Riot's built-in report.

See the next steps

An off-meta choice is not proof of sabotage.Report a threat, admission or repeated observable conduct, not the champion or lane alone.

Read the off-meta guide

Start with the conduct

A useful report describes what happened

Choose the closest category available in the current client, then describe the clearest observable example. Riot reviews the behaviour and available evidence.

Communication

Harassment, hate or threats

Briefly identify the language or conduct, who it targeted and whether it continued.

Useful
Channel, approximate time and a short paraphrase.
Leave out
Your own reply, insults and demands for a specific penalty.
Participation

Leaving or remaining AFK

State when participation stopped and whether the player returned. Do not guess why they disconnected.

Useful
Last active time, visible state and return time.
Leave out
Claims about their internet, hardware or motive.
Match conduct

Repeated sabotage or deliberate feeding

Describe repeated actions and timing. A poor score alone does not prove intent.

Useful
Repeated route, action and timestamps.
Leave out
KDA as the entire report or anger about an unusual pick.
Integrity

Cheating or scripting concern

Record the unusual behaviour you saw without presenting suspicion as confirmed fact.

Useful
The exact movement, timing or repeated interaction.
Leave out
“Definitely cheating” when you cannot verify the cause.

Turn a reaction into evidence

Build the report from three facts

The shortest useful report usually answers when, what and whether it repeated. Riot already has match and chat systems; your note helps point review toward the relevant behaviour.

  1. 1
    Locate itWhen?

    Use a match time, champion-select phase, or post-game chat.

  2. 2
    Describe itWhat happened?

    Write the visible action or a short relevant paraphrase.

  3. 3
    Give contextOnce or repeated?

    Add another time only when it shows a meaningful pattern.

Report noteMatch conduct
WHEN12:40, 14:05 and 15:20 WHATWalked into the enemy turret without attacking or retreating CONTEXTRepeated after returning to base
At 12:40, 14:05 and 15:20, the player repeatedly walked into the enemy turret without attacking or attempting to leave. Please review the repeated actions; this report is not based on KDA alone.
Reviewable and neutralNo diagnosis, abuse or requested punishment.

Avoid false certainty

These are not enough by themselves

Context can matter, but none of these facts alone establishes intentional misconduct.

A bad KDA or lost lanePlayers can have difficult matches and still be trying.
An off-meta pickChampion and role choice is not proof of sabotage.
A build you disagree withYour preferred item order is not a conduct rule.
Missed abilities or mistakesMechanical errors happen at every level.
Not voting to surrenderAnother player can choose to continue playing.
One brief disconnectReport the observable absence only when it materially fits the category; do not invent a cause.
Ignoring a ping or callA ping communicates your plan. It does not require a teammate to agree or follow it.
One risky solo or turret playA failed kill, split push or attempt to damage a turret is not sabotage by itself.

A common disagreement

A teammate ignored my ping. Is that reportable?

Usually, no. Retreat, danger, assistance and objective pings share information; they do not make one player the commander of the team. A teammate may miss the ping, disagree, react late or make a poor decision.

Different call

They continued after your retreat ping

Choosing a different play, attempting a solo kill or arriving late is normal gameplay disagreement unless clearer conduct shows otherwise.

Not enough alone
Turret pressure

They attacked a turret with allied minions

That can be an ordinary push, plate attempt or trade for pressure. The play may be risky or unsuccessful without being deliberate sabotage.

Judge the conduct, not the result
Communication conduct

They used pings to harass or disrupt

Mute excessive pings first. If the pattern is abusive or deliberately disruptive, report the repeated ping conduct rather than claiming they disobeyed you.

Describe the pattern
1
One ignored ping followed by a death

A mistake or different decision. Do not present your ping as proof of intent.

Usually do not report
2
Repeated risky plays without an admission

Keep judging what is observable. Repetition can add context, but you still should not invent motive from the outcome alone.

Use caution
3
Repeated non-participation, deliberate deaths or an explicit admission

Describe the exact actions, timing and relevant statement. Mention the ping only as context, not as the offence.

Potentially reportable

Ping spam boundary

Repeated does not automatically mean disruptive

Open the complete ping guide
Normal use

Urgent, useful or playful

A short cluster for an immediate gank, retreat or objective; an updated call when the situation changes; or occasional celebration and humour.

Potentially disruptive

Sustained frustration aimed at a teammate

Repeatedly targeting the same teammate after a mistake, following them with unrelated pings, or continuing across the match to annoy, blame or harass.

There is no public “X pings equals misconduct” rule.The client may rate-limit some ping types, but that technical limit is not the reporting verdict. Riot describes the target as extreme, sustained and clearly disruptive use, and Riot makes the final decision.

Thirty-second check

Four checks before submitting

Tick the points your report already covers. This is a writing aid, not a decision from Riot.

0 of 4 readyKeep the report factual and brief.

Write less, say more

Write a factual report

Choose the closest starting point, replace every bracketed prompt and remove anything you did not personally observe. This editor stays in your browser and does not submit anything to VRC.LOL.

171 characters

Local writing toolYour text remains in this browser tab. VRC.LOL does not receive or store it.

Or copy a template directly
General report
At approximately [time], [player] [observable action]. This happened [count] times after [brief context]. I am reporting the behaviour, not their champion choice or score.
Harassment or threats
During [champion select / match / post-game], the player sent [brief wording or paraphrase] toward [target]. It continued at approximately [times].
AFK or leaving
The player stopped participating around [time] and remained [in base / disconnected / stationary] until [time or match end].
Repeated sabotage
At approximately [times], the player repeatedly [observable action] after [brief context]. Please review the repeated actions; this report is not based on KDA alone.
Cheating concern
At approximately [time], I observed [specific unusual behaviour]. I cannot verify the cause, so please review the match rather than treating this as a confirmed accusation.
Champion select
During champion select, the player [specific threat / harassment / stated intent to sabotage]. I am reporting the stated or observed conduct, not the selected champion or role.

Choose a template to copy it.

Close the loop

Report, protect your space, move on

Do not turn one report into another conflict.

  1. 1
    Mute or block when needed

    Use the client controls to reduce further contact during or after the match.

  2. 2
    Submit one accurate report

    Pick the closest category and include only your clearest evidence.

  3. 3
    Do not organise retaliation

    Do not chase the player on social media, publish their Riot ID or ask a server to mass report them.

  4. 4
    Use Riot Support when appropriate

    Follow Riot's current support process if the client route is unavailable or Support directs you there.

    Open Riot Support

Official context

Riot's rules remain authoritative

VRC.LOL explains the public material below. Riot sees evidence this page cannot access and makes the final enforcement decision.

Community PactPlay to win, play fair and play with respect. Patch 26.1 report updateCurrent category wording aligned with Riot's Community Pact. Behavioural systemsRiot's published examples of feeding, sabotage, leaving and AFK conduct. Terms of ServiceThe binding user rules and enforcement framework.