How Can I Find a Mako When I Remember Its Category but Not Its Name?

If you remember a Mako’s category but not its name, open the Mako Archive from the MakoBits home page and use the visible category route first: Creatures or Artifacts. If the useful clue is rarity, try Rare; if you retain any name fragment, try Search Mako Archive. Then open each candidate record and compare its displayed type and rarity with your memory. When the list remains broad or empty, return to All and relax one clue at a time. Keep a short log of the route, records displayed and fields that confirmed or contradicted your memory. The supplied public page confirms these labels and record fields, but not the precise matching behaviour of each control, so this sequence is a disciplined way to inspect the archive rather than an assumption about its internal rules.

Verified product note: the MakoBits homepage shows the Mako Archive, Search Mako Archive, All, Creatures, Artifacts and Rare, and describes record details such as type and rarity. Those are the only site-specific interface facts used in this guide.

The C-L-A-R framework: capture, limit, audit, reopen

A category memory is useful, but it is not the same thing as an identified record. The C-L-A-R framework keeps four jobs separate:

Stage	Question	Practical action	What not to assume
Capture	What do I actually remember?	Write the category, any rarity clue, any text fragment and any visual detail. Mark each as certain, uncertain or appearance-only.	A colour, shape or mood is not a verified category.
Limit	Which one visible route best tests the strongest clue?	Start with Creatures, Artifacts, Rare or Search, using one route at a time.	The label alone tells you exactly how matching works.
Audit	Does the opened record agree with the clue?	Compare the record’s displayed type and rarity; use other displayed fields only when they match something you genuinely remember.	A familiar-looking image or name is enough to identify the record.
Reopen	What should change if the evidence is weak?	Return to All or remove one uncertain clue, then log the new route.	Repeating the same guess will add evidence.

The important distinction is between a memory card and an evidence card. Your memory card might say “creature, perhaps rare, name starts with B, blue details”. The evidence card should say “route used, exact record label displayed, fields checked, and which clue remains unverified”. Keeping the two cards separate prevents a plausible visual impression from becoming a false fact.

Use confidence labels that are easy to apply:

Certain: you remember the category or a text fragment clearly enough to test it.
Probable: the clue feels familiar, but you could be confusing it with another record.
Visual only: the clue is based on colour, silhouette, pose or atmosphere. Keep it as a note, not as a selection rule.

This is more useful than trying to remember everything at once. A category is a route choice. A rarity is a checking field as well as a possible route. A visual impression is a tiebreaking note only after the record’s own details have been inspected.

Choose a route without overfitting your memory

Use the strongest reliable clue first, then make the smallest change needed when the displayed records do not settle the question. This decision table is editorial guidance for using the visible controls; it does not describe undocumented product logic.

Memory profile	First route to try	What to check in a candidate	Next move if the display is too broad	Next move if no useful candidate is visible
Category is certain: creature	Creatures	Does the record identify the expected type? Is the displayed rarity consistent, inconsistent or simply unknown to you?	Add Rare only if you truly remember rarity, or inspect candidates one by one.	Return to All and mark the category as possibly mistaken.
Category is certain: artifact	Artifacts	Check the record’s type first, then compare any remembered rarity.	Use Rare only when that clue is independent and reliable.	Return to All; do not substitute a visual guess for the category.
Rarity is the clearest clue	Rare	Confirm the displayed rarity and then inspect type.	Add a category route, one step at a time, if you remember it.	Use All and retain rarity as a note to verify later.
A text fragment is reliable	Search Mako Archive	Open any displayed candidate and compare type and rarity.	Add a category route if the fragment is too common or incomplete.	Do not infer the search engine’s matching rule; use a category route or All.
Only appearance is remembered	All	Look for record fields that can turn the visual memory into evidence.	Once a real category clue emerges, try Creatures or Artifacts.	Record the lookup as unresolved rather than choosing a name by resemblance.

A useful stop rule is “two confirmations or pause”. Treat a record as identified only when at least two independent details agree with the memory—for example, category/type plus rarity, or a reliable text fragment plus type. If only a visual detail agrees, keep the record in the candidate list. This rule is not a claim about the game’s interface; it is a way to keep your notes honest.

