Public evidence issue tracker
BOMBANANA! Known Issues and Hot Fixes
Last updated: July 8, 2026
Not every problem you hit in BOMBANANA! is the same kind of problem. This page sorts them into three buckets so you know what to expect: issues the developer has already marked fixed, issues that are still only player-reported, and situations that look like bugs but are actually rules being misread. Knowing which bucket you are in changes what you should do next — and whether a report is worth filing.
Everything here is anchored to public evidence: the game's official Steam hot-fix notes and player reports from community channels. Where a fix has shipped, this page says so and names the update. Where an issue is only player-reported, it says that too, rather than presenting a guess as a confirmed defect.
How to read this page
Before you file a report or spend an evening troubleshooting, place your problem in one of these three buckets:
- Officially fixed. The developer listed it in a hot-fix note. If you still see it, update the game first — the fix may not have reached your build yet.
- Player-reported. Players describe it, but no developer note confirms a fix or even a shared cause. Treat these as open, and worth reporting with detail.
- Rule misread. The game is behaving as designed; the confusion comes from a manual, a language setting, or a role mismatch. No bug to file — just a step to recheck.
Official update timeline
These are the dated, developer-published milestones. Use them to check whether your build is current before assuming an issue is unfixed.
| Date | Update | What it means for players |
|---|---|---|
| June 14, 2026 | Steam Next Fest live stream | Promotional appearance, not a patch — no gameplay changes tied to this date. |
| June 16, 2026 | Hot Fix (six items) | The core bug-fix batch this page tracks: manual text, lobby join, voice delay, emote texture, and mute vision. |
| July 3, 2026 | macOS support added to the demo | Mac players can now run the demo and play alongside Windows players; this is a platform addition, not a bug fix. |
Officially fixed items
Each row below appeared in the June 16 hot-fix note as fixed. The "try this" column is what to do if you still see the symptom, and the "do not assume" column is the reading that keeps you from filing a duplicate or a false report.
| Fixed issue | Fixed in | If you still see it, try this | Do not assume |
|---|---|---|---|
| Italian manual white pages and Italian "Calculation Module" text | June 16, 2026 Hot Fix | Update the game and reselect the language, then reopen the manual before assuming the pages are still blank. | A blank page returning after the update is new evidence worth reporting, not proof the old fix was reverted. |
| Lobby join network issues | June 16, 2026 Hot Fix | Update all three players to the current build, recreate the lobby, and resend the Steam invite. | A current join failure is more likely a mismatched build or a fresh network case than the specific issue this fix closed. |
| Voice chat delay | June 16, 2026 Hot Fix | Update first, then check Steam voice settings and the Windows input/output device before changing anything in-game. | Lingering delay after updating points at Steam voice, a local device, or the connection rather than an unfixed game bug. |
| Emote wheel texture stuck | June 16, 2026 Hot Fix | Update and restart the game; if the wheel sticks again, note the role and whether it stayed after closing. | This is the texture bug only — it is separate from feedback that emotes feel slow or cannot be cancelled. |
| Mute player blurry vision | June 16, 2026 Hot Fix | Update and recheck as the Mute player; if blur returns, record the module context and timing before reporting. | The public note does not state the original trigger, so a similar blur may be a different cause entirely. |
Player-reported issues
These come from player discussion, not developer notes. None is confirmed fixed, and in some cases the underlying cause is not confirmed either. The "how to read it" column separates what players observe from what the evidence actually supports.
| Report | Where it shows up | Try this first | How to read it |
|---|---|---|---|
| Friends cannot join a lobby, or invites do not connect | Player help threads after the June update | Confirm every player is on the current build, then rebuild the lobby and resend the invite from Steam. | The June 16 fix targeted a specific lobby-join network case. A current failure is player-reported until a developer note ties it to the same cause. |
| Voice chat still feels one-sided or delayed after updating | Scattered player comments | Recheck Steam voice settings and the Windows input/output device; test with one known-good headset before blaming the game. | With the delay fix already shipped, remaining reports more often trace to Steam voice or a local device than to an open game bug. |
| Emotes feel slow to trigger or hard to cancel | Player feedback, distinct from the fixed texture bug | Note whether the wheel is stuck (a texture symptom) or simply feels sluggish (an input-feel report), since only the first was addressed. | This is feedback on feel, not a confirmed defect. The June 16 fix was the stuck texture, not emote responsiveness. |
Lobby and voice checklist
Lobby joins and voice chat are the two areas players most often mistake for open bugs after they have already been fixed. Before you report either, run this checklist — most current cases clear at one of these steps.
- Confirm all three players have updated to the current build. A single stale client is the most common join failure.
- Rebuild the lobby from scratch and resend the Steam invite rather than reusing an old session.
- For voice, check the Steam voice input/output device and the Windows default device separately — they can disagree.
- Test voice with one known-good headset before concluding the game is at fault.
- If a problem survives all of the above, that detail — build number, what you already tried — is exactly what makes a report useful.
Calculator and manual confusion
The Calculation Module is where a rule misread most often gets mistaken for a bug. The June 16 fix corrected wrong text in the Italian manual page — not the module's logic. That distinction matters, because the two failure modes look identical from the operator's seat.
If the numbers do not resolve, work through the misread path before the bug path. Confirm the manual's language setting, then confirm the manual reader and the bomb operator are looking at the same module. A manual in the wrong language, or two players on different modules, produces the same "the calculator is broken" feeling that an actual defect would — but resolves the moment the manual and the bomb are matched. Only after those checks does a mismatch become worth reporting.
What this page is not
This is an evidence tracker, not a live bug database or a support desk. It does not host patch downloads, betas, or unofficial builds, and it does not promise that a fixed issue can never resurface. For anything not covered by a public note or a player report, the honest answer is that there is no confirmed information yet — and this page will say so rather than fill the gap with a guess. For account, purchase, or platform problems, Steam support is the correct channel.
Known issues FAQ
Are the June 16 hot-fix issues gone for good?
For the five items in that note — Italian manual pages, the Italian Calculation Module text, lobby join network issues, voice chat delay, the emote wheel texture, and mute-player blurry vision — the developer marked them fixed. Update the game first. If a similar symptom returns after updating, treat it as new evidence to report rather than proof the fix was reverted, because the public note does not describe the original trigger.
My friends still cannot join. Is that the known lobby bug?
Not necessarily. The fixed issue was one specific lobby-join network case. A current join failure is more likely a build mismatch or a fresh network problem: confirm all three players are on the same current version, rebuild the lobby, and resend the invite before assuming it is the same bug.
Does the Calculation Module confusion mean the module is broken?
Usually no. The fixed item was wrong text in the Italian manual page, not the module logic. If the numbers do not work out, first confirm which language the manual is set to and that both the manual reader and the operator are reading the same module. A rule misread looks like a bug but resolves once the manual and the bomb are matched.