Anime Expeditions Wiki Editorial Policy & Corrections

What does this wiki publish?

We publish information that helps a player complete a clear task: joining the correct game, redeeming a code, choosing an early route, comparing units, finding a material, or understanding a reported update. A claim must have a named public source and a check date. If a detail cannot be supported or does not help the reader make a decision, it is left out.

How is the official game identified?

The game link is checked against its Place ID, Universe ID, creator, and group before it is treated as official. That identity check prevents a same-name copy from being used as the source of truth. Readers can compare the fixed identifiers on the official links page.

How are changing facts handled?

Official pages and Roblox records come first for identity and announcements. Public community guides may fill gaps in codes, recipes, drops, and unit advice, but those claims remain labeled as reports. When reliable sources disagree, we show the conflict, narrow the wording, or remove the claim until it can be checked again. The Sources page lists the actual links rather than hiding them behind a generic citation.

How are tier lists edited?

Tier lists are dated comparisons of attributed community rankings, not official or permanent grades. Each publisher's scale remains visible, missing units stay “Not listed,” and unconfirmed DPS figures are not invented to force a single score. Role, deployment cost, team composition, and game mode can make a lower-ranked unit the better choice for a particular player.

What happens when a page is wrong?

A correction is checked against the live game, an official record, or current public reporting. The page is then corrected, marked as disputed, or shortened to the part that can be supported. Its modified date changes only when the public content changes; an automated check that finds nothing new does not create a fresh date.

Send the page URL, the disputed sentence or table row, and a source through Contact. Corrections are evaluated on the evidence supplied, not on whether they agree with the site's previous wording.

How are images and video used?

Official Roblox promotional artwork is used sparingly, stored locally, and documented with its source and access date. The site does not use images copied from competing guides. The release trailer stays on YouTube and loads through the privacy-enhanced player only after a visitor presses play.

What makes a source usable?

A usable source lets another reader inspect the evidence behind a claim. It should be publicly accessible, identify what was observed or announced, and provide enough context to connect that evidence to Anime Expeditions. A current in-game panel can support a recipe or reward; an official Roblox record can support the game's identity; a dated guide can support a community-reported ranking. One type of source should not be stretched to prove a different kind of claim.

• Traceable: the page links to the original public destination rather than an unexplained screenshot or copied summary.
• Specific: the evidence supports the sentence, row, or value beside it, not merely the general topic.
• Dated: readers can tell when the source was published or when the claim was last checked.
• Contextual: the game version, unit form, map, mode, or other condition is recorded when it changes the meaning.
• Reviewable: another editor can repeat the check without needing a private account, private chat, or inaccessible file.

What does a citation prove?

A citation supports only the claim attached to it. An official announcement that names a new unit does not automatically prove that unit's best trait, exact damage, or place in a tier list. Likewise, a current community guide can document an author's tested recommendation without turning that opinion into an official fact. Pages keep those boundaries visible so a strong source for one detail does not lend false certainty to everything around it.

How are facts separated from recommendations?

Names, IDs, visible costs, listed effects, and update announcements are presented as facts when the cited evidence directly shows them. Team-building advice, farming priorities, and tier grades are recommendations. Recommendations should explain the role, resource cost, mode, and source disagreement that affect the choice. They are not written as commands that every player must follow.

How are older checks and translations handled?

An older source can remain useful as a record of what existed at release, but its date and applicable version must stay visible. It is not silently presented as current. When newer evidence changes a material claim, the public page is updated and its modified date changes. A routine check that finds no content change does not make the article look newly written.

Translated routes share the same structured game records as the English pages, which prevents a code, unit name, or identifier from being maintained seven different ways. A localized page is published only when its reader-facing text is complete for that route. Missing translations are not replaced with a thin mixture of English and another language.

What is intentionally not published?

The wiki leaves out private messages that cannot be checked, leaks presented as confirmed releases, account credentials, exploit instructions, copied competitor articles, and invented numbers added to make a table look complete. It also avoids publishing an exact rate, drop chance, damage figure, or recipe when the available evidence is too weak or contradictory. “Not verified” is more useful than a precise-looking guess that wastes a player's resources.

Can payment or promotion change coverage?

No paid placement, affiliate ranking, sponsored unit grade, or link-exchange request determines what appears in a guide. A publisher, creator, or reader may suggest a correction, but the same evidence rules apply to every submission. If the site's funding or commercial relationships change in the future, that relationship should be disclosed where a reader would encounter the affected content.