Do not stack every remembered clue immediately. If the category is wrong, adding rarity and a partial name can make the search feel precise while hiding the original error. One route, one observation, one adjustment gives you a traceable path back to the answer.

Implementation steps: run one lookup you can revisit

Create a clue card before opening controls. Write category, rarity, text fragment, visual detail and confidence. Use “unknown” rather than filling a gap with a guess. If the memory is only “it was some kind of creature”, record exactly that.

Open the Mako Archive from the home page. Note the initial state you can actually see. The supplied public signal verifies the archive and the labels All, Creatures, Artifacts and Rare, but it does not supply a live interaction trace. Do not copy a candidate name or count into your notes until it is displayed in your own check or in an approved source observation.

Choose one route. Select the control that tests your highest-confidence clue. For a category memory, start with the matching category label. For rarity, start with Rare. For a reliable text fragment, use Search Mako Archive. Record the exact route in the worksheet, including the order in which controls were tried.

Read the display rather than predicting it. Write down the exact record identifiers or names that appear, if any. If there are no candidates, write “none displayed in this check”, not “this Mako does not exist”. If the display is large, record the first set you inspected and the point at which you stopped; do not manufacture a total.

Open candidates and audit their records. The supplied page says that selecting a Mako opens its record and that a record can include type, rarity, origin, power, ability, personality, likes, friends and rivals. Compare only the fields relevant to the clue card. A field that you did not remember is useful context, not confirmation.

Change one variable. If the candidate set is too broad, add one remembered constraint or try the next relevant control. If it is empty, return to All or remove the least certain clue. Never change category, rarity and text fragment simultaneously, because you will not know which change altered the display.

Close with a status. Use one of three plain labels: identified when two independent details agree; candidate when one meaningful detail agrees; or unresolved when the clues are too weak or conflicting. Record the next check beside the status. A clean unresolved entry is more useful than a confident guess that cannot be retraced.

If you are checking several memories, keep each task separate. Reusing the same open record for a second memory can quietly transfer a name or category from one lookup to another. Start a new row, copy only what you actually remember, and repeat the route decision.

Example: a creature clue with no remembered name

Consider a reader who remembers only “the creature entry” and has no reliable name or rarity clue. The category is high confidence; everything else is unknown. The clue card is therefore:

Category: creature — certain.
Rarity: unknown.
Name fragment: none.
Appearance: not used as a route.

The supplied public signal contains one concrete archive observation: the visible excerpt includes the string #001 Comum Robô Bitto Criatura and, nearby, the controls All, Creatures, Artifacts and Rare. This is an observation of the supplied page, not a claim that pressing Creatures returns that record or that it matches the reader’s memory. The original wording is retained because the supplied excerpt does not establish how those displayed labels should be translated in every locale.

Here is the worked decision:

Start with Creatures, because category is the only certain clue.
If the live display presents candidates, record their exact labels rather than assuming that the visible #001 ... Criatura line is the selected result.
Open a candidate and check the record’s type. If it agrees with the remembered category, mark the type as one confirmation.
Check the displayed rarity, but mark it “not compared” rather than “confirmed” because the reader remembered no rarity.
If several candidates remain, use Rare only if the reader later recalls that clue. If none is useful, return to All and record the category as uncertain.
Status: candidate, not identified, until a second remembered detail agrees.

The example is fully worked at the decision level: it shows the input, the route, the evidence boundary and the stop status. It deliberately does not invent a live control result, a list size or a successful identification. That is the correct treatment when the supplied material shows the archive labels but does not include an approved five-task interaction run.

Five-task lookup worksheet

Use this worksheet when you want to compare routes rather than rely on repeated browsing. Run each task in a fresh row. In the result column, record only what the archive displays in the approved check. The blank wording is intentional: the supplied signals do not provide five live lookup outcomes.

