Esta é a versão em português do Brasil do guia de Bahkruums. Ela preserva os fatos, identificadores, links e limites de evidência do corpus aprovado em inglês; nomes oficiais, teclas e valores em código permanecem sem tradução. Use os links internos desta versão para continuar no mesmo idioma.
This is the single Bahkruums updates tracker. The current first-party record confirms that the experience is labeled Bahkruums [BETA], was created on July 21, 2026 UTC, and showed an updated timestamp of August 6, 2026 UTC when checked on August 7. Roblox does not expose a written Bahkruums changelog through the public game metadata used here, so an updated timestamp is evidence of a publication change, not proof of a particular map, nextbot, balance adjustment, or feature.
The stable official identity is Place 91698952875688, Universe 10539789203, creator OrbitWave Creations, and genre Survival. The description lists Shift Sprint, Q Scream, T Speak, Z Unlock Mouse, G Emote, confirms bhop, and warns that console/mobile are not fully supported.
Latest checkpoint: official metadata checked 2026-08-07 UTC; game
updatedtimestamp was2026-08-06T03:07:35.5061579Z. Complete patch contents still require a developer announcement or dated in-game comparison.
Status atual da beta
[BETA] appears in the official experience name. That label tells players to expect active development and makes dates important. It does not automatically mean progress resets, that every feature is temporary, or that a particular bug is known. Use the current game prompt or creator announcement for those claims.
The Games API reported a maximum of 20 players. Live concurrency, visits, favorites, and votes are dynamic snapshots and are not copied into this evergreen tracker. They can show interest at one moment but cannot explain what changed in a build.
2026-08-06 - Official game metadata updated
Type: First-party metadata checkpoint
The Roblox Games API returned an updated timestamp on August 6. This confirms that Roblox recorded a change to the experience or its published metadata by that time. The public response does not identify the changed files, server behavior, map geometry, entity roster, or user interface.
- Recheck the official description and visible in-game prompts after joining a current server.
- Treat routes, safe spots, bhop behavior, platform controls, and nextbot observations from earlier recordings as version-sensitive.
- Do not turn the timestamp into a numbered patch or a feature list without a creator-owned announcement.
Source: Roblox Games API for Universe 10539789203
2026-07-21 - Experience created
Type: First-party creation record
The same official API reports a created timestamp of July 21, 2026 UTC. This provides the public experience’s origin checkpoint and explains why indexed guides, map lists, and code coverage are still sparse. It does not reveal when private development began or establish a separate release schedule.
- Use current sources rather than assuming a launch-day video still matches the latest server.
- Keep unknown entity names and map labels out of canonical pages until they can be reproduced.
- Treat the beta label as current status, not as a promise about when a full release will occur.
Source: Roblox Games API for Universe 10539789203
What the official description currently confirms
The description provides the most useful written feature baseline. It welcomes players to Bahkruums, gives five keyboard actions, says bhop is possible, warns that console and mobile are not fully supported, and names inspiration from GMod, Hussrooms, and other nextbot games.
That baseline supports the Controls, Guides, Nextbots, and Maps sections. It does not support exact stamina, movement speed, damage, spawn rules, map names, nextbot names, code redemption, rewards, rounds, revives, or escape conditions. Those fields remain omitted instead of appearing as a speculative changelog.
Como verificar uma atualização anunciada
Start with the official Roblox page and creator identity. Record the title, description, and visible update notice. Join a current public server and compare one specific feature: a key action, interface button, route junction, visible entity cue, or platform prompt. A before-and-after comparison is stronger than a video title that simply says “new update.”
Use a five-part record:
- UTC date and, if visible, server or build context.
- Official Place ID and creator.
- Previous observable behavior or wording.
- Current observable behavior or wording.
- Evidence level: Official, In-game verified, Community corroborated, or Community reported.
Do not combine unrelated observations into one patch. A changed map corner does not prove a movement rebalance; a new video thumbnail does not prove a new nextbot; an API timestamp does not prove either.
Páginas para revisar após cada atualização
The Codes page should be checked for a real redeem interface or creator-published string. The Keyboard Controls and Platform Controls need a new test if prompts change. The Bunny Hop guide needs rechecking if landing or sprint behavior feels different.
Nextbot identification and behavior records should be dated against the current server. Map route cards should be walked in both directions after any geometry change. A previously quiet location must return to unverified status if pathing or access changes.
Confiança em uma atualização
- Official: the experience, Roblox API, OrbitWave Creations group, or creator-owned announcement states the change.
- In-game verified: the changed behavior is directly observed in a current server and dated.
- Community corroborated: two independent current Bahkruums sources show the same change.
- Community reported: one relevant current source shows it, without independent confirmation.
- Needs in-game testing: the claim is plausible but not reliable enough to publish as a change.
The tracker does not choose the most exciting claim when sources disagree. It keeps the official checkpoint and labels the disagreement until better evidence appears.
FAQ de beta e atualizações
What is the latest Bahkruums update?
The latest verified public checkpoint is the August 6, 2026 Roblox updated timestamp, checked August 7. No complete written patch content was exposed by the sources reviewed.
Is there a version number?
No official numbered version is published here. [BETA] is a status label, not a semantic version.
Did the August 6 update add a map or nextbot?
The timestamp alone cannot support that claim. A creator announcement or dated in-game comparison is required.
When will beta end?
No release date was verified. Do not infer one from the creation date or update frequency.
Why keep updates on one page?
One canonical tracker prevents thin event pages and conflicting timestamps. Future verified changes can be added to this timeline without creating child routes or an Updates dropdown.
Sources checked 2026-08-07 UTC: official experience, Roblox Universe lookup, Games API, experience media API, and OrbitWave Creations group API. No full creator-written changelog was available in the reviewed public evidence.