Contribute

Anyone can propose a change to GachaWiki. Edits go through review before publication, because this site promises verified content rather than instant content; the trade is deliberate. Every published change is recorded as a numbered revision with the editor and an edit note, and each page shows its full history under "Revision history" in its tools panel.

Three ways in

1. Report an error. Use "Report an error" on any page, or open an issue directly. Include a link to a primary source that supports the correction; sourced reports get fixed fastest.
2. Suggest an edit or a new page.Open an issue with the proposed text and its sources. The "View as Markdown" link on any page gives you the exact format to follow. A reviewer checks the sources, applies the change, and credits you in the revision note.
3. Send a pull request. Every page is one markdown file under content/ in the public repository, frontmatter plus body, and the build gates check style, schema, sources, and links before anything can merge. The build also records a numbered revision for every change, so nothing lands silently.

Honest mechanics: an issue or a pull request is a proposal, not a published revision. It becomes part of the wiki when a reviewer verifies the sources and the change ships in a build; until then it stays visible, in public, as exactly what it is.

The sourcing checklist

A submission is ready when you can answer yes to all of these:

• Every factual claim is supported by an entry in the page's sources list, or by inline citation.
• Sources meet the sourcing hierarchy: publisher and government sources first, no content farms.
• Community-measured numbers (soft pity and similar) are labeled as community-documented.
• Rates and pity values match the game's current in-game disclosure, and date fields are updated.
• Anything you could not verify is omitted or explicitly marked, never guessed.

Style, briefly

• Encyclopedic register: describe, do not promote. Plain sentences beat clever ones.
• Sentence case headings. Straight quotes. No em dashes, anywhere, ever.
• Link generously to other wiki pages on first mention.
• Dates in ISO form (2026-07-09) in data fields; natural phrasing in prose is fine.

The build enforces part of this automatically: pages without required metadata, verified pages without sources, em dashes, or leftover draft placeholders fail the build and cannot be merged.

What needs doing

• Pages marked stub or partially verified need sources and expansion; the newest games need their in-game rate disclosures transcribed.
• Re-verification: any verified page whose "facts checked" date has aged a year needs a fresh pass.
• Missing games and terms: if it has a pull system and players, it belongs here eventually.

On-site editing

Not there yet: editing in the browser with lightweight accounts is on the roadmap. The content already lives in plain, reviewable files, so the path exists; what a live editor would need is the same thing every other route needs, a human checking sources before publication. Until then, the issue tracker is the lowest-friction path, and a plain-text description of the problem with a source link is a complete, welcome contribution.

By contributing you agree to license your text under CC BY-SA 4.0.