LL777 PRACTICAL HELP LIBRARY

LL777 Tournament Scoring: Points, Caps and Tie-Breaks

LL777 Tournament Scoring: Points, Caps and Tie-Breaks

A leaderboard total makes sense only when the pieces underneath it are clear. Write down LL777 point values, multipliers, caps, penalties and tie-breaks before the event begins.

Use the detailed category screen for calculations. A rank can move while the score stays still if another result settles or a tie-break changes the order.

Deadlines and personal status can change; confirm both inside the signed-in service before acting.

DETAILS TO USE NOW

Start with the section that fits the problem

Build a Plain-Language Score Map

Build a Plain-Language Score Map

List every action that adds points, any value that changes by category and the conditions that make a result count. Include weighted rounds or best-result rules. Put a small example beside each unusual line; working through one calculation early is faster than trying to decode the table after the event.

Apply Multipliers, Caps and Penalties Correctly

Apply Multipliers, Caps and Penalties Correctly

Check the order of operations in the published rules. A multiplier may apply before a category cap, while a penalty may be removed from the final total. Follow the stated rounding method and keep intermediate figures. The same raw activity can produce a different score when the order changes.

Track Categories, Not Only the Headline Total

Open the detailed breakdown at natural breaks and compare each category with your score map. A capped section will stop adding points even when activity continues, and a pending round may be absent temporarily. Avoid chasing live rank until the underlying totals are settled.

Use Tie-Breaks in Published Order

When totals are equal, apply the first tie-break rule and continue only if the accounts remain level. Common criteria include best round, earliest qualifying result or fewer penalties. Do not average several rules together or assume the latest leaderboard position explains which criterion was used.

Audit the Final Result With One Calculation

After LL777 marks the event final, compare the event ID, category values, multipliers, caps, penalties and tie-break with the account screen. If one line differs, show the expected calculation and attach a readable result screenshot. A focused scoring question is much easier for support to verify.

A USEFUL ORDER

Take these actions one at a time

1

Build the score map

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

2

Choose scoring priorities

Focus on reliable actions that fit the format.

3

Track at natural breaks

Review category details between rounds rather than chasing rank.

4

Apply tie-breaks in order

Use the first published criterion that separates equal totals.

5

Audit the final result

Compare each category and document one clear mismatch.

IF THE FIRST TRY FAILS

Checks that help narrow down the cause

The total is lower than expected

A cap, penalty, uncounted round, or category condition may explain the difference.

  • Check the detailed breakdown.
  • Compare the rule line for that category.

Rank changed with the same score

Another result, correction, or tie-break may have changed the ordering.

  • Open the tie-break detail.
  • Wait until the table is final.

NEXT USEFUL GUIDES

Continue from this topic

COMMON FOLLOW-UP QUESTIONS

Short answers before you move on

Another account's result may have settled, a correction may have applied, or a tie-break may have changed the ordering.
Send the event ID, final status, disputed category, rule value, expected calculation, and one clear result screenshot.