Sponsored link
KrakeruzzCasefile
Round systems

this is krakeruzz! Maps & Systems

What this is krakeruzz! maps and systems look like in the documented record: the official Survival / 1 vs All frame, the 12-player round container, and the hidden-role loop — with unnamed gaps kept honest.

Reference check 2026-10-06this is krakeruzz maps
Quick answer

The short version

What is documented about the game's systems: Roblox classifies it as Survival / 1 vs All with servers capped at 12 players; each round assigns hidden roles (innocents, a sheriff, a hidden murderer per the trackers); codes add inventory items. Map names, timers, objectives text and spawn rules are not published anywhere in the checked record (2026-10-06).

The record

What the sources document

Every claim in this box resolves to a source on the register: the official Roblox record or a dated community tracker.

The official frame

Two platform facts anchor everything: the official genre tag Survival / 1 vs All (Roblox Games API, checked 2026-07-17) and the server cap of 12 players from the same record. One player against the lobby is the game's declared shape, and a dozen-person server is its declared size.

The round loop

Lawod describes roles being handed out at the start of each round — innocents trying to survive, a sheriff able to stop the killer, and a hidden murderer working through the lobby. That is the system you actually play: assignment, hidden-role survival, resolution, re-queue.

  • Assignment: roles rotate every round; odds are unpublished.
  • Play: deduction and survival in a small lobby where every sighting matters.
  • Resolution: round ends when the murderer is stopped or the lobby falls; exact win-condition text is not published.

Maps: what can and cannot be said

No source — official page, Roblox Den, Lawod or Creator Exchange — names a single map for this universe. Lawod's tips reference the feel of the spaces (open areas versus narrow corridors) without naming them, which matches the format's single-map-per-lobby tradition but is not a map list. This wiki therefore documents the map system as observed through play rather than fabricating a roster.

Systems adjacent to the round

Three systems interact with rounds and are documented:

  • Codes: the official description promises them; three strings are on record, granting inventory items (see the codes page).
  • Inventory: the left-side HUD icon also hosts the EnterCode box — the only documented collection screen.
  • Servers: 12-player cap; Lawod recommends fresh servers so code data is current.

Gaps kept open on purpose

Timers, spawn rules, role probabilities, map counts and names, and overtime mechanics are all unpublished. Every one of these gaps is a standing recheck item: the update page re-verifies them after each game update, and any system the developer publishes gets added here with its source and date.

FAQ

Questions this page answers

How many maps does this is krakeruzz! have?

No map names or counts are published in any checked source. Round maps are observed in-game; this wiki does not invent a roster.

How long is a round?

No round timer is documented. Rounds end when the sheriff stops the murderer or the murderer eliminates enough of the lobby, so length varies with play.

How many players are in a server?

Twelve, per the official Roblox record (Games API, checked 2026-07-17). That cap is the game's only published systems number besides its genre.

Is there a lobby or shop between rounds?

A between-round state exists (codes are redeemed from the Inventory HUD), but no shop, currency or upgrade system is documented for this universe.

Do private servers exist?

Roblox supports private servers platform-wide, but this game's private-server price and behavior are not documented in the checked record — check the official page's server section for the current offer. The 12-player cap is the one published party number.

Related pages

Hand off to the decision pages

Each link goes to the page that turns this topic into a next action.

All wiki pagesSources registerEditorial policy