What 1.4 says shipped
The October 28, 2025 release introduces Profile Management as a new feature.
- A dedicated Profiles tab
- Multiple saved presets
- Quick switching between settings
- IXP intentionally not supported
Profile field guide · Evidence checked Aug 02, 2026
Keep setups separate.
Know what travels.
Luczystrap Profiles let you save multiple presets and switch between settings from one tab. The useful part is separation. The important limit is that the official release does not document every field a profile contains.
Confirmed: release 1.4 added Profile Management, multiple saved presets, quick switching, and an explicit IXP exclusion. A public 1.4.9 log now confirms installed mode loading
%LocalAppData%\Luczystrap\Profiles.json; portable storage, field scope, export, and format compatibility still need verification.01 / Evidence status
Separate shipped, observed, and unknown.
Release notes establish the feature. A current public runtime log establishes the installed file path. Neither source publishes a field-by-field schema or cross-version recovery contract.
What 1.4.9 loads
A public July 2, 2026 log initializes %LocalAppData%\Luczystrap as Base and reports a successful load from Profiles.json.
- Installed-mode path observed in a current log
- Settings and FastFlags load separately
- The active process log remains the path authority
- Portable placement still needs runtime verification
What remains unknown
Luczystrap’s current application source is closed, and public notes do not explain profile serialization.
- Exact 1.4.9 saved categories and values
- Create, clone, rename, delete, export labels
- Automatic backup and merge behavior
- Compatibility across future profile formats
02 / Scope inspector
Does the profile save this?
Choose a category. Each answer uses the narrowest statement supported by the official release and README, then gives you a verification test instead of an assumption.
FastFlags
The README describes flags and per-profile overrides, while the release only says “settings.” Because the same README marks Full Profiles planned, verify one harmless allowlisted key in your installed build.
Test
Record one allowlisted key, change it in one profile, switch away and back, then inspect the value.
Do not infer
A visible profile name does not prove every FastFlag or imported pack belongs to it.
Backup
Export the active FastFlag JSON separately before testing profile behavior.
Policy still applies: a profile cannot make a non-allowlisted local key recognized by Roblox Player.
03 / Create and switch
Build one profile you can prove.
Exact button labels are not published for 1.4.9. This workflow uses the confirmed Profiles tab and observable state, so it remains valid even when the UI wording changes.
Record version and state
Open Luczystrap and note its version, the visible active profile if one exists, and the original value of the one setting you plan to test. Do not begin with a large preset import.
Close and back up
Close Luczystrap and every Roblox process. Copy the product-named configuration roots that actually exist to a dated folder outside AppData and outside a portable UserData directory.
Open Profiles
Restart Luczystrap and open the Profiles tab introduced in release 1.4. Use the create or add action visible in your installed build; this guide does not invent a button label.
Name the purpose
Use a descriptive name such as Baseline, Low-load test, or Visual test. A purpose survives game updates better than a vague name such as “New Profile 2.”
Save one difference
Choose one reversible category from the scope inspector. Record the original and candidate values, save, and confirm that the intended profile still appears active.
Switch in both directions
Activate another known profile, verify the test value leaves or changes, then return to the new profile and verify it returns. If it does not, that category is not proven to be profile-scoped.
Verify in Roblox
When the setting affects Player, close all Roblox processes and relaunch. For FastFlags, check the current local allowlist. Keep the backup until the state survives another Luczystrap and Roblox launch.
Finish line: you can name the active profile, show one setting changing when you switch away, show it returning when you switch back, and restore the untouched pre-test backup.
04 / Activation proof
Is the profile actually ready?
Check only what you have observed. The score is a local checklist, not a Luczystrap diagnostic and not proof that every category is saved.
Verified checkpoints
0/5
Not verified yet
Complete the reversible switch test before relying on this profile.
05 / Backup boundary
Preserve data without guessing one file.
The current README documents general data roots, not an exact profile path. Use them to locate Luczystrap-owned data, then verify timestamps and contents on the machine you are backing up.
Roaming AppData
%AppData%\Luczystrap\The README calls this the installed config root. Close the application before copying it, and confirm the copy contains real files rather than shortcuts.
Beside the application
.\Luczystrap\UserData\The README documents this portable data root. Moving only the executable is not the same as moving its documented user data.
Local logs
%LocalAppData%\Luczystrap\logs\Logs are evidence for a failed switch, update, or restore. Preserve recent logs separately; they are not a substitute for the profile data itself.
Exact profile path unknown: do not delete or overwrite Luczystrap folders because one README path looks authoritative. Close the app, inspect which Luczystrap-named roots exist and change when you save, then copy those specific roots to a dated folder. Never back up or publish the whole Windows user profile.
06 / Version compatibility
Treat every move as a migration.
No public compatibility contract describes the profile format. Preserve both sides of a change until one restored profile passes a controlled switch and launch test.
| Change | What is known | Safe action |
|---|---|---|
| Luczystrap update | Profiles shipped in 1.4; no later release publishes a profile-format guarantee. | Back up before updating, record both versions, and test one profile before trusting the rest.Keep old backup |
| Installed → portable | The README documents different data roots for the two modes. | Do not move the EXE alone. Preserve both roots and restore only after a clean portable launch.Storage changes |
| Portable → installed | The installed config root is documented separately from portable UserData. | Start installed mode clean, then test a copied profile layer rather than replacing every setting at once.Stage the restore |
| Old backup → current build | Forward compatibility is not documented. | Keep the original immutable, restore a copy, and stop if fields disappear or reset.Schema unknown |
| README “full profile” assumption | The same README describes profiles as available and planned. | Use the scope inspector and prove each category independently.Do not assume everything |
| IXP inside a profile | Release 1.4 explicitly excludes it. | Do not attempt to recover or bundle IXP through profiles; keep IXP management off.Explicitly excluded |
07 / FAQ
Profile questions, answered.
Short answers for the exact points where release evidence, runtime evidence, and current implementation boundaries differ.
Luczystrap 1.4 release notes describe a profile as a saved preset that lets you keep multiple groups of settings and switch between them from a Profiles tab.
Back up the current state, open the Profiles tab, use the create or add control shown in your build, give the profile a purpose-based name, save one recognizable setting, switch to another profile, then switch back and verify the value and active profile.
The 1.4 release confirms multiple presets and switching but does not publish a field-by-field scope. Current logs load Settings.json, FastFlags, and Profiles.json separately. Verify each category instead of assuming the profile saves everything.
No. Luczystrap 1.4 release notes explicitly say IXP is intentionally not supported by Profile Management. See the IXP and FastFlags boundary for the current policy context.
The README uses per-game or context language, but the release notes only confirm saved presets and quick switching. Automatic per-game activation is not confirmed for the current 1.4.9 build, so switch manually unless the installed interface clearly documents otherwise.
A public 1.4.9 log shows installed mode loading %LocalAppData%\Luczystrap\Profiles.json. Confirm your own Paths::Initialize and ProfileManager::Load lines because portable or moved installations may initialize another Base.
Current official evidence does not confirm a dedicated profile export or import control. Until that workflow is verified, close the application and make a dated manual backup of the Luczystrap data roots that actually exist.
Confirm the intended profile is visibly active, test one known included setting, save, close every Roblox Player process, and relaunch. If the profile itself is missing or reset, use the preservation-first recovery guide.
08 / Continue by task
Use the page for the layer inside.
Profiles organize states. The linked guides explain the individual setting, policy, measurement, or recovery boundary that still applies after a switch.
Graphics setup
Graphics controls
Separate FastFlags, global settings, presets, and measured results.
Open graphics hub →Flag configurationFastFlags hub
Edit, import, verify, and reset Roblox-allowlisted local keys.
Open FastFlags guide →Missing or resetProfile recovery
Find the active Profiles.json, preserve candidates, and test one copy safely.
Recover a profile →Excluded categoryIXP boundary
Understand why IXP is not part of Profile Management.
Read policy context →09 / Primary evidence
Read the project record directly.
The release establishes the minimum shipped feature. A public current log establishes the installed file path. Neither source publishes the complete profile schema or a compatibility contract.
Luczystrap · Official release · Oct 20251.4 Profile Management and IXP exclusion
↗Luczystrap · Public 1.4.9 diagnostic logInstalled Base and successful Profiles.json load
↗Luczystrap · Current READMEProfile claims and roadmap conflict
↗Luczystrap documentationIXP exclusion and current Roblox policy context
→Roblox local configurationCurrent 18-key FastFlag allowlist snapshot
→Luczystrap recoveryProfiles.json discovery and controlled restore workflow
→Evidence note: tag 1.4 closes the application source, so exact current profile serialization cannot be independently audited. This page deliberately labels implementation details unknown instead of converting README intent into a shipped guarantee.