Balloon Boy and JJ are the first two records in the original FNAF World Multiplayer badge inventory. Balloon Boy is badge 2124579878 and JJ is badge 2124579962. Both are enabled, and both descriptions state that the named character was unlocked.
Official records
Award statistics are changing snapshots. They do not disclose current route difficulty, character power, or whether the same trigger still works.
Historical walkthrough evidence
Gallant Gaming published a directly relevant video titled How To Get Balloon Boy Badge and JJ Badge in Roblox FNAF World Multiplayer. It is useful because it addresses these exact two target-game records rather than a generic FNAF badge. It is also historical, so use its landmarks and interactions as route leads.
Community-reported historical route. Verify every landmark and interaction in the current original Place before calling the route successful.
Do not begin until the linked experience is Place 5379293691. Pause the video at each transition and compare the current environment. If the map no longer matches, stop; continuing by guessing can send you to an unrelated trigger.
Current verification route
First check your Roblox badge inventory for both IDs. If one is already owned, use the other as the test target. Join a fresh root server and wait for the map and interactions to load. Follow the historical video one landmark at a time, checking that the object, room, path, or interaction still exists.
Perform only the demonstrated interaction. Wait for a Roblox badge notification before moving to the next target. After the notification, open your account’s badge record and confirm the awarding experience is the original Universe.
Return to the character selector and check whether Balloon Boy or JJ becomes visible and selectable. If it does not refresh, rejoin once. Do not repeat the route indefinitely when the badge is already on the account.
Test the two badges separately
Even though the video groups them, these are separate badge IDs. Confirm which notification appears after each trigger. A single notification cannot prove that both were awarded.
If you are playing with a friend, let one player interact first and compare both accounts. Shared server presence may or may not share credit. Swap roles only after identifying the result of the first attempt.
Common problems
No notification appears. Check whether the badge is already owned, verify Place ID, and compare the current map with the historical footage.
Only one badge awards. Treat that as a successful result for one record. Do not assume the second shares a prerequisite or trigger.
The character stays locked. Rejoin a fresh server and check the selector again. Preserve the badge proof separately from current selection mapping.
The route looks different. Stop at the first mismatch and label the old step historical. Do not substitute a location from Multiplayer 2 or the 2026 namesake.
Mobile interaction is missing. Confirm the action prompt works on touch before attempting the complete route. A desktop test can determine whether the issue is UI-specific.
What is confirmed
The exact badge names, IDs, enabled states, descriptions, target Universe ownership, and historical demand for a two-badge walkthrough are confirmed. The official API also preserves creation and update timestamps.
The current coordinates, interaction sequence, prerequisites, server conditions, shared credit, character-selector refresh, moves, and stats need live verification. The historical video is strong enough to guide a cautious attempt, not to guarantee a 2026 result.
After unlocking
Use the Characters Dex to compare the documented roster. Test Balloon Boy and JJ one at a time with the Combat Guide rather than importing their abilities from another FNAF game. Record any current live labels and controls with the test date.
Leave the server normally, return through the original Place, and inspect both character entries again. A badge that persists on the Roblox account but fails to restore its matching selection after a clean rejoin should be reported as a badge-to-roster problem, not as a failed award. Keep the two IDs separate in that report.