Reference hub // checked 2026-08-13

Bahkruums wiki

Bahkruums is a Roblox beta experience published by OrbitWave Creations. This unofficial wiki currently verifies identity, five keyboard controls, bhop support, incomplete mobile and console support, and the developer-stated inspirations; undocumented maps, encounters, stats, and completion rules remain open research items.

Verified facts firstBrowse the guide index
Official Bahkruums game icon from the Roblox experience page
Official Roblox experience icon; source checked 2026-08-13.
Guide index

Choose the page that matches your question

Each page has one job so controls, first-session advice, movement, compatibility, and code status do not compete with one another.

Published record

Facts supported by the official listing

These statements are kept deliberately narrow. Follow the source page when a live beta update conflicts with this snapshot.

  • The official title is [QoL] Bahkruums [BETA].
  • The experience is published on Roblox by OrbitWave Creations.
  • Bunny hopping (bhop) is supported.
  • Console and mobile support are not fully implemented yet.
  • The game is strongly inspired by GMod, hussrooms, and other nextbot games.
Input index

Five published keyboard actions

The wiki records the labels; the controls page handles usage limits and troubleshooting.

ShiftSprintHold Shift to sprint.
QScreamUse the scream action.
TSpeakUse the speak action.
ZUnlock mouseRelease the mouse from camera control.
GEmoteOpen or trigger the emote action.
Open controls reference

Open research

Not yet verified

These topics need official evidence or repeatable current-version play before they can become factual wiki entries.

  • exact nextbot behavior, spawn rules, or encounter values
  • map layouts, hidden rooms, or item locations
  • stamina, speed, damage, or other numerical stats
  • a public code redemption system or redeemable code strings
  • a complete console or mobile control layout
  • an official wiki, Trello, or strategy guide

Entry standard

When a topic deserves its own wiki page

  1. 1.It answers a distinct player question rather than repeating another guide.
  2. 2.Important claims have an official link or documented current-version test.
  3. 3.Screenshots or video show the relevant screen, route, or behavior.
  4. 4.The test device, date, and beta version context are recorded.
  5. 5.Unknowns and conflicting observations remain visible.
  6. 6.The entry links to the relevant controls, beginner, platform, and source pages.