A field guide for complete campaign runs
This project exists to make Halo: Campaign Evolved easier to finish without losing track of a Skull, Terminal, achievement requirement, or important update. Its purpose is to bring mission-by-mission routes, concise explanations, troubleshooting notes, and a local collectible tracker into one focused reading experience. The aim is practical orientation: help a player identify the right Rally Point, understand what can be missed, and return to the campaign with a clear next action. It does not replace the game or official support documentation.
How the research is assembled
Research begins with a dated route snapshot and a deliberately limited set of permitted public references. Factual notes are compared across official announcements, store listings, developer material, and clearly labelled third-party reporting when those sources are relevant. Each local record keeps source identifiers so a claim can be revisited without fetching remote content during normal use. Observations are separated from confirmed details, and changing information is described with dates or cautious language rather than presented as permanent certainty.
Accuracy has a visible boundary
Accuracy matters, but a guide can still lag behind a patch, regional release, or newly discovered interaction. The checked-in pages therefore favour specific scope over false completeness. A date describes when a report was current; a source note describes the evidence that supported it; and an unknown field stays unknown instead of being filled with a guess. Players making an important purchase or save-file decision should confirm the latest official information before acting.
Original writing and original art
The site content is written for this implementation rather than copied from another guide. Article summaries, routes, search descriptions, legal text, tool instructions, and interface explanations use an independent voice. Game screenshots and key art come from official Halo or platform media sources and are used to identify the game; surrounding layout, checklists, diagrams, and prose are original to this project.
Independent and not affiliated
This is an independent fan project and is not affiliated with, endorsed by, or operated by Halo Studios, Xbox Game Studios, Microsoft, or a platform holder. Halo, character names, game imagery, and related trademarks belong to their respective owners. Official links are citations or further reading, not statements of partnership.
How corrections are approached
A useful correction explains both what changed and why. When an error is identified, the relevant local record should be checked against its cited evidence, amended in the source file, and covered by a focused test when the mistake reveals a reusable rule. Date-sensitive reports should preserve their historical context instead of silently pretending they were always current. Because this build has no submission form, correction requests are handled through the development workflow available with the project, where a proposed change can be reviewed alongside its evidence.