Sources follow the claim
A useful guide names the game or project before giving instructions. Official Minecraft and Xbox announcements support claims about official content. A creator’s project page and release files support claims about that creator’s mod or add-on. One cannot establish the other’s behavior.
For community downloads, we distinguish the author, project identifier, game version, loader and specific file. A project-wide tag is not proof that every version and loader combination is available.
What verification means
A source review checks the cited material against the article. It does not mean we installed a mod or completed a gameplay test. If we publish first-hand tests, the report must identify the game or project, release version, loader where relevant, and what was actually observed.
Practical suggestions, such as rehearsal or troubleshooting order, are labeled as editorial advice. We do not turn a trailer image into a claimed drop rate, unlock route or complete map.
Read the dates correctly
- Publication date: when the article was first issued on this site.
- Source review date: when the cited material was checked for the claims in the article.
- Substantive update date: when an answer, procedure or other meaningful content changed.
A newly checked date does not mean the game itself changed. News distinguishes the date of an event from the date of its announcement.
Corrections and material changes
Use Contact and Corrections to identify the affected page, passage and supporting source. We review the report against the relevant announcement, project page or release file. A substantiated error is corrected; a changed release is described as an update. Material changes should explain what changed and revise the relevant date.
Original AI-generated concept art is labeled as illustration. It is never used as evidence of a game feature or presented as an in-game screenshot.
Match evidence to the question
A source is useful because it supports a particular claim. An official launch article can establish a game’s release and announced platforms. A community release page can establish the Minecraft version and loader attached to that file. A screenshot can show that something appears in an image. Those are different kinds of evidence, and our wording should preserve the distinction.
When a guide gives a sequence, the source must support the sequence rather than merely naming the same destination. When a table gives a dependency, the requirement must belong to the relevant file or a clearly applicable author statement. When a probability appears, we identify whether it is an author’s stated rule or a measurement from a defined test. A number without that context can turn a useful hint into a misleading promise.
Official information and community implementations
Official sources take priority for what Mojang or Microsoft has announced about the official games. Community creators are the primary sources for their own projects. A creator’s interpretation can be valuable and well documented without describing the final behavior of a future vanilla release.
The same name can therefore have more than one accurate explanation. If two implementations differ, we compare them rather than selecting whichever description is longer. A pet entitlement in one game and a taming mechanic in a mod belong in separate rows, with the game or project visible in each row. The reader should be able to choose the applicable explanation before following any steps.
Files, requirements, and missing records
File-level information is preferred for compatibility decisions. We record the release identity, game version, loader, and available dependency evidence together. A project’s broad list of supported versions does not establish every possible pairing, and the absence of a pairing from our records does not establish incompatibility.
An unknown result should direct the reader to the next source that could resolve the question. For example, a missing dependency record calls for the original file page, not a guessed empty dependency list. A changed release can require a new review even when the project name remains the same.
| Evidence | Appropriate claim | Extra evidence needed for a stronger claim |
|---|---|---|
| Official dated announcement | What was announced at that time | A later release notice for current availability |
| Creator’s release file | Its listed game version and loader | Runtime observation for a tested combination |
| Creator’s mechanism description | The behavior the author documents | A defined test for our own measured result |
| Labeled screenshot | What the image identifies or shows | Instructions or observation for a complete procedure |
| Tool metadata result | What the selected package declares | Publisher identity and runtime checks for broader conclusions |
Build an answer from the evidence
A useful article does more than repeat a source in a different order. We organize information around a decision: which project to select, which ingredient to gather, which stage of a procedure needs attention, or which release track an announcement concerns. Tables, diagrams, and examples should make that decision easier.
Editorial advice is labeled when it adds an order or preference that the source does not prescribe. For example, choosing one resource goal for a first outing is a planning suggestion. It must not become an invented game requirement. A troubleshooting checklist can order the documented prerequisites without claiming to fix every possible failure.
Examples are also identified by their role. A hypothetical file mismatch illustrates a comparison; it is not evidence that a particular download failed on our machine. A practice exercise can demonstrate a website tool without being described as a completed in-game run. Readers should be able to tell what the example teaches and what it actually proves.
Resolve changed or conflicting information
When sources disagree, we first compare their subject and date. They may describe different projects, releases, platforms, or stages of development. A newer date alone does not make a source applicable to an older file, and a popular tutorial does not override a clearly identified author release requirement.
If the difference affects the next action, the article should explain it close to that action. A loader change belongs beside the file choice. A revised activation step belongs beside the procedure. We avoid scattering the same broad caveat throughout an article when a precise note at the decision point would answer the concern.
A correction changes something that was wrong when published. An update reflects information that became different later. That distinction matters for news archives: a report of an announcement remains a report of that event, while the current release page should carry the present answer. We link those pages so readers can move between history and current status.
Handle images, quotations, and diagrams
Source links let readers inspect the original material. They are not licenses to reproduce it. Third-party screenshots and artwork require their own attribution and appropriate reuse basis; a link alone does not settle those questions. Quotations should be short, clearly attributed, and useful to the point being explained.
Our concept illustrations are original AI-generated artwork. A caption or alternative description should identify them as illustrations and describe the actual scene. They do not establish the layout of an Ancient City portal, the appearance of a named official biome, or an item’s crafting recipe. A factual diagram should instead map an evidenced relationship, such as which file fields must agree or which resource leads to which documented interaction.
Send a correction that can be checked
Use the contact page with the affected URL, the passage, and the source supporting a different answer. For a mod, add the author and exact release. For a dated announcement, identify both the event and the publication you are referring to. You do not need to provide a complete replacement article.
We review the evidence and the related pages that may share the same fact. A corrected file requirement may affect the project page, installation guide, and tool record together. The aim is a consistent answer wherever the same decision appears, while preserving each page’s separate task. Reports containing personal information should go to the support mailbox rather than a public thread.
