How Can I Track My Progress Toward Discovering All 60 Makos?

The most reliable way to track progress towards discovering all 60 Makos is to keep a separate verification log based on the Mako Archive roster. Give every archive number from 001 to 060 its own row, then record the name and any category or rarity shown, whether you reviewed the profile, and a short note. Start every row as “Not yet verified”; change it only after you have opened that record. This makes your total a count of checked records, not a guess based on memory.

The archive-verification framework

The useful distinction is between seeing a record and understanding what it contains. A collection tracker should therefore use three states:

• Not yet verified: you have not opened or checked this roster entry in your log.
• Profile reviewed: you opened the entry and copied only the fields currently shown there.
• Fully checked: you reviewed the entry and added a useful note about what you want to remember or revisit.

“Fully checked” is an editorial tracking label, not an in-game completion status. The game’s public page describes a Mako Archive with records numbered 001–060 and says a record can include type, rarity, origin, power, ability, personality, likes, friends, and rivals. Your worksheet should leave fields blank when the profile does not show them; blank is safer than inference.

Use the TRACE method for each entry:

1. T — Target: select one archive number rather than trying to remember a name.
2. R — Record: write the displayed name exactly as you see it.
3. A — Attributes: capture only visible category, rarity, and profile fields that matter to your own notes.
4. C — Check: mark the state as Profile reviewed or Fully checked after looking at the entry.
5. E — Escalate: choose the next row using the decision rules below, not a hunch.

This turns the roster into a repeatable audit. It also keeps the worksheet distinct from the game: the log is your external aid, while the Archive remains the place where you inspect records.

A decision rule for choosing the next record

Do not automatically pick the next number in sequence. Choose the row that reduces uncertainty most usefully. Apply these rules in order:

1. Close an obvious gap: if a row is Not yet verified, prefer it over copying information into a row you already checked.
2. Preserve the archive order: when several rows are equally useful, choose the lowest unverified number. This keeps the log easy to audit.
3. Use a visible filter carefully: if the Archive exposes categories or a rarity filter, use it to narrow your inspection, but record what the screen actually shows rather than treating a filter as a completion requirement.
4. Separate discovery from note quality: a record counts as checked because you opened it, not because you have filled every possible note field.
5. Stop when evidence runs out: if a field is not displayed or you cannot verify it, leave it blank and explain that in Notes.

A simple priority score can make the choice consistent:

priority = 3 × unverified + 2 × relevant_to_current_goal + 1 × easy_to_confirm

Use 0 or 1 for each factor. “Relevant to current goal” is your own choice—for example, a category you are trying to understand. This is not a game statistic and does not predict which Mako will appear next. It only prevents a random choice when multiple rows are open.

Example: a three-row verification session

Suppose your worksheet has three nearby rows in different states:

Row 015 is the best next target because it is the only unverified row. The score is higher for that row even if 014 has a more interesting note. After opening 015, copy its displayed name and any displayed fields. If you have no further note to add, mark it Profile reviewed rather than Fully checked. The example deliberately uses placeholders: the supplied public material verifies the bounded roster and available field types, but it does not provide the names or attributes for these entries.

Printable 60-entry tracker

Copy this table into a document or spreadsheet and print it in landscape orientation. The initial status for every row is Not yet verified. Do not treat the table as an in-game feature or as a synchronised record.

Decision key:

• Use Not yet verified until you inspect that numbered record.
• Use Profile reviewed after you open it and capture the displayed name and relevant visible fields.
• Use Fully checked only when you have reviewed the record and made the personal note you intended to keep.
• Count progress from rows marked Profile reviewed or Fully checked; do not count a row from memory.
• If a displayed field changes later, update the row and add a date or context in Notes so the change is understandable.

Implementation steps

1. Make the roster the source of row numbers

Create the 60 rows first, numbered 001 through 060. This prevents a discovered name from becoming a duplicate or leaving an invisible gap. Keep the number as the stable identifier even if you later improve a name or note.

