Source hierarchy
We use the strongest available source for every factual claim. The hierarchy is simple: the developer's official words first, then the storefront record, then official media, then clearly labeled community material.
- Official text: Mossbomb's site, press kit, Steam description and Early Access Q&A.
- Storefront data: Steam pages and public appdetails records for release date, languages, features, requirements and media metadata.
- Official media: Screenshots, UI captures and trailers published by Mossbomb. These can prove what a build shows; they cannot prove a hidden formula.
- Community reports: Useful for finding questions, but not used as primary evidence. If cited, they are attributed and kept separate from confirmed facts.
The full list, with access dates, is on the source log.
Evidence labels
Official
The claim appears in official developer or storefront text. It is the strongest evidence we have, though plans can still change.
Official media
The behavior or object is visible in an official screenshot, UI capture or trailer, but the developer has not described its numbers. We report what is visible and say what is not.
Named only
A name is confirmed but its effect is not published. We list the name and mark the effect unknown.
Not announced
No primary source exists. We say so. We do not turn a plausible guess into a “likely” fact.
Editor's take
Planning advice or analysis derived from confirmed systems. It is not a claim about the game's code, balance or hidden values.
No fabrication
We do not invent creatures, bosses, upgrades, damage values, release times, player counts, reviews or patch notes. If a page cannot be filled with verified information, it stays short and says what is missing. We do not create a page for every keyword in a game that has not published enough material to support one.
The same rule applies to guides. A recommendation can be useful without being a “tested” claim. We label the difference. We do not present an AI-written route as a personal playthrough, and we do not use fake “hours played” credentials.
Automation and AI
Research and drafting are assisted by automated tools. That is a production method, not a source. Every game fact must still resolve to a linked primary source or an official screenshot. The reviewer is responsible for the published claim, the context and the label.
We do not use automation to mass-produce near-duplicate pages, scrape competitor text or generate fake FAQs. The site grows by adding a page when there is a real question and enough evidence to answer it.
Updates and corrections
Each page shows a reviewed date. When a source changes or a correction is accepted, we update the page and the date. We do not change dates to fake freshness, and we do not remove an old claim without noting the correction if it materially affected a guide.
To send a correction, include the page URL, the exact claim and the source that contradicts it. Screenshots should include the build or date. Use the contact page.
Advertising and independence
Malignus Wiki is independent and not affiliated with Mossbomb. There are currently no advertising, affiliate or sponsored-content scripts on the site. If advertising is introduced later, it will be clearly separated from editorial content and will not determine a page's conclusions. Sponsorship will be disclosed on the page where it appears.
The site does not sell review scores, rankings or “best build” placements. A page's recommendation is either a labeled editorial judgment or a direct report of an official fact.