Task	Remembered clue	Route tried	Result	Confirmation	Limitation
1. Category: creature	Creature; no name	Mako Archive → Creatures	Record exact displayed candidates, or write `not observed`	Compare each opened record’s type; check rarity only as a separate field	The supplied evidence does not document the control’s matching behaviour
2. Category: artifact	Artifact; no name	Mako Archive → Artifacts	Record exact displayed candidates, or write `not observed`	Compare type and any independently remembered detail	A category memory can be mistaken or incomplete
3. Rarity: rare	Rare; category unknown	Mako Archive → Rare	Record exact displayed candidates, or write `not observed`	Check the record’s displayed rarity before considering type	The label is verified; its exact interaction rule is not
4. Category plus rarity	Creature or artifact plus Rare	Try the category route, then try Rare as a separate step	Record the display after each route, not a combined result unless observed	Compare type and rarity on opened records	Changing two controls at once makes the evidence difficult to interpret
5. Weak or visual clue	Appearance only, or no usable clue	Mako Archive → All; use Search only if a text fragment exists	Record what was inspected, or write `not observed`	Promote a visual clue only when a record field supports it	A visual resemblance alone cannot identify a record

To make the worksheet reusable, add two small fields above the table: check date and archive version or page state, if shown. Do not fill either field from memory. They make later review easier if labels or records are different when you revisit the task.

When the five rows are complete, compare the routes on three editorial measures:

Specificity: did the route reduce the candidate set enough to inspect carefully?
Evidence: did an opened record provide fields that matched the memory?
Revisit cost: can another person follow the recorded route without relying on your recollection?

These measures are for organising a lookup log, not for asserting that one control is universally superior. A route that is narrow but poorly documented is less useful than a broader route with clear record checks.

Limitations

The supplied first-party signal verifies that the Mako Archive, Search Mako Archive and the All, Creatures, Artifacts and Rare labels are visible. It does not document whether a control filters, sorts, searches by partial text, or uses another matching method. This guide therefore describes what to inspect, not an undocumented interaction rule.
Category and rarity clues can be incomplete, remembered incorrectly, or shared by more than one record. An empty display also does not establish that the memory is impossible; it may mean the route or clue needs review.
The page excerpt includes a record line with mixed-language labels. Do not silently translate, normalise or reinterpret a displayed name or rarity label when recording evidence. Copy the visible string first, then explain it only when the source supports that explanation.
Archive labels and records may change. Source-sensitive interface details should be checked again at production time and whenever the worksheet is reused.
This method is for retrieving one uncertain archive record. It is not a collection-completion plan, a board-space guide, an evolution audit or a device-compatibility check.
No live five-task archive results are supplied here. Leave unobserved result cells blank or mark them not observed; do not replace missing evidence with a plausible name, count or rarity.

FAQ

Should I start with Creatures or Rare?

Start with the clue you trust more. If “creature” is clear and “rare” is only a hunch, use Creatures first and treat rarity as a field to check. If rarity is the only solid memory, try Rare first. Record the route before changing it.

Can I use more than one control at once?

You can test a sequence involving more than one visible control, but record each step separately unless the live interface clearly shows a combined state. The supplied evidence confirms the labels, not the rules governing combinations. Separate observations make it possible to tell whether a change came from the category route or the rarity route.

What if I remember only a colour or shape?

Begin with All and keep the visual description on the clue card. Do not use the appearance as proof. Once an opened record supplies a type or rarity that fits, promote that detail to evidence and decide whether a category route is worth trying.

Should I use Search when I remember only part of the name?

Search Mako Archive is a visible control, so it is a reasonable route for a text fragment. Enter only a fragment you genuinely remember, record what is displayed, and inspect the candidate record. Do not assume whether matching is partial, exact, case-sensitive or otherwise defined; that behaviour is not documented in the supplied signal.

What should I do when several records fit?

Keep all plausible candidates in the result column. Open each and compare type and rarity, then use another displayed field—such as origin, power or ability—only if it connects to something you already remember. If no independent detail separates them, leave the status as candidate and note the next clue needed.

What should I do when no record fits?

Return to All, remove the least certain clue and try one route again. Check whether you accidentally recorded an appearance as a category or treated a remembered rarity as certain. If the second pass is still inconclusive, mark the lookup unresolved. That status tells you exactly what evidence is missing without inventing an answer.

Is the visible `#001 Comum Robô Bitto Criatura` line the answer?

Not necessarily. It is a concrete string in the supplied public-page excerpt, so it can be recorded as an observed candidate in an evidence log. The supplied material does not show that a particular reader selected it, that the Creatures control returns it, or that its displayed rarity matches an unstated memory. A live record check is still required.