King 1x1x1x1 is an official Build and Kill Zombies boss identity. Roblox badge ID 1091825320056581 is named You defeated the King 1x1x1x1, and its description says the player defeated the Hacker Event Great Boss. The badge proves the entity and broad victory result; it does not publish HP, timer, trigger, attacks, phases, team rules, or item rewards.
Check whether the fight is available
Join the official Place, finish any blocked tutorial state, and inspect the current event UI. Look for the exact King name, a countdown, entry action, arena or route, and objective text. Capture the server time and update date.
If a countdown exists, observe what happens at zero. If the King does not appear, do not convert an old community schedule into a current rule. Try another official server once and compare the event panel.
Prepare the car before the trigger
Use a stable saved car with predictable steering, enough fuel for the observed route, protected power and fuel components, and a front weapon or defense that already works against ordinary zombies. Build a separate event version so a failed test does not erase the normal Cash loop.
Avoid stacking untested weapons. One controlled support whose contact and direction are understood is more useful for diagnosis. Use Weapons and Defenses and Best Car Build for the role checks.
First-attempt observation card
Learn phases without guessing
Use the first attempt to see the complete sequence where possible. Record obvious transitions by what the interface and boss behavior do, not by assigning names. On the next attempt, change one response or build feature.
If the fight includes adds, hazards, or a route, record their timing and whether they are required for progress. Describe only what the current fight demonstrates. Treat a route from an older recording as a test lead until it works in a current official server.
Also watch the objective panel during each transition. A disappearing health bar, teleport, or temporary pause is not automatically a defeated phase. Wait for the next explicit objective or victory message, and record where the vehicle and players are moved. This prevents a connection delay or arena reset from being mistaken for a boss mechanic.
Solo versus co-op
The official API reports up to five players per server, but it does not say whether the King scales, how damage credit works, or who receives the badge. A solo result and a group result should be recorded separately.
In a group, assign one variable per role: driver, front contact, support, observation, or another live objective. Record vehicle ownership and the accounts that receive the badge. Do not promise participation credit without a successful test.
After a failed attempt
Identify whether the car failed before reaching the King, lost control on contact, ran out of fuel, broke a critical mount, or survived without useful damage. Fix only that failure and repeat. More speed cannot repair a weak front, and more weapons cannot help a car that misses the trigger.
If the event closes between attempts, preserve the record with date and server context. Do not present the old route as currently playable until another live check succeeds.
Badge and reward check
Open the Roblox badge inventory before and after a victory. Capture the in-game success message and any visible currency or item change separately. The official badge description supports only the Great Boss defeat result.
If an item appears, record its displayed name, source, description, and checked date in the Parts Dex. If a code or shop action was also used, separate that reward from the boss outcome.
Confidence
Boss identity and broad defeat result are Official. Current availability, trigger, schedule, HP, phases, attacks, scaling, participation credit, and rewards are Needs in-game testing as of September 25, 2026.