2. Run one short verification pass

Open the Mako Archive and choose a small batch of unverified rows. For each row, work from the displayed record: name first, then category and rarity if shown, then the profile fields that are useful to you. Avoid filling future rows from memory or from a guess based on a similar record.

3. Mark the state immediately

Update the status before moving to the next row. A delayed update is where memory errors enter the process. If you opened a profile but did not finish your note, mark Profile reviewed and leave a clear note such as “follow-up needed”; do not promote it merely to make the total look higher.

4. Reconcile the count

At the end of a session, count the rows marked Profile reviewed or Fully checked. Compare that count with the number of rows that still say Not yet verified. The two counts should account for all 60 rows. If they do not, look for duplicate numbers, accidental blanks, or a row marked complete without a corresponding inspection note.

5. Keep the log useful, not exhaustive

Notes should answer a future question: why you checked this record, what you want to revisit, or which displayed connection deserves attention. The public page says profiles may include origin, power, ability, personality, likes, friends, and rivals, but you do not need to transcribe every field to maintain an accurate discovery count.

6. Use the official game path when you need to verify the context

The verified product path is Home → Mako Archive → 60-record roster → individual Mako profile. If you need to begin there, use the MakoBits home page, then open the Archive from the game’s public navigation. The worksheet supports this inspection; it does not replace it.

Checklist for a trustworthy progress log

Before calling a session complete, check:

• [ ] Every row has an archive number from 001 to 060.
• [ ] New rows begin as Not yet verified.
• [ ] Names are copied from the record rather than reconstructed from memory.
• [ ] Category and rarity are recorded only when shown.
• [ ] Profile reviewed? is marked only after the profile was opened.
• [ ] Fully checked is used for a reviewed row with the intended personal note.
• [ ] Unavailable or unclear fields remain blank, with an explanatory note where useful.
• [ ] The checked-row count and unverified-row count account for all 60 rows.
• [ ] The worksheet is kept separate from claims about built-in game syncing or completion rewards.

Limitations

This method is a personal worksheet, not a demonstrated in-game tracker, cloud sync system, notification, or completion calculator. The supplied public signals verify the 60-record Archive concept and the kinds of fields a record can include; they do not verify a reward for checking every profile, a particular order of discovery, persistence between devices, or a way to export the roster. The tracker also cannot prove that a record’s displayed information will never change. Recheck the record when accuracy matters, and preserve the date or context of your own note rather than presenting it as an official game status.

The priority score has a narrow purpose: it helps you choose among rows you can inspect now. It does not reveal hidden records, increase discovery odds, or tell you what to merge. If your real goal is board efficiency, use a separate board decision process instead of turning this collection log into unsupported gameplay advice.

FAQ

How do I know whether a Mako counts as discovered?

For this worksheet, count a row only after you have opened the corresponding Archive record and marked Profile reviewed or Fully checked. This is a personal evidence rule, not a claim about the game’s internal completion logic.

Should I fill in all profile fields?

No. Record the fields that are displayed and useful to you. The public page indicates that records can include several kinds of information, but a missing field should remain blank rather than being inferred.

Is the tracker an official MakoBits feature?

No. It is an original editorial worksheet designed to accompany an Archive check. It should not be described as synchronised with the game or as an in-game completion system.

Should I inspect records in numerical order?

Numerical order is a good tie-breaker because it makes omissions easy to spot. It is not presented here as the game’s discovery order. If you have a clear personal reason to inspect another unverified row, record that reason in Notes.

What should I do if I cannot verify a field?

Leave it blank, keep the status tied to what you did verify, and add a short note such as “not displayed” or “recheck needed”. An explicit unknown is more reliable than a completed-looking guess.

How can I make the log easy to review later?

Keep the archive number fixed, use the three status labels consistently, and add dates or context to notes when something may change. A spreadsheet can sort by status, while a printed copy is useful for a manual pass; neither should be mistaken for a live game record.