Discord activity · checked August 1, 2026

Show Roblox on Discord. Choose what follows.

Luczystrap can publish basic Roblox activity to a running Discord desktop client. Start with the game card only; add your Roblox identity or a join route only after you inspect what another person can see.

Recommended first setup: Activity tracking on, Show game activity on, Allow activity joining off, Show account on profile off, server location off, and server uptime off. Then launch one public experience through Luczystrap and inspect the card from a second Discord account.

Set it up →Preview the fields

Written by Luc6iPublished August 1, 2026Updated August 1, 2026Public build 1.4.9

01 / Current contract

Basic presence now. Composer later.

The current repository, recorded UI, and historical code answer different questions. This page keeps those evidence levels separate.

Current claim

Basic Discord presence

The README lists basic Discord RPC as available. Direct RPC depends on a running Discord desktop client.

Use now: enable, launch, inspect, disable.

Historical detail

Fields and privacy switches

Public 1.3 code establishes the older experience, creator/server, timer, images, account and button behavior.

Use as a field map—not a 1.4.9 guarantee.

Roadmap

Presence Composer and fallback

Rule-based composition, privacy filters, and robust behavior when Discord is closed remain planned in the README.

Do not search for controls that have not shipped.

02 / Privacy preview

See the optional fields before enabling them.

This browser-only preview does not read or change Luczystrap or Discord. It illustrates the historical field boundaries.

Preview controls · no local access

What another viewer may seeIllustrative

LZDiscord profilePlaying Luczystrap

Live

RBX

Luczystrap

Experience name

by Creator

00:23 elapsed

DisplayName (@username)

Approx. server context

See game pageJoin server

Discord says custom activity buttons appear only to other users. Use a second account or a trusted friend to verify the real card.

03 / Setup

Enable the smallest useful presence.

The exact current labels may differ because 1.4.9 application source is not public. The December 2025 workflow and historical settings use this dependency order.

Open Discord desktop first

Sign in to the desktop client. Discord documents that direct Rich Presence over RPC does not work through web, mobile, or console clients.

Close Roblox and open Luczystrap Settings

Start from a clean session so the next activity belongs to one launch and one settings state.

Open Integrations

Enable Activity tracking. Historical UI made Discord game activity depend on this master signal.

Enable Show game activity

This is the basic presence switch. Leave server location and uptime off; historical UI treated them as separate optional lookups.

Keep identity and joining off

Leave Show account on profile and Allow activity joining off for the first test. Add one only after the base card passes.

Review Discord Activity Sharing

Discord User Settings → Activity Sharing controls whether other people can see activity. Profile Privacy and per-server choices can narrow the audience further.

Close Settings normally

Reopen once and verify the switches persisted. If they reset, use the settings and mods diagnostic before testing Discord.

Launch one Roblox experience through Luczystrap

Wait until the experience fully joins. Then inspect the real Discord card from another account inside the audience you selected.

04 / Historical field map

Know what each visible line can reveal.

These mappings come from public 1.3 code. Current 1.4.9 fields must be verified on your profile because its application source is unavailable.

Details

Experience name

The older implementation used the Roblox universe name as the main activity description.

Source: UniverseDetails.Data.Name

State

Creator or server type

Public sessions showed the creator; private and reserved sessions used explicit server labels.

Source: ServerType + creator

Timestamp

Session start

The card could show elapsed time and preserve the original start across teleports in one universe.

Source: TimeJoined / RootActivity

Artwork

Game and optional account

A game thumbnail was large artwork; enabling account display could add Roblox avatar and identity text.

Source: Roblox thumbnail APIs

Always in old code

See game page

The historical presence added a link to the current Roblox place page.

Viewer-side button

Optional

Join server

The older join route depended on the joining control and server context. Keep it off by default.

Viewer-side action

Separate lookup

Server location

Historical activity tracking queried ipinfo.io. Geolocation is approximate and not required for presence.

External request

Separate lookup

Server uptime

Historical code used RoValra first-seen data as an estimate, not an authoritative Roblox clock.

External request

Evidence boundary: a field existing in 1.3 source does not prove the same endpoint, value, or reliability in closed-source 1.4.9. Inspect the current output.

05 / Privacy controls

Three products decide who sees the card.

Luczystrap decides what it attempts to publish. Discord decides whether and to whom activity is visible. The Roblox session determines what context exists.

Control	What it exposes	Where to change it	How to verify
Show game activity	Basic game activity card and historical session context	Luczystrap → Integrations	Turn off, restart the session, and confirm the card clears.Required for presence
Show account on profile	Historical Roblox avatar, display name, and username	Luczystrap → Integrations	Leave off; inspect from another account for identity text.Recommended off first
Allow activity joining	A route another viewer may use to join the current server	Luczystrap → Integrations	Leave off; another viewer must see no Join server action.Recommended off first
Share my activity	Whether Discord shares activity at all	Discord → User Settings → Activity Sharing	Test with a viewer inside the chosen Friends/Servers audience.
Profile Privacy	Who can see activity as part of the full Discord profile	Discord → Data & Privacy → Profile Privacy	Test the exact audience; profile and activity controls are separate.
Server-specific activity	Visibility to members through that Discord server	Discord server → Privacy Settings	Remember friends or another shared server may still provide visibility.

