Skip to content

Safety Model

Claude Sonnet 5 edited this page Aug 25, 2026 · 2 revisions

Safety Model & Double-Consent

These rules apply across every feature and can never be bypassed:

  1. Core binaries are protected. The app will never write to, overwrite, or delete GTA5.exe, GTA5_Enhanced.exe, PlayGTAV.exe, launcher/anti-cheat binaries, or any .exe in the game tree — including through the Advanced Tools Editor.
  2. Double-consent for destructive changes. Any overwrite or deletion of an existing file requires you to confirm twice. Cancel at either step and nothing changes. This applies to installs that would overwrite existing files, uninstalls, full-mods-folder restore, and Editor saves.
  3. Backups before changes. Originals are copied to backups\ before they are overwritten, and installs roll back automatically on failure. See Data Locations and Logs for exactly where.
  4. Elevation on demand. The app runs unelevated and only asks for administrator rights when it actually needs to write into a protected folder (e.g. GTA V installed under Program Files).
  5. The game is never modified out from under itself. Game Setup and Launch detects whether the game process is running, and blocks install/uninstall/enable/disable while it is.
  6. This tool never ships or uses GTA V's proprietary decryption keys. The SP to FiveM Converter can read unencrypted .rpf archives, but AES/NG-encrypted ones are detected and reported, not decrypted.

Why this exists

The app is built for players who want to install mods quickly without risking their game files or their save data. Every feature — install, uninstall, enable/disable, the Editor, full backup/restore — routes through this same set of guarantees, so the safety model doesn't need to be re-verified per feature; it's a property of the app as a whole.

Clone this wiki locally