LuaProtect v2.1 - Versions, Game Opportunities & a Leaner Engine
LuaProtect v2.1 replaces commits with a version system for controlled rollouts, adds the Game Opportunities page, a build warning before risky builds, first-use key expiry, better moderation, a new landing page and faster startup.
Introduction
v2 changed a lot at once, and v2.1 is where we follow up on it. We fixed the things v2 broke, listened to your feedback, and added a few features that make releasing and growing your scripts a lot easier. The two biggest ones are a new version system for controlled rollouts and the Game Opportunities page.
Here is everything that changed.
Replaced "Commits" With a Version System
The old commits system is gone. In its place you now have versions. You can serve a new version to only a few selected users first, or exclude certain people from testing an update. That way you can release a new version in a more controlled way, catch problems early, and only roll it out to everyone once you are happy with it.
Game Opportunities
The new Game Opportunities page shows you trending Roblox games that have plenty of players but only a few scripts. Every game gets a score, together with its player count, how many public scripts it already has and any anticheat reports, so you can quickly see where a new script would actually stand out.
Game Opportunities is available on Pro and Enterprise for now.
Safer Builds
We made it harder to accidentally release unprotected code. When we detect problems in your code before a build, you now see a "This build might fail" warning. If you build anyway and it succeeds, the warning is cleared automatically.
The Cortex obfuscator has been removed, and all builds now run through Centurion. Your dashboard now shows which Centurion version protected each script, so you always know what your players are running.
We also fixed an issue where the game could crash after a few obfuscations.
Keys
- The Create keys window was redesigned, and you now pick a script every time instead of it being preselected
- Key expiry now starts when the player first uses the key, not when you create it
- You can set a custom duration for keys
- Added a Discord link to the key input screen
- Redesigned the multi-select bar for bulk actions on keys and other lists
- Shared keys only need 5 characters now
Dashboard
- Updated the Overview page and added a What happened component
- Added average session time to your script stats
- The executor breakdown now uses the color of each executor's logo
- Merged some Settings pages, so there is less to click through
- 2FA setup now opens in its own window instead of inline
- Added an exempt from VPN protection setting to user profiles
- Brought back IPs for Enterprise users
- Updated profiles and added a new badge
- Added a question system to broadcasts and moved the broadcast button
- Improved and fixed dropdowns, which sometimes acted glitchy while scrolling
- Updated the editor
- Improved the mobile dashboard
- Fixed UI issues caused by v2, plus lots of general polish
Security & Moderation
We improved security on the runner and across the whole site again. Moderation got much stricter as well: images and text inputs were not checked well enough before, so they now go through the OpenAI moderation API.
Performance
Startup and execution times got faster again, and we made the whole website more robust. We also fixed auto-execute sometimes stopping after a while.
Fixes
- Fixed Lynx executor not working
- Fixed Projects not working
- Fixed avatars sometimes not loading
- Fixed plan models and the AI being out of sync
- Fixed OAuth bugs
- Fixed the MCP instructions
- Fixed a nil error, a game error and a backend issue
- Fixed lots of smaller issues
If you see a "Your executor does not support…" message, please let us know in our Discord, together with the executor you are using.
Website
We fully updated the landing page, including its header, as well as the login page and our marketing pages. We also did more SEO work, so LuaProtect is easier to find.
Behind the Scenes
Besides all of the above, there were plenty of internal updates and smaller changes that did not need their own heading.
Thanks for all the feedback. Keep it coming in our Discord!