Game 3: Any Player Rampage?

• 01
  Price move

  Down 51pp over 24h

  Now 0¢; -10.0pp in the last hour.

• 02
  Active signal

  Momentum observation firing

  Probability moved down 50.9pp in 24h with 0.0× liquidity turnover and a tight spread.

• 03
  Active signal

  Resolution-risk observation firing

  Market has reached expiry. Watch the UMA dispute window.

Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.

This market is about whether any player achieves a Rampage during Game 3. In Dota 2, a Rampage occurs when a single player kills all 5 enemy heroes in rapid succession without dying. This market will resolve to "Yes" if any player on either team achieves a Rampage during Game 3. This market will resolve to "No" if no player achieves a Rampage. If the match is canceled (not played at all) or is delayed beyond 7 days from the scheduled date, this market will resolve to 50-50. If Game 3 is never played due to forfeit, disqualification, or walkover, this market will resolve to 50-50. If Game 3 is not played because the series result has already been determined (e.g., a team clinches the series before Game 3 is needed), this market will resolve to 50-50. If Game 3 begins but is not completed and ends via forfeit, this market will resolve based on whether a Rampage occurred prior to stoppage. If no Rampage occurred, this market will resolve to "No". If Game 3 is remade, resolution will be based on the remade game only. The resolution source for this market will be official information from https://www.dotabuff.com. However, if https://www.dotabuff.com has not published final results within 2 hours after the event's conclusion, a consensus of credible reporting may be used instead including video evidence.

Categories come from a deterministic engine: manual overrides (highest priority) → sports hard markers → event-tag rules → keyword rules → Gamma category hint → default. The engine is versioned in category-overrides.ts; methodology lives at /methodology.