IM777 FIELD NOTE · PRACTICAL WALKTHROUGH

IM777 Event Scoring Guide: Points, Penalties and Tie-Breaks

IM777 Event Scoring Guide: Points, Penalties and Tie-Breaks

A point system table is easier to use when points, multipliers, penalties, and tie-breaks are read as separate lines. Estimating everything from position alone invites mistakes.

This IM777 field note covers live totals, provisional standings, later corrections, and the evidence needed when a confirmed point total still looks wrong.

For live dates, profile status and feature availability, rely on the current IM777 app page.

THE WORKING NOTES

Take the topic one part at a time

Stop when the question is answered; there is no benefit in changing several settings together.

Turn the Instruction Table Into a Point Total Map

Turn the Instruction Table Into a Point Total Map

Write down every action that adds points and every condition that subtracts them. Include caps, multipliers, stage weighting, and any category that counts only once.

Use the latest IM777 app event instructions, not a table from a similar earlier app event. Small point system changes can alter the best priority.

  • Add caps and multipliers.
  • Record penalty triggers.
  • Write down stage weighting.
  • List base point values.
Read Live Scores as Provisional

Read Live Scores as Provisional

A live total might exclude a pending stage, later bonus, or penalty review. The standings can move even when your own displayed number has not changed.

Review standings at natural breaks and look at the category detail. Constant refreshing gives little useful information during active play.

  • Review between stages.
  • Treat live position as provisional.
  • Save important point total changes.
  • Look for pending categories.

Follow Tie-Breaks in Order

Equal totals might be separated by head-to-head outcome, completion time, secondary point total, highest stage, or another published measure. The first criterion that resolves the tie usually decides position.

Don't jump directly to the last tie-break. Compare each line in the listed order and keep a copy of the confirmed table that shows the applied outcome.

  • Compare criteria in sequence.
  • Review if time is measured.
  • Keep a copy of the resolved position.
  • Find the first tie-break.

Review a Confirmed Point Total Mismatch

Wait until every stage is settled and the app event is marked confirmed. Compare base points, multipliers, penalties, and tie-breaks as separate categories.

If one line still differs, send the IM777 help team the app event ID, confirmed page, disputed category, instruction value, and expected calculation. A focused report is easier to verify.

  • Recalculate one category at a time.
  • Include the matching instruction line.
  • Report only the disputed value.
  • Verify confirmed app event state.

Multipliers, Caps and Rounding

A multiplier might apply before or after a category cap, and decimal values might be rounded at a specific stage. The order can change the displayed total.

Work through the published example if one is provided. Calculate base points, apply the multiplier in the listed place, enforce the cap, then use the app event's rounding instruction.

When reporting a difference, show each line of that calculation. A confirmed number without the intermediate steps is harder to compare with the IM777 point system.

  • Apply category caps correctly.
  • Use the published rounding instruction.
  • Show intermediate values.
  • Look over the order of operations.

ACTION LIST

A useful order for the checks

1

Build the point total map

List values, multipliers, caps, penalties, and weighted stages.

2

Select point system priorities

Focus on reliable actions that fit the structure.

3

Track at natural breaks

Review category information between stages rather than chasing position.

4

Apply tie-breaks in order

Use the first published criterion that separates equal totals.

5

Audit the confirmed outcome

Compare each category and document one clear mismatch.

IF SOMETHING STALLS

Two likely places to look first

The total is lower than expected

A cap, penalty, uncounted stage, or category condition might explain the difference.

  • Look over the detailed breakdown.
  • Match the instruction line for that category.

Position changed with the same point total

Another outcome, correction, or tie-break might have changed the ordering.

  • Head to the tie-break detail.
  • Wait until the table is confirmed.

RELATED FIELD NOTES

Continue only where it helps

QUICK ANSWERS

What people usually ask next

Another profile's outcome might have settled, a correction might have applied, or a tie-break might have changed the ordering.
Send the app event ID, confirmed state, disputed category, instruction value, expected calculation, and one clear outcome screenshot.