QORPO Blog / Studio

How AneeMate’s leaderboard development handles older derived scores

Q
QORPO Studio17 November 2026 · 4 min read
Graphite blocks with a mint tile aligned on the top row
Concept illustration created for this article, not a gameplay screenshot.

A change in AneeMate's competition service adds a pass that recalculates stored creature board values when the service starts. The aim is to apply the same calculation to older records and new records after a rule correction. This is a look at implementation and tests from November 9. It uses a model example to explain what a change like this means for a board.

Why can the same catch appear with a different score?

A leaderboard can store the inputs to a score and the result it last calculated. If a rule changes, the original catch can stay in the records while the derived result changes. That is useful when the older result was calculated with the wrong rule. It also means a browser screenshot taken before the change may show a different value from a current board.

Imagine a model creature board that uses a creature's species and level to calculate a power column. A rule correction changes what one species contributes to the calculation. New entries immediately use the corrected rule. If older result values remain untouched, the board compares entries using two different versions of the calculation. Recomputing the stored values removes that inconsistency once the service actually runs the new code.

The AneeMate records and web leaderboard article explains how a game event reaches a web board. Here the question begins a step later, after the service already has the inputs.

What did the service change?

The reviewed service change adds a recomputation step after schema setup. It reads stored creature records, derives values with the current calculation and updates rows where the relevant values differ. The code covers derived fields such as potential grade and power. The repository also contains tests with fixed inputs and expected outputs for specific grading cases. Those tests give reviewers stable expectations for future rule changes.

This workflow is useful because an implementation can pass a test for new entries and still leave earlier entries on the old rule. A good review asks about both. If you are writing a test plan, map one example to an existing record, then run the same inputs through the new-entry path. The QORPO guide to expected game test results describes how to state the expected result before generating or extending test cases.

How would a reviewer check both paths?

In a model test, create an older record with a derived value from the previous calculation. Keep the inputs stable. Run the update, open the board with the same filters, and confirm that the displayed value matches the new calculation. Then create a new record with comparable inputs and check that both rows were scored using the same rule. Keep identifiers in the test environment and record only aggregate or synthetic examples in shared notes.

Also look at a record whose result is expected to stay the same. It gives the reviewer a useful control. Compare what happens when the work runs again, especially if the update is part of service startup. A repeat run should produce the same visible result given the same inputs and rule. Check the board order as well as the row value. An unchanged creature might still move in the list because another row's score changed.

If the board is paginated, look at the boundary between pages as part of a test. A correction that changes tied values can push a row across that boundary. Record the selected sort and compare the final order using the project's tie policy. You can then describe the change without making an unsupported claim about who gained a position.

How should a player read a change on a board?

Start with the board name, the selected species and the metric. A potential grade, a power value and the fact of a catch each describe something different. If you are comparing an older image with a current page, make sure both display the same metric and filters. The AneeMate guide to comparing board periods covers that first check.

The source reviewed for this article establishes the service implementation. Its production rollout and board-wide effects have not been verified for this report. For the actual listings, start with the AneeMate species ranks page. Follow the QORPO studio feed for separate progress on the game and its services.