Skip to content

support for 6.382.893.0 + other improvements/fixes

Choose a tag to compare

View all tags
@DVS-code DVS-code released this 27 Jun 17:04
· 11 commits to main since this release
V2.7
0f31ab8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ForzaCryptoTool V2.7 — Release Notes

⚠️ Major workflow change: Sessions removed

The Sessions tab is gone. The full GameDB flow — decrypt → edit → re-encrypt → re-edit → merge — now happens entirely on the Dashboard with plain files. No session bookkeeping, no hidden state. This is a simpler, more predictable workflow.

New

  • Decrypt ANY modified database. You can now decrypt a GameDB you've already edited/re-encrypted — not just stock game files. The tool automatically picks the right decrypt path (IV table for stock DBs, in-file IVs for modified ones), so the re-edit loop works: decrypt → edit → re-encrypt → decrypt again → edit again → re-encrypt.

  • Merge another DB's changes (auto-detect). New Merge button on the Dashboard: pick a donor decrypted GameDB and the tool automatically detects what changed in it (added/modified rows) and applies only those rows into your DB — no table-picking. Includes integrity checking, foreign-key safety, and a container-size guard, and it backs up your file first.

  • Re-encrypt without sessions. Re-encrypt asks for the original encrypted .slt only when it needs it; right after a decrypt it's one click. Sends the IV table for stock originals and goes table-free for modified ones automatically.

  • Real error messages. Backend failures now show the actual reason.

  • Multi-version GameDB IV table. The bundled IV table covers multiple game builds at once (currently 6.353.145.0 and 6.382.893.0). This is to add unlimited support for future game versions.

  • "No edits detected" warning. After a re-encrypt, if the output is byte-identical to the original, the tool warns you loudly — catching "I forgot to save / edited the wrong file."

  • In-app next-step guidance. After each operation the tool tells you exactly what to do next.

Improved

  • Auto-update fixed. The updater now points at the correct public releases repo (it was 404'ing before) and gives honest "up to date / no release / can't reach GitHub" messages instead of falsely claiming you're current.

  • Older ForzaTech: only valid combos. The game/key-type dropdown now offers only the key types each game actually supports, so you can't pick a combination the backend rejects.

  • Consistent naming/icons. The re-encrypt action is "Re-Encrypt" with a single icon everywhere.

  • Sidebar navigation rebuilt on a cleaner internal model.

  • MS Store version is now FULLY supported.

Fixed

  • The "Job polling failed: backend reported failure" error on modified databases — root-caused and fixed across frontend (decrypt-path selection, real error surfacing) and backend (block-0 reconstruction, oversized-recovery rejection).

  • Re-Encrypt no longer greys out on a decrypted GameDB loaded on its own.

  • Merge no longer freezes the window (runs in the background) and is guarded against exceeding the fixed GameDB container size, with a clear message instead of a confusing backend error.

How to use it (quick reference)

Edit the game database

  1. Dashboard → drag your encrypted gamedbRC.slt → Decrypt.
  2. Open the ..._decrypted.sqlite in DB Browser for SQLite, edit, Save, close.
  3. Re-Encrypt (pick the original .slt if asked) → loadable .slt.

Merge another DB's changes into yours

  1. Decrypt your base DB. With the decrypted .sqlite loaded, click Merge.
  2. Pick the donor decrypted .sqlite → it auto-applies the donor's changes.
  3. Re-Encrypt → loadable .slt.

Notes

  • Always back up your files before editing.
  • IV capture for Profile and Method 22 is unchanged.
  • After a game update there's a chance the backend needs updating. Please don't spam-report issues if the backend simply needs new keys after a patch.
Assets 3
Loading