Project: Afternight tags are player-facing labels or identity decorations discussed in search suggestions and community customization references. A tag may communicate progression, participation, a role, an event, or another status, but its exact meaning comes from the current game—not from its color or a copied name.
No first-party public API exposed a complete tag inventory or unlock table during the September 6, 2026 check. Use this guide to build a current, cautious tag index from the live interface.
Confirm what the current UI calls a tag
Open the official Place and inspect the current customization, profile, or shop interface. Record the exact category label. Distinguish a selectable player tag from a Roblox display name, chat tag, group role, staff label, Badge, title inside another game, or decorative icon.
Do not promise that a tag appears in chat, above the avatar, on a result screen, or inside a match until you observe that location. One item can have a preview without being visible in every game mode.
Read the tag’s current status
For one selected tag, capture name, description, visual style, locked/unlocked state, requirement, availability note, and equip button state. If the item shows a source song, event, role, achievement, date, or performance condition, keep every part together.
Never infer privilege from appearance. A bright color, unusual border, or “developer-style” word does not grant moderation powers. Official staff identity should be verified through current Roblox group roles or first-party announcements, not a player-created imitation.
Use a status-first tag index
Available
Visible in the current interface and selectable by the tested account.
Locked
Visible with a current requirement that has not been completed.
Role or event limited
Only use when the live description or first-party announcement states the restriction.
Not found
Known from an older lead but absent from the checked interface; not proof of permanent removal.
Changed
Name, style, requirement, or display differs from the dated older entry.
Verification required
Search or community mention exists, but no current UI observation confirms it.
This makes the list useful even when exact historical details are incomplete.
Verify an unlock requirement
If the tag requires a song or performance result, confirm the current source chart, difficulty, key count, rate, modifiers, accuracy, and combo wording. Do not borrow numbers from Roblox Badges or animation rules. Each system can define its own condition.
Use Shop Unlocks to record the attempt and Accuracy and Full Combo when the requirement names performance. If the source song cannot be found, label the tag unresolved and check Updates before attempting a substitute.
If the tag is tied to a community role or event, use only a current official description. Joining an unofficial Discord, paying a stranger, or sharing account access should never be required.
Equip and locate the tag
After unlocking or selecting the tag, use the current equip/save action. Check whether the interface marks it active. Then look in each relevant location separately: lobby identity, avatar overhead display, chat, speaker or stage, and result screen.
Record only the locations where it appears. If it is hidden in one mode, that does not automatically mean the equip failed. Some interfaces reduce labels for space, especially on mobile.
Build a tag card
Each verified card should include:
- Exact current tag name and short description.
- Appearance described in plain language, without unsupported status claims.
- Source and complete requirement, or blank when unknown.
- Locked, available, equipped, role/event-limited, changed, or not-found status.
- Where it was observed in the interface.
- Device, account eligibility context, and checked date.
- Link to a current official announcement when the tag is event or role based.
Avoid a wide desktop-only spreadsheet. Cards keep long requirements readable at 320px and let unknown fields stay visibly blank.
Troubleshoot a tag that did not unlock
Reopen the current item and compare its full wording with your result. Confirm song identity, difficulty, key count, accuracy, Full Combo, modifiers, event window, and role requirements only when they are actually listed. Save the result screen.
Check whether the tag unlocked but needs manual equipping. Try a fresh server after preserving the visible condition. If a time-limited event is involved, verify the current dates from an official source and do not assume another time zone or automatic extension.
Troubleshoot a tag that is not visible
Confirm that the intended tag shows active in the customization screen. Unequip and re-equip once if the current UI supports it. Test in a simple lobby and one normal song. Remove only conflicting display options one at a time.
If it appears on desktop but not mobile, record the exact interface location and device rather than declaring the tag unsupported. A compact mobile UI may hide labels in one view. If it disappeared after an update, use an official support route with the tag name, date, device, mode, and screenshot that contains no private data.
Avoid scams and impersonation
Never provide a Roblox password, cookie, authentication code, or session token to receive a tag. Avoid executor scripts, “staff tag” downloads, and paid unlock offers. Do not use a similar-looking label to impersonate Dawndreamer Studios, moderators, or event winners.
The official developer identity is the Roblox group Dawndreamer Studios, Group 17371285. Use the Roblox Group guide to verify that identity.
Keep the list current
Date both the requirement check and the display check. Move entries between statuses only after a current observation or first-party announcement. Community pages can supply search leads, but their age and completeness must remain visible.
For neighboring customization systems, see Animations, Custom Icons, and Outfit IDs. A trustworthy tag page is small enough to verify and clear enough that a player knows exactly what remains uncertain.