lurelockv1.0
features · manual

Every feature, on the table.

One rule runs through the whole list: Lurelock touches only the folders it owns — the client's flag directory, its content tree, and its own manifest. If you remove Lurelock, nothing lingers.

core

FastFlags table editor

Browse 300+ curated flags split into supported, placebo, rejected, community and tweaks. Search by name or value, stash strings, and apply per instance.

studio

Studio flag editor

A separate flag namespace keeps your editor installs independent from your client. Studio-only flags live here and never leak into play sessions.

drop-in

Drop-in mods

Drag a folder of textures, fonts, sounds or scripts into the mod list. Lurelock stamps it onto the client content and tracks every byte in its manifest.

portable

Portable mode

Run Lurelock from a stick. Profiles, manifest and cache live next to the exe instead of %APPDATA%, so your whole setup travels with you.

ids

Id & private server

Pin your preferred user id into a profile and Lurelock writes it into the client at stamp time — handy for private-server setups and testers.

security

Clean sweep undo

Cache cleaning keeps an undo ledger. Accidentally swept your inventory cache? Walk it back by session, not by guesswork.

look

Theme packer

Package a theme as a single .lurelock file from the manager UI, or author it by hand in JSON. Import anywhere, share by file.

hooks

Hook API

A tiny local hook bus in the manager. Bind external scripts to session events — before-stamp, after-launch, on-exit — with plain JSON callbacks.

Scope What Lurelock deliberately does not do: memory editing, exploit injection, bypasses of moderation or anti-cheat, or anything that requires being signed in as an account with elevated standing. It is a bootstrapper — it arranges files and launches a client. Full boundaries are written down in the developer docs.