Luczystrap
Normal Windows-user authority, or elevated authority if launched as administrator.
Settings manager APIMod / theme manager APILogger + versions API
01 / Evidence snapshot
Four facts before any plugin decision.
Confirmed means a current public file says it. Unknown means the evidence needed to answer is absent—not that a protective feature definitely does or does not exist.
.NET 8 DLL model
The README builds a class library, pairs its DLL with plugin.json, restarts Luczystrap and enables it in Plugin Manager.
Lifecycle and host services
Load, unload, Roblox launch and close callbacks receive logging, settings, mod, theme, data-directory and version surfaces.
Interfaces + PluginContextCurrent loader controls
No public 1.4.9 loader source establishes signature checking, hash pinning, trust enforcement, process isolation or permission prompts.
Current app source unavailableDo not infer a sandbox
Microsoft says untrusted code cannot be safely loaded into a trusted .NET process. Use an OS or virtualization boundary for isolation.
Microsoft Learn plugin guidance02 / Capability inspector
What the SDK exposes—and what it does not limit.
Select a surface to separate the published interface from the security conclusion. These are capabilities, not user-facing permission prompts.
Select a capability surface
Public interface
A plugin can run at four lifecycle points.
The main interface defines asynchronous methods for load, unload, Roblox launch and Roblox close. OnLoad receives PluginContext and returns a success value.
Published surface
OnLoadAsync · OnUnloadAsync · OnRobloxLaunchAsync · OnRobloxCloseAsyncWhat this establishesWhen plugin behavior can be triggered
Code can react during app and Roblox lifecycle transitions.
What remains unknownTimeout and failure isolation
Current callback ordering, cancellation, crash containment and loader recovery are not published.
Review rule: inspect every callback, including “empty” ones, and test load, launch, close and unload separately.
03 / Interactive trust gate
Seven questions before Enable.
This checklist does not scan or certify a plugin. It helps expose missing evidence. Even seven answers mean “reviewable,” never “guaranteed safe.”
Evidence completed
0 / 7
Do not enable yet.
The plugin has not crossed even the minimum evidence gate.
Browser-only checklist · no file access · no saved state · no transmission
Mark only what you have actually verified
04 / Hard stops
Reject the plugin before testing.
Any one of these conditions is enough to stop. Popularity, a Discord role, a polished manifest or a clean name does not override the behavior.
It asks for account secrets.
Password, `.ROBLOSECURITY`, 2SV code, backup code, recovery email access or an unrelated API token.
It demands permanent elevation.
Administrator mode expands the effective authority available to the host and loaded code.
It asks you to disable protection.
Broad Defender exclusions, antivirus shutdown or recursive permission changes are not acceptable installation steps.
It injects, automates or alters memory.
Do not treat gameplay automation, memory modification or exploit behavior as an ordinary customization plugin.
It is an opaque reupload.
A DLL from a chat attachment or mirror with no canonical release, exact hash and trustworthy author remains unknown code.
It proves trust with its own manifest.
isTrusted: true, author text, ratings and download counts are fields—not self-validating attestations.
Credential incident rule: if a plugin received or may have read a Roblox session cookie, remove the plugin from the device only after moving account recovery to a known-clean environment. Then use official Roblox Session Management and reset access.
05 / Package anatomy
Know every file before it enters Plugins.
The SDK README documents a folder whose name, DLL and manifest ID match. Dependencies and persistent data widen the review surface even when the package looks small.
%LocalAppData%\Luczystrap\Plugins\plugin-id\SDK-documented path
DLL
plugin-id.dllExecutable .NET assembly
RequiredJSON
plugin.jsonDeclared identity and metadata
RequiredDEP
Dependency assembliesAdditional executable code if shipped
Review allDAT
Generated plugin dataSettings or files created after load
Removal scope01
Prove the clean baselineMove all plugins out, launch Luczystrap twice, start and close Roblox, and keep the newest clean log.
Baseline02
Freeze package identityRecord author, source commit, release, DLL and dependency SHA-256 values, manifest and target app version.
Record03
Pass the trust gateReview lifecycle code, file and mod writes, endpoints, credentials, elevation and complete rollback.
Inspect04
Place only one pluginUse the documented matching ID/folder/DLL structure only if the installed Plugin Manager matches it.
Isolate05
Enable as a standard userRestart, enable one plugin, read the latest log, and test only the exact feature it claims.
Observe06
Exercise all lifecycle pointsCheck load, Roblox launch, Roblox close and unload behavior; note every new file and network request.
Test07
Disable, remove and re-proveClose apps, remove only that plugin, clean its documented data and mods, then confirm the baseline returns.
RollbackCompatibility boundary: the public SDK setup route does not prove that an arbitrary plugin loads in 1.4.9. Use the exact app–SDK compatibility matrix and a dated runtime test.
06 / Continue by intent
One question per evidence route.
Use the page that owns the next decision. Compatibility, account recovery and permission failures should not be collapsed into one plugin verdict.
Compatibility
Will this plugin load?
App version, SDK snapshot, manifest, dependencies, callbacks and controlled runtime test.
Open plugin matrix →Credential responseDid a plugin touch account access?
Use the cookie exposure and official Roblox recovery sequence from a known-clean device.
Open account security →Runtime evidenceWhere did loading fail?
Find the newest Luczystrap log before and after the isolated one-plugin test.
Find logs →Developer contractWhat does the public SDK expose?
Review the interfaces and example directly at the canonical repository.
Inspect SDK source ↗07 / Exact questions
Luczystrap plugin safety FAQ.
Direct answers that separate a manifest claim, an SDK interface, a runtime result and a genuine security boundary.
The public SDK describes a .NET 8 class library compiled to a DLL, paired with plugin.json and enabled through Plugin Manager. It is executable code, not a passive theme file.
No sandbox can be verified from current public evidence. Microsoft says untrusted code cannot be safely loaded into a trusted .NET process, and the current Luczystrap loader source is unavailable.
A plugin data directory, logger, settings manager, mod manager, theme manager, Luczystrap version and Roblox version. These helpers do not cap what arbitrary .NET code can attempt.
No. The public SDK defines the field but not a signature scheme, verification criteria, revocation system, permission enforcement or loader-side validation. A manifest cannot attest to itself.
The SDK README documents %LocalAppData%\Luczystrap\Plugins\<plugin-id>\ with a matching DLL and plugin.json. Verify this route against the visible manager in your installed release.
Not by default. Elevating the host raises the effective access available to code running inside it. Reject permanent elevation without a narrow, documented and trustworthy reason.
Treat that as a hard stop. Do not provide browser cookies, passwords, 2SV codes, backup codes or unrelated credentials to a plugin.
No. A scan result is one signal for one exact hash. It cannot prove that every feature, endpoint, update, dependency or future behavior is appropriate.
Prove a plugin-free baseline, record exact versions and hashes, add one reviewed package, observe every lifecycle callback and claimed effect, then remove it and verify rollback.
Disable it when possible, close Luczystrap and Roblox, remove only its folder, then inspect documented settings, data, mods and logs. Restart without it and verify the clean baseline.
08 / Primary evidence
Sources behind the trust model.
SDK files establish exposed contracts. Release notes establish announced behavior. Microsoft defines the security limit of in-process .NET plugin loading.
Luczystrap · Public SDKCanonical plugin contract and example tree
↗Luczystrap SDK · README.NET 8 build, package path and Plugin Manager route
↗Luczystrap SDK · InterfaceLoad, unload, Roblox launch and close lifecycle
↗Luczystrap SDK · ContextData, logging, settings, mods, themes and versions
↗Luczystrap SDK · MetadataIdentity, dependencies, rating and isTrusted fields
↗Luczystrap SDK · Mod managerRoblox resource install and removal surface
↗Official release · 1.4Plugin SDK and community modding introduction
↗Official release · 1.4.1Plugin errors changed from silent failure to logging
↗Luczystrap repository · CurrentCurrent application and loader source closure marker
↗Microsoft Learn · .NET pluginsUntrusted-code warning and OS isolation guidance
↗Luczystrap compatibility auditSDK reproducibility and app–plugin runtime matrix
→Luczystrap account securityCookie exposure and official recovery route
→Checked August 6, 2026. The public SDK documents intended interfaces and installation structure. It does not publish a permission manifest, sandbox contract, signature or hash enforcement, trust-verification criteria, process isolation design, marketplace review policy or current 1.4.9 loader implementation. Microsoft’s in-process warning is therefore used as the safe default boundary. This page does not scan DLLs, endorse community uploads or convert metadata into a security claim. Luczystrap is not affiliated with or endorsed by Roblox Corporation.