Is a bad KDA reportable in League of Legends?

No. A bad score, losing lane or making mistakes does not establish intentional misconduct. Report specific observable behaviour, not the scoreboard.

Is an off-meta champion or role reportable?

Not by itself. An unusual pick is different from a stated or observable intent to sabotage the match.

Should I ask other players to report someone?

No. Submit your own good-faith report and let Riot review the available evidence. Do not retaliate, argue or organise mass reporting.

Arrr, good-faith reporting

Report behaviour, nay th' scoreboard

A useful report gives Riot a short, factual description o' something ye observed. It does nay need a courtroom argument, a diagnosis o' motive or a campaign in chat.

Inspect th' report Arrr, use a template

Use League's built-in report first aboard.Nay external recording be normally required.

Set sail wit' one query

What did ye actually observe?

A report should point to conduct Riot can inspect. Pick th' course that best matches what happened afore writing anything.

Arrr, specific conduct

Arrr, i saw or received something reportable

Note th' clearest action, approximate time and whether it repeated.

Loadout th' report

Arrr, score, pick or mistake only

I am frustrated, but only saw a difficult battle

A bad KDA, unusual role, missed trick or disputed loadout be nay enough by itself.

Inspect what be nay enough

Protect yer space

I need th' contact to stop now

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

See th' next aboard steps

Set sail wit' th' conduct

Arrr, a useful report describes what happened

Pick th' closest category available in th' present client, then describe th' clearest observable tale. Riot reviews th' behaviour and available evidence.

Communication

Arrr, harassment, hate or threats

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

Useful: Arrr, channel, approximate time and a short paraphrase.
Arrr, leave out: Yer own reply, insults and demands fer a specific penalty.

Participation

Arrr, leaving or remaining AFK

State when participation stopped and whether th' sailor returned. Do nay guess why they cast adrift.

Useful: Last aboard active time, visible state and return time.
Arrr, leave out: Arrr, claims about their internet, hardware or motive.

Clash conduct

Arrr, repeated sabotage or deliberate feeding

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

Useful: Repeated course, action and timestamps.
Arrr, leave out: KDA as th' entire report or anger about an unusual pick.

Integrity

Arrr, cheating or scripting concern

Record th' unusual behaviour ye saw without presenting suspicion as confirmed fact.

Useful: Th' exact movement, timing or repeated interaction.
Arrr, leave out: “Definitely cheating” when ye cannae verify th' cause.

Arrr, turn a reaction into evidence

Loadout th' report from three facts

Th' shortest useful report most often answers when, what and Arrr, whether it repeated. Riot already has clash and chat systems; yer note helps point inspect toward th' relevant behaviour.

1
Arrr, locate itWhen?
Use a clash time, champion-pick phase, or post-battle chat.
2
Arrr, describe itArrr, what happened?
Write th' visible action or a short relevant paraphrase.
3
Arrr, give contextArrr, once or repeated?
Stow another time only when it shows a meaningful pattern.

Arrr, report noteClash conduct

WHENArrr, 12:40, 14:05 and 15:20 WHATWalked into th' foe turret without attacking or retreating CONTEXTArrr, repeated after returning to base

At 12:40, 14:05 and 15:20, th' sailor repeatedly walked into th' foe turret without attacking or attempting to leave. Please inspect th' repeated actions; this report be nay based on KDA alone.

Arrr, avoid false certainty

These be nay enough by themselves

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

A bad KDA or lost courseSailors can have difficult matches and still be trying.

Arrr, an off-meta pickChampion and role choice be nay proof o' sabotage.

A loadout ye disagree wit'Yer preferred gear order be nay a conduct rule.

Missed tricks or mistakesArrr, mechanical errors happen at every level.

Nay voting to surrenderAnother sailor can choose to continue playing.

Arrr, one brief disconnectReport th' observable absence only when it materially fits th' category; do nay invent a cause.

Arrr, ignoring a ping or callA ping communicates yer course. It does nay require a teammate to agree or follow it.

One perilous solo or turret playA failed kill, split push or attempt to damage a turret be nay sabotage by itself.

A common aboard disagreement

A teammate ignored me ping. Is that reportable?

Most often, no. Retreat, peril, assistance and prize pings share ship's intelligence; they do nay make one sailor th' commander o' th' crew. A teammate may miss th' ping, disagree, react late or make a poor decision.

Arrr, different call

They continued after yer retreat ping

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

Nay enough alone

Arrr, turret pressure

