How We Verify Pokebonk Guides

Pokebonk (officially styled PokéBonk) is a free browser game that changes fast: the official version file moved from Beta v0.7.2 to v0.8.62 in about ten days. A guide that was right last week can be wrong today. This post explains how we check what we publish, and how to read the version and evidence notes on our pages.

Where our facts come from

We rank sources by how directly they show the game’s real behavior. Every guide states which of these it relies on.

Source	What it proves	What it does not prove
Official announcements (the developer’s news feed and in-game notices)	What the developer says changed, and when	How the change plays in a real run
Official game client (the code the official site serves, matched to the official version file)	Default controls, mode rules, item and move data at that build	Balance over a long run, or behavior on a specific phone
Dated screenshots and play notes from our own runs	What a menu or screen looked like on that day and version	That the screen still looks the same after a later patch
Community reports and videos	That other players see something	Anything, on their own — we cite them and label them as unconfirmed

What the labels on our pages mean

• Game version badge. The version shown at the top of a guide is the build the page was last checked against. If the live game is newer, treat specific numbers as possibly out of date.
• “Checked on [date]” notes. These name the exact source and date, for example a check of the official client on 26 October 2026 (UTC).
• “Not playtested” / “Untested”. We use these words when a fact comes from code or an announcement but we have not seen it in a real run, such as co-op on every account or performance on mobile hardware.
• Historical screenshots. Older images stay when they still show where something is, but the caption says which beta they come from.

How a check works in practice

1. We read the official version file to see which build is live.
2. We compare the guide’s claims against that build’s official client or the latest official notice.
3. Where a claim needs play to confirm, we test it in the game and record the date and version, or we mark it as untested.
4. For larger guides we publish the evidence itself. Our Mew and Moltres boss guides come with a public evidence file that lists each source, when we retrieved it, a fingerprint of the file, and what we did and did not conclude from it.

What we will not do

• We do not invent codes, drop rates or “best” rankings. Our codes page lists only codes we can source.
• We do not host or embed the game. Pokebonk runs on the official site, pokebonk.com ; our Play page explains how to open it and how to spot copies.
• We do not present community opinion as official. When we rank starters or builds, we say whose method it is.

Found a mistake?

If the game no longer matches a guide, check the version badge first, then tell us at support@pokebonkwiki.com with the page, your game version and what you saw. We correct pages and update their dates. You can see recent changes on the patch notes page.