Collection guide

ACE COMBAT 8 Named Aces Checklist: How to Use It

Use the partial ACE COMBAT 8 ace checklist, distinguish reports from confirmed Assault Records, and back up collection progress without changing mission ranks.

Official ACE COMBAT 8 promotional artwork; not a screenshot of this specific guide or mission.

Use the named-ace checklist to keep track of records you personally confirmed, not to claim that a trigger has certainly worked. The current release contains six selected entries. It is neither a complete list of Assault Records nor an automatic game-save reader.

Three different observations

An attempted trigger, an aircraft appearing and an Assault Record being registered are different observations. Record hunting becomes confusing when they are compressed into a single claim such as “I did the condition, so it must be complete.” The checkbox on this website represents only your confirmation of the recorded result.

The linked Piyoko and Rafly guides report Veteran-or-higher requirements and mission completion for conditional aces. They do not establish a single, fully reconciled prior-clear or checkpoint rule here. Consult the original mission-specific account and your actual game state rather than extending a general note to every encounter.

Our score diagnostic has a different scope: Ace / Free Mission with no checkpoint retry. That software limit does not mean every named ace requires Ace difficulty. Likewise, an ace checkbox does not provide evidence for a scoring bonus.

What is included

The current cards correspond to Missions 2, 3, 5, 6, 8 and 16. Each card contains the reported condition, its attribution and any important uncertainty. Exact positions, enemy-health thresholds and timing limits are not invented to make a card look complete.

Two descriptions agreeing is not automatically independent testing. Some accounts may reuse the same underlying discovery, and this site has not reproduced these encounters in-game. The date shown on a card is the source-review date, not an asserted patch number.

A useful sequence for a personal attempt

Before launching, choose one intended record and read the exact caveat on its card. Prepare a place in your notes for what you observed. After the sortie, compare those notes with the actual Assault Record, then mark the website entry only when you are satisfied that it is present.

If the record is missing, keep the observation specific. Did the aircraft never appear? Did it appear but escape? Did you finish the sortie? We do not infer which condition failed or label the game as bugged from a missing checkbox. A clean observation is more useful for your next attempt than a confident but unsupported diagnosis.

Avoid treating a time displayed in another player's video as a universal spawn timer. It may describe their particular route. This website does not convert an observed timestamp into a deterministic deadline unless the source actually supports that requirement.

Storage, backups and safe imports

The collection list uses a separate browser-storage key from the mission flight log. Marking or resetting an ace does not change any rank, score or mission note. English and Chinese pages share the same collection data on the same website origin; another device or another preview hostname does not automatically share it.

Export a JSON backup before clearing browser data. The ace import accepts its own versioned format, not a mission-log export. It checks identifiers, booleans and timestamps before saving. Invalid data must leave the previous list unchanged. For duplicate valid entries, the newer timestamp wins; an older backup must not resurrect a record you subsequently unchecked.

If stored data cannot be read, changes are locked instead of replacing it with an empty list. Resetting requires a deliberate confirmation and affects only the collection list. Browser restrictions can still prevent saving; pay attention to the displayed status instead of assuming a checkmark has reached storage.

Newly added entries and older backups

Flamma and Tessera link to their own mission dossiers. Importing an older four-entry-era backup does not automatically confirm them or erase newer collection choices. Keep the same backup format; there is no account migration.

Why some names are not present

Coverage follows reviewed evidence, not a target page count. We excluded unresolved entries rather than automatically merging conflicting names or trigger descriptions. A missing card means it is not included in this release. It does not establish that the game lacks the encounter.

Can I use the list without an account?

Yes. There is no website account or server-side progress database. Export a backup to move your own data.

Does a checked ace mean I earned S rank?

No. The two tools store separate, user-entered observations. The site never converts one into the other.

Return to the ace checklist, mission library or mission flight log.

Sources