MPL Malaysia Season 18 · quick answers
Who can still reach the top six?
56 of 56 series played; results last checked . These answers update automatically after each result; the season tiebreak rule is provisional. How the numbers work
Can Bigetron MY by VIT qualify? 6–8 · Secure*
Bigetron MY by VIT finishes in the top 6 in every remaining result under the provisional series-win and game-difference ranking rule. Current record: 6–8 with 0 series left.
Can Team Flash qualify? 5–9 · Secure*
Team Flash finishes in the top 6 in every remaining result under the provisional series-win and game-difference ranking rule. Current record: 5–9 with 0 series left.
Can AC Esports qualify? 4–10 · Out*
AC Esports cannot reach the top 6 under the provisional series-win and game-difference ranking rule. Current record: 4–10 with 0 series left.
Can RRQ Tora qualify? 3–11 · Out*
RRQ Tora cannot reach the top 6 under the provisional series-win and game-difference ranking rule. Current record: 3–11 with 0 series left.
* Under the provisional ranking assumptions. Open the playoff routes below for the exact score dependencies.
MPL Malaysia · Season 18 · Leg 2
Road to playoffs
Eight teams. Top six qualify.
Top 6
Playoff qualification
Roster adjustments: off · Percentages use team records
Updates automatically from the official MPL MY schedule · last checked 18 Oct, 20:36 MYT. Forecasts are estimates; season tiebreak rules remain provisional.
Season rules awaiting confirmation
Series wins → game difference. Qualification labels depend on these provisional rules.
The race
League standings
Both legs counted · select a team to analyze
| Rank | Team | Series W–L | Leg 2 | Game Δ | Left | Top 6 estimate | vs W7 |
|---|---|---|---|---|---|---|---|
| 1 | 11–3 | 5–2 | +16 | 0 | >99.9% | 0.0pp | |
| 2 | 10–4 | 5–2 | +11 | 0 | >99.9% | 0.0pp | |
| 3 | 10–4 | 5–2 | +8 | 0 | >99.9% | 0.0pp | |
| 4 | 7–7 | 3–4 | 0 | 0 | >99.9% | +0.0pp | |
| 5 | 6–8 | 3–4 | -2 | 0 | >99.9% | +0.0pp | |
| 6 | 5–9 | 2–5 | -6 | 0 | >99.9% | +0.5pp | |
| 7 | 4–10 | 3–4 | -14 | 0 | <0.1% | 0.0pp | |
| 8 | 3–11 | 2–5 | -13 | 0 | <0.1% | -0.5pp |
Estimates use 5,000 simulated seasons. A very high forecast is distinct from a secure mathematical path. Movement compares with a reconstruction after the previous week.
Kelayakan playoff
How can
RRQ reach the top 6?
Meet every condition in one row.
RRQ: no playoff route under these rules.
All scenarios
Choose exact wins. Meet both rivals’ conditions.
All outcomes checked
0 scenarios
No secure route with 0 more wins.
+ = at least · GD = maps won − lost · Chances overlap
Scenario rules
Select exactly this many remaining series wins. Both rivals must meet their loss totals. If tied on wins, compare each rival’s final GD with RRQ’s. More losses remove that tie condition.
Secure mode requires rivals strictly below RRQ. Include tiebreaks allows equal final scores; a cutoff tie does not guarantee qualification. Loss counts include matches against RRQ.
Chance is the likelihood of exactly the selected wins and both rivals finishing below the team (or tied in Include tiebreaks). It includes all matching score combinations, rather than only the example. Rows overlap.
Every group has a legal full completion. Groups overlap and their count is not a probability. All outcomes are checked under the configured scoring rules. Scores show one example; Try applies it to the simulator.
Detailed simulator · edit scores and compare percentages
What if?
Scenario lab · Kelayakan playoff
Test a result and compare the effect on every team. Combine several matches to explore the results needed for a top-six finish.
Applies to 0 pending series. Replaces this team's assumptions and keeps other scenario results.
Choose a result above to see percentage changes and qualification routes. With no assumptions, both columns match.
| Team | Recorded results | Your scenario | Change | Kelayakan · before → after | Wins to secure · before → after |
|---|---|---|---|---|---|
| >99.9% | >99.9% | 0.0 pp | SecureSecure | Already secureAlready secure | |
| >99.9% | >99.9% | 0.0 pp | SecureSecure | Already secureAlready secure | |
| >99.9% | >99.9% | 0.0 pp | SecureSecure | Already secureAlready secure | |
| >99.9% | >99.9% | 0.0 pp | SecureSecure | Already secureAlready secure | |
| >99.9% | >99.9% | 0.0 pp | SecureSecure | Already secureAlready secure | |
| >99.9% | >99.9% | 0.0 pp | SecureSecure | Already secureAlready secure | |
| <0.1% | <0.1% | 0.0 pp | No qualifying routeNo qualifying route | No qualifying routeNo qualifying route | |
| <0.1% | <0.1% | 0.0 pp | No qualifying routeNo qualifying route | No qualifying routeNo qualifying route |
Percentages estimate top-six qualification; changes are percentage points against recorded results at the selected cutoff. Qualification and win guarantees use series-win bounds with adverse ties under the stated scoring assumption. A 99.9% estimate does not prove a secure berth. Small percentage changes may be simulation noise.
Team pathway
RRQ Tora
Top 6 estimate
<0.1%
Attainable rank bounds
#8
Path to a secure berth
Series wins alone cannot guarantee a berth in these bounds. Rival results or the eventual tiebreak resolution can still matter.
A possible route
Even winning every remaining series cannot put this team inside the top six.
Rank bounds use series wins only: favorable ties for the best case, unfavorable ties for the worst. They are wider than forecasts using game difference.
Estimated final position
Remaining opponents (0)
No remaining regular-season matches.
Rival watch
Teams closest to the bubble
Other teams whose forecasts are closest to 50%. Their results can change the race; use scenarios to test a dependency.
Fixture scenarios
The second leg
Set pending scores to see the effect on every team. Only complete BO3 results can be tested.
Week 511 Sept7/7 recorded
11 Sept, 17:00 MYT · Leg 2
11 Sept, 20:15 MYT · Leg 2
12 Sept, 14:30 MYT · Leg 2
12 Sept, 17:00 MYT · Leg 2
12 Sept, 20:15 MYT · Leg 2
13 Sept, 14:30 MYT · Leg 2
13 Sept, 17:00 MYT · Leg 2
Week 618 Sept7/7 recorded
18 Sept, 17:00 MYT · Leg 2
18 Sept, 20:15 MYT · Leg 2
19 Sept, 14:30 MYT · Leg 2
19 Sept, 17:00 MYT · Leg 2
19 Sept, 20:15 MYT · Leg 2
20 Sept, 14:30 MYT · Leg 2
20 Sept, 17:00 MYT · Leg 2
Week 78 Oct7/7 recorded
8 Oct, 17:00 MYT · Leg 2
8 Oct, 20:15 MYT · Leg 2
9 Oct, 17:00 MYT · Leg 2
9 Oct, 20:15 MYT · Leg 2
11 Oct, 14:30 MYT · Leg 2
11 Oct, 17:00 MYT · Leg 2
11 Oct, 20:15 MYT · Leg 2
Week 816 Oct7/7 recorded
16 Oct, 17:00 MYT · Leg 2
16 Oct, 20:15 MYT · Leg 2
17 Oct, 14:30 MYT · Leg 2
17 Oct, 17:00 MYT · Leg 2
17 Oct, 20:15 MYT · Leg 2
18 Oct, 14:30 MYT · Leg 2
18 Oct, 17:00 MYT · Leg 2
Asian Games break: 21 Sep–4 Oct. Week 7 includes Thursday 8 Oct; fixtures follow the official schedule.
Round report · recorded results
What changed in Week 8
Completed week · compared with W7
Largest estimated gain
Team Flash
Largest estimated drop
RRQ Tora
Changes include both recorded results and refitted team strengths. Small shifts may be simulation noise.
Regular-season fixtures complete
Forecast method and assumptions
Recorded snapshot: 18 Oct, 20:36 MYT. This view uses a dated capture and does not automatically update. Missing scores remain pending.
Six teams qualify. Forecasts rank series wins, then game difference; unresolved ties share places. The detailed season tiebreak rules are unconfirmed. Qualification guarantees apply only under these scoring assumptions.
The strength model combines opponent-adjusted season map strength with the pair’s head-to-head map record. Direct meetings are excluded from the season prior, then blended back with an eight-map prior weight. BO3 probabilities assume independent games with fixed matchup strength. Scenario chances sum all matching fixture outcomes exactly under this model. The equal-strength baseline gives both teams a 50% map chance; it describes the fixture structure rather than predicting team ability.
Model season-strength-h2h-prior8-v2; seed 1806. Typical maximum 95% sampling margin is ±1.4 percentage points. This measures simulation noise, not model accuracy. The model has not yet been calibrated on historical seasons. Draft, roster, patch, and injury effects are not included.
Historical weeks are reconstructed from this capture's results, not live snapshots saved at that time. Only results at or before the selected week train its model; later corrections can change a reconstructed history. Scenario scores never train team strengths.