Skip to article

What AneeMate’s Matebook base total means when you sort by Stats

QORPO Studio · 20 November 2026 · 5 min read

Buxy examining five stone stacks of different heights in an island clearing
Concept illustration created for this article, not a gameplay screenshot.

The AneeMate website’s Stats sort orders matching creatures by their reference base-stat total, from larger to smaller. That total adds five fields: hit points, damage, attack power, toughness and haste. It is a catalogue comparison, not a universal ranking of battle performance.

The inspected website implementation sorts the current matching list by that total and uses the creature number to break ties. Reading the individual fields remains necessary after choosing a card.

What is being added?

The public species data contains a base value for each of the five fields and a base-stat total. The total gives a compact summary of those reference values.

For Buxy, the current entries are 67 hit points, 73 damage, 81 attack power, 66 toughness and 54 haste. Their sum is 341, matching its reference base total.

This arithmetic does not define how those fields translate into every combat outcome. It simply explains the number used by the website’s base-total comparison.

What happens when you press Stats?

The reviewed Matebook code first selects creatures matching the current search and filters. It then sorts that selection by descending base total.

If two entries have the same total, the reviewed sorting function uses their number as the next comparison. That tie-break is a catalogue-order decision, not a claim that the lower-numbered creature is stronger.

If the list is unexpectedly short or empty, see the filter recovery guide. Sorting an already filtered list does not restore entries excluded by its conditions.

Compare the shape of the stats

Two creatures can reach a similar total with different distributions. One may place more of that total in hit points, while another places more in damage or haste.

A model comparison would first identify the task: surviving a particular encounter, using an available move or accompanying a specific party. The reviewer would then inspect the relevant fields and matchup information.

Without that context, the first item in a sorted list is only the first item under that sorting rule. It does not establish the best choice for every player.

The Buxy family shows why individual fields matter

The current reference totals are 341 for Buxy, 355 for Buxica and 408 for Lixarina. Looking only at those totals could suggest a smooth increase across every field.

The listed base hit points tell a different detail: 67, 58 and 67 respectively. Buxica’s larger total than Buxy therefore does not mean it has a larger value in every component.

The Buxy family guide covers the accompanying move and element differences. Reading that context is more useful than treating the total as a complete progression verdict.

Base total and the card’s current-level display

A species card can display values for a selected companion level and other reference controls. Those displays answer a different question from the stored base total used by the catalogue sort.

When comparing cards, note the labels and selected level. A value shown under a current-level heading should not be silently substituted for the base value in a comparison.

Likewise, a family ceiling is not the same thing as the starting reference total. The card labels are there to distinguish these views, so keep those distinctions when describing a creature to another player.

Matchups remain outside the sum

The total does not encode the whole defensive element combination. A larger number cannot tell you whether the opposing move is Electric, Ice or another element.

The element matchup guide explains that separate part of planning. Read the creature’s actual badges and defensive entries alongside its statistics.

The Usbir family guide provides another example where a later form changes its element combination. That change needs attention even when the overall reference total increases.

What the development check should verify

A focused website check can compare the displayed Stats order with the public base totals of the same filtered entries. The expected rule is descending total, with the documented number tie-break.

That is a precise acceptance case for the catalogue. It does not require inventing combat simulations or claiming that a website sort measures a player’s account.

This article is grounded in the published sorting function and current species data. The source makes the sorting rule reviewable; actual browser checks still need to record which list and conditions were inspected.

Common questions

Does the top Stats result win every fight?

No. The total omits the specific encounter, available moves and individual companion state. Use it as one reference while planning.

Can a later form have a lower value in one field?

Yes. The Buxy and Buxica base hit-point entries provide a concrete example. A higher total is not a statement that every component is higher.

Does changing the level slider reorder the entire Matebook?

The inspected catalogue Stats sort reads the reference base total. Do not assume a card-level preview control rewrites that stored sorting field.

Is rarity the same sort?

No. The website has a separate Rarity control. Rarity order and base-total order use different fields and should not be treated as interchangeable.

Open the Matebook, choose Stats and then inspect a creature’s individual card. The total is a useful starting point when its meaning stays clear.

Sources