Inside AneeMate’s Matebook filter counts: showing the next choice

AneeMate’s web Matebook counts filter alternatives separately from the final grid. For an Element count, the website keeps the other active filters but leaves out the current Element selection. This lets the sidebar show what another element would offer, instead of repeating only the creatures already visible.
That distinction is small enough to miss and useful enough to explain. A player looking at Water creatures may still see a nonzero number beside Fire. The number is a navigation aid. It does not mean Fire-only creatures have slipped into the Water results.
This development explanation follows the live website and its reviewed source on 21 November 2026. It concerns the public catalogue, not a change to combat, catching or the game’s collection.
What does the final grid count?
The grid applies the selected collection view, element, rarity and search together. Sorting happens after that filtering. A creature must meet every active group’s condition to remain visible.
Inside the Element group, a dual-element creature matches either of its listed elements. Selecting Water therefore includes a Water-and-Ice entry. The site does not require Water to be the first element.
This is where a useful catalogue differs from a simple list of names. A visitor can ask a particular question, such as which Water creatures match a rarity, and still see where to go next if the current answer is too narrow. Our earlier Matebook development overview introduces the wider studio context.
Why ignore the group being counted?
The reviewed drawRail function creates a different candidate set for each group. Element counts use matches with the element condition skipped. Rarity counts skip the rarity condition. Collection counts skip the collection condition.
Every other condition still matters. If you add a name search, the sidebar alternatives narrow around that search too. The website is not displaying permanent totals beside every option regardless of what you typed.
Consider a clearly labelled model catalogue containing four entries. Two are Water, one is Fire, and one is Water and Fire. With Water selected, the visible grid contains three entries. The Fire alternative can show two because those are the entries that would match Fire under the remaining conditions. These are illustrative numbers, not the current AneeMate roster.
Why can adding the element counts mislead?
The model creature with both elements belongs to both counts. Adding Water and Fire gives five memberships even though the catalogue has four distinct entries.
That is an ordinary consequence of overlapping categories. It is especially relevant to creature games, where dual elements carry useful meaning. Forcing the counts to add up would require hiding one of those memberships or changing what the labels mean.
A sidebar is easier to trust when each number answers a clear question. Here, it describes an alternative filter choice. The grid answers the final combined question. Those two numbers can be different while both are correct.
What should a source review check?
A small review can use a fixture roster rather than the complete product dataset. Include one single-element entry, one dual-element entry, and two rarities. Write the expected grid and sidebar results before running the code.
Then change one group at a time. Confirm that a rarity selection changes the Element alternatives, while the selected Element does not erase its sibling alternatives. Add a name query and repeat. Finally, clear the query and check that the broader counts return.
This is a proposed verification method, not a claim that we ran a new game test. The current article’s publication checks establish the website source and public presentation. They do not establish every possible future roster combination.
What happens to caught and missing views?
Caught marks belong to this browser’s checklist. The code uses them when calculating the Caught and Not caught alternatives, while retaining the other filters. They are not imported from the game.
That boundary matters for interpreting a count. A zero beside Caught may describe the browser checklist under the current conditions. It says nothing about the player’s save or their friend’s progress.
The public AneeMate Matebook is the right place to explore the interface. Its browser checklist explanation provides the separate collection context if that is the question you are trying to answer.
What does this teach a game website team?
Before adding counts, write the question each number answers. “Results visible now” and “results available if I choose this option” are different contracts. Mixing them creates an interface that looks precise while requiring visitors to guess.
For another studio example, read our capture interruption explanation. For the wider evidence boundary, QORPO Live separates public progress reporting from a claim that every source change is already released.
FAQ
Does a nonzero alternative mean the current grid is wrong?
No. It can describe the result of changing that group while keeping the other conditions.
Do these numbers predict spawn or catch chances?
No. They count catalogue entries under website filters.
Is this a new game feature announcement?
No. It explains existing public website behaviour reviewed on the date above.
Sources and next step
Primary evidence is the live Matebook and its public interface script, particularly matches and drawRail. Explore the roster there, or follow QORPO Studio for the products behind these development decisions.
QORPO