Editorial Policy
How we keep guides useful, honest, and correctable.
MetaGuide Hub publishes practical game guides for Minecraft, Roblox, and Fortnite. We are still a small site, so we do not pretend to be a giant community wiki or a full video studio. The goal is to be clear about what each guide covers, what it does not cover, and how readers can correct it.
Bylines
Guides are currently published under editorial desks, such as the Minecraft survival desk, Roblox safety and systems desk, and Fortnite systems desk. We do not create fake personal author biographies, fake playtime claims, or fake player identities. If we add named reviewers later, their role and scope will be stated clearly.
Version Scope
Each guide page includes a version-scope box near the top. Minecraft guides describe whether the advice is general Java and Bedrock survival guidance or whether edition-sensitive mechanics may matter. Fortnite guides mark season-sensitive pages clearly and avoid exact live values unless they are checked. Roblox guides explain that code menus, rewards, privacy labels, and private server behavior can vary by experience.
Verification Standard
We prefer practical checks that a player can repeat: material lists, setup order, symptom tables, decision rules, and common failure cases. When a detail depends on a current patch, event, live loot pool, temporary code, or platform menu, the guide should say so instead of pretending it is permanently true.
Images And Media
We do not hotlink random screenshots from wikis, Reddit, forums, or image search results. Local diagrams are labeled as diagrams. Real gameplay screenshots and short clips should be first-party captures, official media we can use responsibly, or reader-submitted media with permission and private details removed.
Community Data And Image Use
Community-maintained mechanics pages, support threads, and player reports can be used as source material when they help explain real player problems. We summarize the practical takeaway and link the source instead of copying large passages.
Community images are stricter. We only embed a community image when the license allows commercial reuse, attribution can be shown clearly, and the image actually helps the guide. Screenshots from Reddit, Discord, Fandom, YouTube, or a wiki are treated as reference material unless we can confirm permission for reuse on an ad-supported site.
Current Media Sourcing Log
| Media source type | Status | How we use it |
|---|---|---|
| Minecraft Wiki screenshots and files | Reference only for now | Many files are marked as Mojang assets or non-commercial Creative Commons. We use the mechanics data, then create our own diagrams or first-party screenshots. |
| Wikimedia Commons Roblox photos | Candidate pool | Only images with commercial-compatible licenses and clear attribution are considered. Photos with people or de minimis screen warnings are reviewed before publishing. |
| Fortnite community screenshots | Not embedded yet | Most gameplay screenshots are not clearly reusable. We use Epic support pages and player discussion patterns for data, then wait for first-party captures or clearly licensed official media. |
| Reader-submitted screenshots | Accepted with permission | We can publish screenshots when the sender confirms permission, removes private details, and identifies the game version or season. |
Corrections
Every guide includes a feedback and correction link. Useful correction reports include the page URL, game version or platform, what happened in your test, and what the guide should say instead. We prioritize corrections for wrong steps, outdated menus, missing version notes, and unclear instructions.
What This Site Is Not
MetaGuide Hub is not a live code tracker for every Roblox experience, not a Fortnite patch-note mirror, and not a replacement for Minecraft Wiki-level block data. It is a practical guide library. When exact current values matter, pages should point readers back to in-game menus, official release notes, or current community-maintained references.