Connect Dex Hood.

Configure the game connection and staff accounts to enable real rankings, Discord sign-in, and shared tags.

1. Install the game update

1. Back up your main Dex Hood place and stop Play/Test in Studio. Keep working in your main file; do not open an older replacement place.
2. Download the native TagStyles installer, copy all its text, and paste it into Studio’s edit-mode Command Bar. Output displays the result; the live F9 console is not the installer.
3. Look for DEX_NATIVE_TAGS_INSTALLED. The installer backs up the dashboard scripts under ServerStorage/DexNativeTagBackups and leaves ReplicatedStorage.TagStyles, PlayerScriptsLoader, and EmojiHandler unchanged. If it aborts, keep the error and do not bypass the checks.
4. Test it in Studio first. Y opens the Tag Panel with actual native style previews, without a corner shortcut. The old U menu stays disabled. Existing staff permissions remain in force. Studio API access uses real game data when enabled.
5. Publish the reviewed main file to the existing Dex Hood experience. Join a new server; running servers must restart to load changed scripts. The game publishes its native style list and checks website tags about every 60 seconds.
6. Sign in here, open Tag Panel, and select Reload styles. Pick a native style and save a test tag for your player ID. Check it from a second player, since your existing renderer can hide your own nametag. Test editing, disabling, deleting, re-equipping, and respawning.

If you need to undo the game update, the rollback script restores the latest installation backup and refuses to overwrite later source edits. It does not undo website publication.

2. Connect Roblox data

In Roblox Creator Hub API keys, create a dedicated Open Cloud API key restricted to Dex Hood (universe 10734956839). Select these permissions:

• universe.ordered-data-store.scope.entry:read — read the ordered leaderboards for this experience.
• universe-datastores.objects:read, universe-datastores.objects:create, and universe-datastores.objects:update — restrict all three to DexDashboard_v1 in this experience. Create Entry is needed for the first tag save.

Start an updated game server first so it creates the shared data store. The website does not need permission to delete data stores, write leaderboard scores, or publish places. If you set an expiry, plan to rotate the key before it expires. Follow Roblox’s API key guide for key management.

Add the key to the website host’s secrets as ROBLOX_OPEN_CLOUD_KEY. Do not put it into game scripts, browser code, a public repository, or the dashboard login form.

The site reads BoardLB_Stomps_v2, BoardLB_Wanted_v1, and BoardLB_Playtime_v1. It reads/writes only DexDashboard_v1 for managed tags; it does not edit player inventory, cash, bans, or legacy tags.

3. Set up staff sign-in

Create a Discord application and add this exact callback URL under OAuth2 redirects: https://dexhood.net/api/auth/callback. The site uses identify plus guilds.members.read when role access is configured. It does not need a bot token or a bot installed in your server.

• SITE_ORIGIN — the exact HTTPS site origin, with no trailing slash.
• DISCORD_CLIENT_ID and DISCORD_CLIENT_SECRET — from the Discord application.
• ROBLOX_ASSETS_KEY and ROBLOX_ASSET_GROUP_ID — optional. A second Roblox key with the asset:write scope, created under the group that owns the game, so staff can upload crew style icons. Without it, staff paste an approved asset ID instead.
• DISCORD_GUILD_ID — one or more Discord server IDs, comma-separated (up to 10). Staff in any listed server manage the same single Roblox game.
• DISCORD_STAFF_ROLE_IDS — comma-separated role IDs allowed to manage tags, checked against whichever listed server the user belongs to. The site rechecks role membership before staff reads and writes.
• DISCORD_STAFF_IDS — optional fallback for explicit user IDs when role access is not configured.
• SESSION_SECRET — a new, randomly generated secret of at least 32 characters.
• Optional DASHBOARD_API_KEY — a separate randomly generated 32+ character owner login key. Keep this private and separate from the Roblox API key.

4. Link tag authors to Roblox

Roblox needs the real author’s Roblox user ID to filter tag text before displaying it. Set DISCORD_ROBLOX_IDS to a JSON mapping of each authorized Discord account to its Roblox user ID. With role-based access, the Discord account still needs a mapping even though the role grants access:

{"DISCORD_USER_ID":"ROBLOX_USER_ID"}

If you use the owner dashboard key, set DASHBOARD_ROBLOX_USER_ID to the key owner’s Roblox user ID. In-game saves automatically use the staff member’s actual player ID. If Roblox cannot filter the text, that tag stays hidden until filtering succeeds; the author may need to join the game. The local preview does not bypass filtering.

5. Verify before sharing

For local Discord testing, set the local SITE_ORIGIN to http://localhost:3000 and register http://localhost:3000/api/auth/callback as an additional Discord redirect. Start and finish sign-in on the same site; a localhost session cannot return to the hosted site. Keep the production origin set to the production HTTPS address.

1. Restart the local server or apply the host’s environment settings with a new publish.
2. Turn off “Sample data.” Check real leaderboard results and the heartbeat in the staff dashboard.
3. Save a harmless test tag for your own Roblox player ID. Check its appearance in a new game server. Test editing and deleting it, then check the audit log.
4. Test that a non-staff Discord account and a non-staff game player cannot save tags. Concurrent edits must prompt the second editor to reload.

Tags created here use native TagStyles keys and the existing game renderer. Equipped and crew tags remain intact. The retired custom-gradient registry is archived, not rendered by the new bridge. Re-create any old website tags that you want to keep by selecting native styles. The browser shows a text preview; exact animations and decorations run in game.

The current site is private to its owner. If you move it to your own Cloudflare account, configure the new site address and Discord callback URL before signing in. Review who can view the site; staff actions always require an authorized account.