Editorial Policy
Our editorial standard is simple: explain the system clearly, separate stable concepts from version-sensitive details, and make uncertainty visible instead of hiding it.
Accuracy before speed
Guides are structured around mechanics that can be explained reliably: resource generation, storage, progression order, structure planning, and troubleshooting logic. We do not intentionally fill gaps with guessed recipes or unsupported numbers.
When a detail can change between Blood Magic builds or modpacks, readers are directed to verify that detail in their exact installation. This is especially important for recipes, tier requirements, capacities, and pack-specific configuration.
Version-aware writing
The site states its reference focus and uses version notes where they help prevent confusion. A page may remain useful across multiple releases while a specific recipe changes, so we distinguish the durable concept from the value that should be checked in-game.
Updates are designed to preserve clean URLs. When a page is improved, the existing canonical route is preferred so bookmarks and search references do not break unnecessarily.
Sources and official links
For downloads and project authority, we point readers to the official CurseForge listing and source repository. We do not describe this site as the official Blood Magic project website.
Technical explanations may summarize game behavior in plain language. We avoid copying large blocks of text from other guides and aim for original explanations written for the task a player is trying to complete.
Corrections and revisions
If a page is found to be unclear, outdated, or internally inconsistent, the preferred fix is to correct the affected explanation and any related navigation or metadata in the same release. Cross-page links are reviewed after route changes.
Major structural changes are tested against both PHP routing and static fallback pages so a content correction does not create a new navigation problem.