Checklist Columns
- CG number or neutral label
- Chapter or story segment
- Route or companion context
- Unlock condition
- Voice-scene marker
- Spoiler level
Save Strategy
Create a save before major choices and keep the first playthrough mostly blind. Completion notes should be written after the scene, not before, so the tracker helps without ruining the story.
- Keep one clean first-playthrough file.
- Create checkpoints before route choices.
- Name saves by chapter or scene type, not late spoilers.
Spoiler Labels
- Safe: no character or plot reveal.
- Route: names a route or companion context.
- Late: reveals a major memory or ending context.
- Hidden: keep collapsed until the reader opts in.
Starter Tracker Template
| CG | Segment | Context | Unlock Note | Voice | Spoiler |
|---|---|---|---|---|---|
| CG-001 | Opening | Protagonist memory | Story progress | Unverified | Safe |
| CG-002 | KaijuTamer setup | Taming event | Story progress | Unverified | Route |
| CG-003 | Companion scene | Name pending official update | Choice or route pending update | Unverified | Hidden |
Continue with the route map guide and beginner guide.
Completion Workflow
A CG checklist becomes messy if it guesses route names too early. Keep early entries neutral, then update labels after the game, demo, or official posts confirm the structure. For search readers, the value is not just the final number; it is knowing where to save, which scenes are safe to preview, and which entries should stay hidden until a route is complete.
For a real completion run, record the save file, visible choice, scene category, and whether the CG appeared automatically or after a route-specific decision. If the scene includes voice work, mark it separately instead of assuming every important CG is voiced.
Update Rules
When official route names or a demo build becomes available, add a route filter and split the table into story, companion, memory, and special-scene groups. Avoid uploading full CG images into the checklist; use local media only for page presentation and keep the tracker focused on navigation and completion notes.
How Players Should Use This Page
On a first playthrough, do not try to complete every entry. Use the checklist only to mark where a save was made, whether a CG appeared, and whether the scene felt route-specific. On a second playthrough, compare the same segment against a different choice path. If the CG changes, record the difference without naming the late-story reveal in the visible row.
For guide writers, the cleanest workflow is to keep two versions of the notes: a public spoiler-light table and a private completion sheet. The public table should help readers find missing scenes; the private sheet can store exact choices, late-route names, and ending conditions until those details are safe to publish.