Anime Expeditions Wiki Sources — Miraheze Database & Sync

Need the live community wiki? Use animeexpeditions.miraheze.org. This page documents how animeexpedition.com builds its unit and item database from public Miraheze revisions (pageid + revid): immutable snapshots, derived tables, and CC BY-SA attribution. We are an unofficial fan site — not the wiki, Miraheze, or the publisher. Everything below explains sync, traceability, and licensing.

Primary source

Structured facts on this site are synced from the public Anime Expeditions Wiki on Miraheze via the MediaWiki API. We are a separate fan site that reuses public wiki content under the wiki’s stated license; we are not that wiki, and we are not affiliated with it or the game publisher.

The Miraheze wiki currently declares CC BY-SA 4.0. Reuse here follows that license: attribution, license link, and a note that content may be adapted into structured pages. See also the source copyrights page. Game trademarks, character art, and third-party assets are separate from the wiki text license.

How sync works (revision inventory)

Each sync run rebuilds a checklist of current wiki pages (pageid, title, and latest revid) and compares it to what we already stored. Only new or changed revisions are downloaded. When the checklist and downloads match, we commit a snapshot — a verified point-in-time copy of the public wiki state we use for building this site.

We do not rely on RecentChanges alone. If a sync is interrupted or delayed, the next full inventory check can still catch up to the wiki’s current public revisions.

Traceability

Behind the scenes, every derived record keeps a link back to the Miraheze page and revision it came from (snapshot id, pageid, revid). Unit detail pages expose a Source wiki link when available; the rest of the chain is for sync and verification, not something you need to read on every page.

Raw vs derived layers

• Raw layer — immutable MediaWiki API responses keyed by pageid and revid (plus snapshot manifests). We keep these so any published fact can be re-checked.
• Derived layer — structured records parsed from a verified snapshot (for example UnitData modules turned into filterable unit rows). The site reads derived data; it does not invent game stats.

If a field is missing on our page, it was usually missing or unstructured in the snapshot — not silently filled in by AI rewrite.

Corrections

For factual disputes, compare with the Miraheze wiki page for that topic. Source-wiki edits land here after the next successful snapshot and rebuild. Site-only presentation bugs (filters, layout, broken links) are separate from wiki content — see About for scope.