The official Roblox badge inventory for Tower Creator returned two enabled badges when checked on September 15, 2026: test and You Joined!. Roblox ties both records to Tower Creator Universe 3289847355 and root Place 8646026339. Their enabled state is official, but neither record provides a confirmed player route or trigger. Do not assume that joining, touching an object, finishing a tower, or entering a particular version will award either badge until the result is observed in the live experience.
Current official Tower Creator badge index
Use the Roblox badge ID as the stable lookup key. A display name or icon can be changed or reused, while the numeric ID identifies one record. Dates below come from the official API in UTC; “last checked” records when this guide read that source, not when a player most recently earned the badge.
test
Official Badge ID: 2970884556030037.
Enabled: yes in the official universe response.
Display description: “hey!” The description does not explain a requirement.
Created and updated: August 22, 2026 at 18:17:40 UTC.
Source: Roblox Badges API for Universe 3289847355.
Earn method: not confirmed. The name and description are not enough to infer a trigger.
Last checked: September 15, 2026.
Open the Roblox badge recordOfficial record · unlock route needs testingYou Joined!
Official Badge ID: 578827598938870.
Enabled: yes in the official universe response.
Display description: none supplied by the API.
Created and updated: August 23, 2026 at 00:53:16 UTC.
Source: Roblox Badges API for Universe 3289847355.
Earn method: not confirmed. The title suggests an idea, but it does not prove which place, version, or join condition awards it.
Last checked: September 15, 2026.
Open the Roblox badge recordOfficial record · unlock route needs testingThis is a currently documented index, not a promise that the inventory will always contain exactly two records. Roblox can expose historical or disabled records differently from the enabled universe list, and developers can add, rename, update, disable, or re-enable badges. Recheck the official experience and badge inventory when a guide, video, or old screenshot shows another name.
What enabled status does and does not prove
An enabled badge record tells you that Roblox currently marks that badge as enabled for the Tower Creator universe. It also confirms the badge ID, display fields, timestamps, icon asset reference, and awarding universe returned by the platform. That is strong evidence for the record’s identity.
Enabled does not prove that every public server can award the badge. It does not reveal the required place, script condition, editor version, account state, or whether an award is limited by a temporary problem. It also does not prove that a title describes the actual trigger. For example, “You Joined!” should not be rewritten as “join any server to earn it” until a dated live test or creator-controlled instruction supports that route.
Treat the API description the same way. The short “hey!” description on test is official display text, but it supplies no action. A useful guide must leave the method unknown instead of turning that text into a made-up objective.
Check a badge safely in Roblox
Start at the official Tower Creator experience and confirm Place 8646026339 with creator Boring Tower Studio. Open Roblox’s badge area or the direct record and compare the numeric ID, not only the title or icon. If another page lists a badge with no Roblox ID, use it only as a lead.
Join the current root experience normally. Note the UTC date, the place or version you entered, and whether Roblox shows an award notification. After the session, check the badge record on your profile rather than relying only on a brief popup. If you are deliberately testing a claimed method, change one condition at a time; joining, entering Edit Mode, loading a personal slot, and finishing an obstacle are separate events and should not be bundled into one guess.
Do not run a script, executor, browser-console command, or downloaded program to force a badge. A legitimate Roblox badge is awarded by the experience through Roblox. External tools cannot make an unsupported unlock route trustworthy and may expose your account or violate platform rules.
How to verify a reported earn method
A strong earn-method report names the exact badge ID, Tower Creator place or version, starting state, ordered actions, result, and test date. A video is more useful when it visibly starts from the correct experience and shows the Roblox award, but one clip can still reflect an older server or a trigger that later changed.
Use this verification order:
- Match the reported numeric badge ID to one official record above.
- Confirm the report uses Tower Creator Place 8646026339 or clearly names a creator-supported Legacy or event destination.
- Separate required actions from actions the player happened to perform during the same session.
- Repeat the smallest supported route on an account that does not already own the badge.
- Check the Roblox inventory after the attempt and record the exact time and server context.
- Prefer a creator-controlled explanation or agreement between two independent current demonstrations before calling the route confirmed.
If the badge is already owned on your account, you cannot prove a trigger by repeating it and seeing no second award. Use a current source that shows the unlock on an eligible account or keep the method labeled unconfirmed.
When a badge does not award
First confirm that you do not already own the exact badge ID. Then verify that the badge is still enabled and that you joined the correct experience. A similarly named Roblox game, a Legacy tutorial, or an event-place screenshot may use a different path from the root Tower Creator place.
If a reported route fails, capture the place, version, device, UTC time, badge ID, and actions. Try a fresh public server once when the experience appears healthy. Do not repeat a long build or reset valuable work for an unverified badge claim. Ask through the verified Tower Creator Discord route only after checking the current server rules and without sharing account credentials.
An absent popup is not always a final answer; Roblox delivery or UI can be delayed. Check your badge inventory. Conversely, an old ownership timestamp does not prove the same route works today. Keep “owned,” “enabled,” and “current earn method confirmed” as three separate states.
Historical and disabled badge claims
Community pages may preserve older Tower Creator badge names or unlock stories. They can help locate what to test, but they cannot override the current Roblox record. A historical entry belongs in this index only when its badge ID can be tied safely to Tower Creator and its current state can be checked. Names without IDs, copied icon grids, and undated unlock lists should remain unconfirmed.
Do not interpret absence from the enabled universe response as proof that a claimed historical badge never existed. It only means this page cannot safely place it in the current enabled list from that response. Likewise, do not call an older badge obtainable because a community page still describes its method.
Frequently asked questions
How many Tower Creator badges are enabled?
The official universe inventory returned two enabled records on September 15, 2026. That count is dated and can change, so use the badge IDs above when checking a later result.
How do I get You Joined!?
The official record does not publish an earn method. Its title is not enough to prove that joining any Tower Creator server awards it. Confirm the exact place, server state, and account eligibility through a current live award or creator-controlled instruction.
What does the test badge require?
No requirement is documented in the official record. Its display description is “hey!”, which provides no reliable route. Do not follow invented touch locations or completion conditions without current evidence.
Are disabled or old badges included here?
Only the two records returned as enabled by the official universe endpoint are indexed as current. Historical claims remain separate until a Roblox badge ID and present state can be verified.