BOMBANANA sources: know where every claim comes from

This wiki separates BOMBANANA evidence into official, platform, data-backed, community-tested, and outdated groups. Official sources establish the game identity, developer, publisher, release state, modes, supported platforms, and advertised features. Steam platform pages establish achievement names and visible requirements. Structured third-party data can fill a compact level or module table, but it does not become an official manual merely because it is machine-readable.

Community BOMBANANA guides are most useful for callout order, team routines, and publicly shared tables. They are cited as community evidence because live rules may change and because a guide author is not the developer. Outdated sources remain visible only when they explain a contradiction. Keeping the old claim beside the current baseline makes the correction auditable and prevents another editor from reintroducing demo information later.

The current BOMBANANA baseline is the September 2, 2026 full release on Steam. The store describes a three-player cooperative game with Campaign, Endless, and Custom modes, support for Windows and macOS, asymmetric Blind, Mute, and Deaf roles, environmental hazards, voice chat, color-blind options, and Steam achievements. The Campaign data used here contains 30 numbered levels, while the module collection contains 11 defusal modules and three ongoing Chaos modules.

Every dated statement has a checked-at value. A date does not prove that a BOMBANANA rule is permanently correct; it tells a future editor when the claim was last compared with its source. Store pages and platform records can change without notice. When a patch alters a timer, slot, module name, achievement requirement, or system requirement, update the affected entry and its check date rather than changing the global date for untouched pages.

When two BOMBANANA sources disagree, the newer source does not win automatically. First compare scope: one page may describe a demo, another the full release, and another one platform. Then compare authority and specificity. A current Steam listing outranks an old fan launch estimate for release state, while an observed in-game level table may contain details the store never promises. Record the conflict instead of averaging incompatible numbers.

A claim is excluded when its context cannot be reconciled. Examples include pre-release statements that BOMBANANA was coming in August, supported only Windows, required 2 GB of memory, had no announced price, or stopped Campaign at seven levels. Those statements may have been accurate for an earlier page state, but they are unsafe navigation for a full-release guide. The outdated label preserves provenance without presenting the claim as current advice.

A polished table can look authoritative even when its BOMBANANA cells were inferred. This wiki publishes a compact mapping only when a traceable public source provides it and the table fits the current procedure. For modules without that evidence, the page documents identification, required inputs, callout order, stage handling, and verification, then directs the player to the in-game manual. An incomplete honest page is safer than a complete invented answer sheet.

Community confirmation still has value. Independent descriptions can reveal that several groups use the same input order or recovery habit. That supports a BOMBANANA procedure, not necessarily every output in a hidden rule matrix. Evidence labels let readers decide how much to rely on a statement during a live attempt. They also give maintainers a clear upgrade path when an official manual or reproducible table becomes available.

The BOMBANANA key art, gameplay screenshot, and three-monkey application icon used by this site come from Steam assets associated with App 4656000. They identify the subject of the guide and remain the property of the game’s rights holders. The favicon is derived from the official Steam client icon rather than a third-party logo search result. Alt text describes what a reader needs to understand without stuffing image fields with repeated keywords.

The information architecture is inspired by AnvilWiki, an MIT-licensed open-source game-wiki template. This project keeps its existing Vinext, React, Tailwind, and daisyUI stack and reimplements the useful patterns: a compact header, direct search, start cards, breadcrumbs, readable article widths, and an on-page contents rail. No AnvilWiki application code or representational artwork is copied into the BOMBANANA site.

Readers can follow each external link to inspect the original context. That audit trail is especially important during the first weeks of the BOMBANANA full release, when old demo pages and rapidly updated platform records may appear together in search results.

When in doubt, favor the narrower claim that a reader can verify directly and record what evidence would be needed to strengthen it later.

• Prefer the current official source for identity and release facts.
• Use platform records for platform-controlled data such as achievements.
• Label structured fan data instead of presenting it as a developer manual.
• Keep community tables linked, dated, and limited to what they support.
• Retain stale BOMBANANA pages only to document why a conflict was rejected.