Feature diagnosis · checked August 1, 2026

Find where the change stopped.

When Luczystrap opens and Roblox launches, do not erase a working installation because one setting, profile, mod, font, cursor, Discord status, plugin, or FastFlag is missing. Find the last checkpoint that passed.

Start here: make one distinctive change, close Settings normally, reopen it, then launch Roblox once through Luczystrap. A value that survives reopening was saved; it may still fail later during profile selection, deployment, allowlist evaluation, or rendering.

Choose the symptom →Settings not saving Run the 10-minute test

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

01 / Symptom router

Describe the observation, not the suspected cause.

Select the closest result. This tool stays in your browser; it does not inspect or upload local files.

What do you see?

Persistence failureCheckpoint 02

Prove one write before changing permissions.

Close Roblox. Change one recognizable option, close Settings normally, then reopen it. If the value reverted, the problem is before Roblox deployment.

First evidenceLatest Settings save lines and the full target path.

Isolation moveTest one ordinary setting and preserve Settings.json.

Next: Run the dedicated write test; route an exact error only after the failed checkpoint is known.

Open settings save diagnosis →

02 / Failure model

A checkbox is only checkpoint one.

Current 1.4.9 issue logs show configuration saves, profile loading, plugin discovery, modification application, and Roblox start as separate operations.

01 / UI

The control changed

A switch, picker, import, or profile selection changed inside this Settings session.

Test: read the value before closing.

02 / PERSIST

The choice survived

The same value returns after reopening and the log records a completed save.

Test: reopen; inspect save path.

03 / STAGE

The output was applied

The active profile was used and the resource, integration, plugin, or config reached its target.

Test: inspect profile and deployment lines.

04 / CONSUME

The target used it

Roblox rendered the asset or accepted the flag; Discord displayed activity; the plugin ran.

Test: observe one repeatable outcome.

A recent file timestamp proves checkpoint 02. It does not prove checkpoints 03 or 04.

03 / First ten minutes

Keep the working baseline visible.

Complete this evidence-preserving sequence before a clean reinstall.

Stop immediately if an error names a specific file or operation. Copy that exact path and use the matching guide.

Close Roblox; keep Luczystrap installed

A running client can lock resources and blur a deployment test.

Record build and active context

Save Luczystrap version, selected profile, Roblox version from the log, and installed or portable mode.

Preserve the newest log

Copy it before another launch rotates evidence. Use the log finder if needed.

Choose one distinctive change

Do not test a flag pack, font pack, cursor, plugin, and profile together.

Test persistence

Close and reopen Settings. In the log, find the corresponding Save complete!.

Launch through Luczystrap once

Confirm the log reaches current-version identification and the relevant deployment or integration stage.

Remove only the failing layer

Return one category to Default, disable one plugin, or test one allowed flag.

Restore or escalate with evidence

Report the last successful checkpoint and preserve the state you tested.

04 / Result matrix

Let the first failed checkpoint choose the move.

Use the observation you can reproduce, not a guessed root cause.

Observed result	Failed checkpoint	First evidence	Next move
Value resets after reopening	Persistence	Settings save result and full path	Preserve `Settings.json`; inspect the exact write error.
Value persists; another profile is active	Selection / staging	Profile name before and after relaunch	Test one profile and one setting; do not merge all profiles.
Mod worked before a Roblox update	Staging / consumption	Version ID and ApplyModifications result	Test stock output, then reapply one compatible resource.
Only one font, cursor, or crosshair fails	Consumption	File source and exact target error	Test one trusted local file; route a named access error.
Discord stays blank while Roblox runs	Integration	Discord state and activity watcher lines	Restart Discord desktop; launch through Luczystrap.
Plugin count is zero	Discovery	PluginManager count and path	Verify the active plugin location; isolate only that package.
FastFlag file updates; behavior does not	Consumption	One flag and current allowlist	Check the allowlist; a timestamp is not acceptance.
Core Roblox launch also fails	Earlier layer	First exception and full path	Return to symptom-first help.

05 / Category checks

Repair only the layer that failed.

Each category needs different proof. “Enabled” is not enough.

Settings & profiles

Prove save, then selection.

Release 1.4 introduced profiles. IXP is explicitly excluded, so do not use an IXP result to judge profile switching.

Change one ordinary setting.
Reopen and verify persistence.
Confirm the intended profile.
Repeat without another import.

Understand profiles →

Mods, fonts, cursors & crosshairs

Separate the persistent source from the deployed copy.

