Maokai_UniqueTrait Sentinel▲ 0.31

Level 9

Placement

4.00

Top 4

53%

Contest.

Full composition

Item combos — main carries (top 10)

Sentinel

Combo	Avg placement
	7.00
	1.00
	4.00
	5.00

Maokai

Combo	Avg placement
	3.00
	1.00
	3.50
	6.00

Taric

Combo	Avg placement
	2.60
	5.00

Seen on the TOP ladders

KR 빨리지기#KR1 GRANDMASTER 222 LP 1

BR JuanGhurkas#Doom GRANDMASTER 226 LP 7

Matchups vs

vs Summoner Zyra 21 encounters 81%

vs Defender Cassiopeia 19 encounters 53%

vs Fae Tristana 16 encounters 38%

vs Solar Kayle 15 encounters 60%

vs Summoner Soraka 13 encounters 92%

vs Battlemage Sivir 13 encounters 31%

vs Riftbeast Cinderling 11 encounters 73%

vs Greenfather Ezreal 11 encounters 45%

vs Caustic Kog'Maw 9 encounters 56%

vs Solar Akali 8 encounters 75%

vs Executioner Soraka 6 encounters 33%

vs FloraFatalis Soraka 6 encounters 100%

vs Executioner Zyra 5 encounters 20%

vs Blossom Ahri 5 encounters 40%

vs Generic 5 encounters 40%

Board variants

Baseline

1.00 avg placement

→

5.33 avg placement

→

3.67 avg placement

Real versions of this comp's final board: which exact group of champions shows up together, how often, and the average placement of those games. Not a game-by-game history (Riot only exposes the end-of-game board, never how it got there): a comparison of builds, not a timeline.

Board add-ons (9th/10th unit)

Base board — 9 units Not enough games with exactly this board, no add-ons

Not enough games with an extra unit for a reliable signal.

The main board above stops at 9 units: reaching a 10th slot needs level 10, which on its own already correlates strongly with a good placement. Below, the average placement of games with this base board plus one or two extra units, shown as a correlation to interpret, not a causal recommendation.

Augment path

Data unavailable. Riot's API doesn't populate the augments field for this set — verified directly on the collected sample (the "augments" field doesn't even appear in the response, across 23,000+ real participants checked). The field does exist in the official schema and worked on older sets, so this probably isn't permanent — this section will activate automatically as soon as it fills in again.