Build and Kill Zombies Badges

Roblox’s official badge API listed three badges for Build and Kill Zombies Universe 10741654282 on September 25, 2026. This is a dated official snapshot, not a promise that the list will always contain three or that every enabled badge is currently obtainable.

Official badge Dex

What enabled means

An enabled API record means Roblox has not disabled the badge object at the time of the request. It does not prove the original event trigger is active, the badge can still be earned in every server, or the published description contains the complete objective.

Check the badge on a current account and server. Record the entry action, objective, success message, and inventory award. If the badge is already owned, use another reliable first-party announcement or a clean account observation before claiming a current award path.

Roblox can display the badge record even when an experience-side trigger is no longer reachable. Treat the API record and the live award path as two separate checks. A valid test should name the server date, account’s prior ownership state, exact action, visible confirmation, and resulting inventory state so another player can repeat it.

How to verify the Welcome badge

Join the official Place and finish the opening load. Check the account’s badge inventory before and after. Record whether the badge appears immediately, after a tutorial action, or not at all.

Do not assume “Welcome!” means join-only beyond the official description. The wording is broad, and its exact award trigger can change. Avoid creating a separate tutorial requirement unless the current server demonstrates it.

How to verify an event badge

For Hacker Event 2026, first prove the event interface is currently available. Capture the entry, objective, and award moment. Separate attendance from defeating the King; the API exposes different badge objects for those outcomes.

For the King badge, capture the boss name and end state, then confirm the Roblox badge award. The badge establishes victory but does not establish item rewards, damage credit, phases, or team rules. Keep those fields in the King guide until tested.

Snapshot fields that can change

Award counts and recent win-rate fields are live statistics, so this page does not freeze them as permanent facts. Check the API directly when those values matter. A low relative award count may suggest difficulty or limited availability, but it does not prove either cause.

Names, descriptions, enabled state, and timestamps can also change. Record the check date. If a badge is renamed, preserve the ID as the stable identity and note the previous name rather than creating a duplicate page.

If the API and the in-game wording disagree, quote neither as a complete mechanic. Keep the official ID, save the two labels with their check dates, and wait for a repeatable award result. This is especially important around updates, when old servers and newly deployed servers can temporarily show different interfaces.

Avoid badge mix-ups

Confirm Universe 10741654282 and root Place 105011592530400. A similarly named Roblox game can have badges that look relevant but belong to another developer and loop. Do not import its objectives, icons, or reward descriptions.

Use official IDs when discussing a badge. A community nickname such as “King badge” is helpful only when it maps back to 1091825320056581.

After a new update

Query the official badge list again after the experience timestamp changes. Compare IDs, names, descriptions, enabled state, and created/updated dates. A new badge can signal a new entity, but it does not provide a complete guide by itself.

If a new badge has too little information, add it to a dated known-badges index only after identity is verified. Wait for current gameplay evidence before writing a detailed entity route. Review Updates for the public deployment timeline.

Official source

• Roblox badges API for Universe 10741654282