Historical public code stages modifications under Luczystrap’s data root. Release 1.4 says cursors transfer to a new version folder, but a current failure still needs the deployment result checked.

Return this category to Default.
Confirm one stock launch.
Reapply one trusted resource.
Route a named CustomFont.ttf error.

Review customization →

Discord presence

Test today’s basic path.

The current README says Discord must be running. The presence composer and closed-Discord fallbacks remain planned.

Open Discord desktop.
Enable activity tracking.
Launch through Luczystrap.
Inspect activity watcher lines.

Review integrations →

Plugins

Discovery is not loading.

Current logs show a Plugins directory, discovery count, and loading stage. A zero count and a later exception are different failures.

Record count and path.
Remove only the suspect plugin.
Verify core launch.
Return only trusted code.

Review plugin trust →

FastFlags

Saved is not accepted.

Luczystrap can write ClientAppSettings.json while Roblox ignores a local flag outside the current allowlist.

Preserve the current file.
Remove packs and conflicts.
Test one allowed key.
Reset if Roblox regresses.

Open FastFlags help →

06 / Permission boundary

Route the exact object, not the whole disk.

If the log says access denied, read-only, or blocked write, preserve the full path and choose the narrow guide.

JSONClientAppSettings.json access deniedClassify working copy, deployed copy, and full path.→ TTFCustomFont.ttf access deniedIsolate read, replace, remove, or deployment stage.→ CFAControlled Folder Access blockConfirm a matching Windows Security event first.→ ACLAnother file or permission errorClassify process lock, NTFS, version, or security control.→

07 / Evidence protection

Do not turn one broken option into an unknown system.

×Do not delete the entire data root before copying logs and config.
×Do not grant recursive Full Control to AppData or Roblox.
×Do not disable antivirus or CFA globally for a guess.
×Do not mix packs, profiles, plugins, fonts, and cursors in one test.
×Do not rely on planned Safe Mode or presence composer controls.
×Do not load an unknown DLL because another plugin failed.
×Do not overwrite the persistent source with an old deployed copy.
×Do not clean reinstall while one optional layer is isolatable.

08 / Escalation

Report the last checkpoint that passed.

“Mods do not work” cannot separate persistence, deployment, format, or rendering. A compact evidence bundle can.

Remove: Windows username, account IDs, private links, tokens, and unrelated paths.

Settings / mods report

Luczystrap version:
Windows version:
Installed or portable:
Affected category:
Expected result:
Observed result:
Last checkpoint that passed:
Active profile:
Roblox version ID from log:
Value survived reopening? yes / no
Stock Roblox worked after isolating category? yes / no
First error and full affected path:
Latest redacted log: attached
Resource / plugin / flag source:
Exact reproduction steps:

09 / FAQ

Short answers for common dead ends.

Why do settings save but not change Roblox?

A save proves persistence only. Profile selection, deployment, the allowlist, or the target resource can still stop the visible result.

Why did a mod stop after a Roblox update?

An update can create a new version directory or change the overridden resource. Confirm modification application, then test the resource alone.

How do I know whether a setting was saved?

Change one value, close and reopen Settings, then confirm it remains and the related log save completed.

What if a custom font or cursor does not appear?

Return the category to Default, confirm stock output, then apply one trusted file. Route an exact access error to its guide.

Why is Discord Rich Presence not showing?

Run Discord desktop, enable activity tracking, launch through Luczystrap, and inspect watcher lines. Planned fallbacks are not current repair features.

What if a plugin does not load?

Remove only the suspect plugin, restart, and compare discovery and loading lines. Do not install an unknown DLL.

Can a FastFlag save and still be ignored?

Yes. Roblox can ignore local flags outside its allowlist. The file timestamp does not prove acceptance.

Should I clean reinstall for one broken mod?

Usually no. Preserve evidence and isolate the category first. Use the clean reinstall workflow only after narrower recovery fails.

10 / Evidence

What this diagnosis is based on.

01Official repository and READMECurrent feature claims, troubleshooting notes, and roadmap limits.↗ 02Luczystrap 1.4 releaseProfiles, plugin support, cursors, and IXP exclusion.↗ 03Luczystrap 1.4.9 releaseCurrent public build and current/removed boundaries.↗ 04Public 1.4.9 diagnostic logCurrent settings, profiles, plugins, mods, and deployment stages.↗ 05Font and crosshair reportConfirms the paired symptom without inventing one cause.↗ 06Public 1.3 source tagHistorical persistence and modification code, not current 1.4.9 code.↗