06 / Verification

Test from both sides of the profile.

Your own card is not sufficient: Discord documents that custom activity buttons are visible only to other users.

VIEWER A

Your account

Launches Roblox and publishes the activity.

Discord desktop is running
Luczystrap settings persisted
One experience is fully joined

→

VIEWER B

Second account or friend

Checks what the selected audience actually receives.

Experience and state are correct
No Roblox identity when disabled
No Join server button when disabled

Pass condition: the intended viewer sees only the fields you enabled; closing Roblox or disabling game activity removes the live card.

Capture the “off” state

Viewer B opens your profile before Roblox launches. Save no private IDs in the screenshot.

Join one public experience

Wait for the Player log to report a completed join and for Discord to update.

Inspect text, art, timer, identity, and buttons

Check every visible element, not just the presence of “Playing.”

Close Roblox

The historical implementation cleared presence on game leave. Confirm the current card disappears or stops being live.

Enable one optional field

If needed, add account or joining—not both—then repeat the same viewer test.

07 / Signal diagnosis

Find the last line that succeeded.

The log wording below comes from historical public code; current 1.4.9 may phrase it differently. Preserve the current timestamps and first exception.

Roblox session

Player launches and joins an experience.

ActivityWatcher::Start

Game detected

Place, universe, user, and time enter activity context.

SetCurrentGame · Place ID

Metadata fetched

Experience details and optional account image are resolved.

UniverseDetails · UserDetails

Discord connected

The local desktop RPC client accepts the connection.

Established connection

Presence updated

The activity is sent and another viewer receives it.

Updating · Presence updated

No ActivityWatcher or game detection

Launch Roblox through Luczystrap, confirm activity tracking stayed enabled, and inspect the Roblox log path. Use the settings diagnostic if the toggle resets.

Game detected; no Discord connection

Open Discord desktop—not web or mobile—restart Discord once, and look for the first RPC error or lost-connection line.

Connected; no visible card

Check Discord Activity Sharing, Profile Privacy, the exact viewer audience, and whether another activity is taking precedence.

Card appears with wrong or excessive data

Turn off account and joining first, restart the Roblox session, and re-check from Viewer B. Disable presence entirely if the output cannot be constrained.

08 / Disable & clear

Prove the off switch too.

Disabling presence should not require uninstalling Luczystrap, clearing Discord data, or deleting Roblox.

Close Roblox

End the active session so there is no new activity event while settings change.

Turn off Show game activity

Keep activity tracking only if another integration needs it; otherwise turn that master control off too.

Close Settings normally

Reopen and confirm the off state persisted.

Restart Discord desktop once

If a stale card remains, restart both Discord and Luczystrap, then inspect the latest RPC cleanup or connection lines.

Escalate without deleting data

Attach a redacted Luczystrap log, timestamps, viewer result, and whether the card remained after both apps closed.

09 / FAQ

Discord presence questions

Does Luczystrap Discord Rich Presence work with Discord in a browser?

No for the documented RPC path. Discord says direct Rich Presence over RPC requires the running desktop client and does not work through its web, mobile, or console clients.

What can Luczystrap show on my Discord profile?

Historical public code could show the Roblox experience, creator or server type, elapsed session time, game artwork, an optional Roblox account, a game-page button, and an optional join-server button. Verify the current 1.4.9 card because its application source is not public.

Do I need server location or uptime for Discord Rich Presence?

Historical settings treated server location and uptime as separate optional activity-tracking lookups. Leave them off when you only want basic presence.

Can I hide my Roblox account but keep game activity visible?

Historical Luczystrap controls separated game activity from showing the Roblox account. Leave Show account on profile off, then verify from another Discord account that no Roblox identity appears.

How do I remove the Join server button?

Turn off Allow activity joining in Luczystrap, restart the session, and inspect the card from another Discord account. Discord notes that activity buttons are visible only to other users.

Why can I see my activity but my friend cannot?

Discord Activity Sharing and Profile Privacy affect who can see activity, and server-specific controls can narrow it further. Test with a friend or second account that is actually inside the audience you selected.

Does Discord Rich Presence improve FPS or ping?

No reliable source establishes an FPS or latency benefit. Rich Presence publishes session context to Discord; disable it during a controlled performance test if you want to measure its small background overhead.

Is the Luczystrap Presence Composer available now?

The current README lists the rule-based Presence Composer and robust fallback behavior as planned. This guide covers the narrower basic presence path.

10 / Evidence

Sources behind the setup

01Official Luczystrap repositoryBasic Discord RPC claim and planned Presence Composer boundary.↗ 02Historical Integrations settings · 1.3Activity dependency, game activity, joining, account, location, and uptime controls.↗ 03Historical DiscordRichPresence code · 1.3Field mapping, buttons, connection logs, updates, clearing, and cleanup.↗ 04Discord Activity Sharing FAQ · July 2026Global, audience, per-server, profile, and joining visibility controls.↗ 05Discord Rich Presence documentationDesktop RPC requirement, activity fields, and viewer-only buttons.↗ 06Recorded Luczystrap 1.4.9 workflowDecember 2025 UI evidence; FPS and ping claims excluded.↗ 07Luczystrap integrations hubEvidence levels for server data, custom hooks, and multi-instance behavior.→