They attacked a turret wit' allied minions

That can be an ordinary push, plate attempt or trade fer pressure. Th' play may be perilous or unsuccessful without being deliberate sabotage.

Judge th' conduct, nay th' result

Arrr, communication conduct

Arrr, they used pings to harass or disrupt

Mute excessive pings first aboard. If th' pattern be abusive or deliberately disruptive, report th' repeated ping conduct rather than claiming they disobeyed ye.

Describe th' pattern

Arrr, one ignored ping followed by a death

A mistake or different decision. Do nay present yer ping as proof o' intent.

Most often do nay report

Repeated perilous plays without an admission

Keep judging what be observable. Repetition can add context, but ye still should nay invent motive from th' outcome alone.

Arrr, use caution

Arrr, repeated non-participation, deliberate deaths or an explicit admission

Describe th' exact actions, timing and relevant statement. Mention th' ping only as context, nay as th' offence.

Arrr, potentially reportable

Arrr, ping spam boundary

Repeated does nay automatically mean disruptive

Unfurl th' shipshape ping chart

Arrr, normal use

Arrr, urgent, useful or playful

A short cluster fer an immediate gank, retreat or prize; an updated call when th' situation changes; or occasional celebration and humour.

Arrr, potentially disruptive

Arrr, sustained frustration aimed at a teammate

Repeatedly targeting th' same teammate after a mistake, following them wit' unrelated pings, or continuing across th' clash to annoy, blame or harass.

Thirty-second inspect

Four checks afore submitting

Tick th' points yer report already covers. This be a writing aid, nay a decision from Riot.

1Arrr, i observed it myselfI am nay repeating a rumour or another sailor's accusation. 2I can describe th' actionTh' report says what happened instead o' guessing th' sailor's intent or identity. 3Arrr, i included useful timingA timestamp, phase or repeated pattern helps locate th' event. 4Arrr, i removed retaliationNay insults, threats, public naming or request fer a mass report.

0 o' 4 shipshapeKeep th' report factual and brief.

Write less, say more booty

Arrr, write a factual report

Pick th' closest starting point, replace every bracketed prompt and remove anything ye did nay personally observe. This editor stays in yer browser and does nay submit anything to VRC.LOL.

Edit yer reportKeep names out o' public posts. Submit through Riot's present report interface.

Arrr, local writing toolYer text remains in this browser tab. VRC.LOL does nay receive or store it.

Or copy to parchment a template directly

Arrr, general report

At approximately [time], [sailor] [observable action]. This happened [count] times after [brief context]. I am reporting th' behaviour, nay their champion choice or score.

Arrr, harassment or threats

During [champion pick / clash / post-battle], th' sailor sent [brief wording or paraphrase] toward [target]. It continued at approximately [times].

Arrr, aFK or leaving

Th' sailor stopped participating 'round [time] and remained [in base / cast adrift / stationary] until [time or clash end].

Arrr, repeated sabotage

At approximately [times], th' sailor repeatedly [observable action] after [brief context]. Please inspect th' repeated actions; this report be nay based on KDA alone.

Arrr, cheating concern

At approximately [time], I observed [specific unusual behaviour]. I cannae verify th' cause, so please inspect th' clash rather than treating this as a confirmed accusation.

Champion pick

During champion pick, th' sailor [specific threat / harassment / stated intent to sabotage]. I am reporting th' stated or observed conduct, nay th' picked champion or role.

Pick a template to copy to parchment it.

Belay th' loop

Report, protect yer space, move on

Do nay turn one report into another conflict.

1
Arrr, mute or block when needed
Use th' client controls to reduce further contact during or after th' clash.
2
Arrr, submit one accurate report
Pick th' closest category and include only yer clearest evidence.
3
Do nay organise retaliation
Do nay chase th' sailor on social media, publish their Riot ID or ask a harbour to mass report them.
4
Arrr, use Riot Support when appropriate
Follow Riot's present support process if th' client course be overboard or Support directs ye there.
Unfurl Riot Support

Arrr, official context

Arrr, riot's rules remain authoritative

VRC.LOL explains th' public material below. Riot sees evidence this chart cannae access and makes th' final enforcement decision.

Arrr, community PactPlay to claim victory, play fair and play wit' respect. Patch 26.1 report refitPresent category wording aligned wit' Riot's Community Pact. Arrr, behavioural systemsRiot's published tales o' feeding, sabotage, leaving and AFK conduct. Articles o' ServiceTh' binding user rules and enforcement framework.