Support

Support debug package

When production breaks, speed matters. This is the minimum professional bundle support needs — tight scope, no secrets. License keys and Telegram tokens stay out. Contact via Support (in-app form under Others → Support mirrors the website).

Support

1. Paste into the message (non-negotiable basics)

  • App version (About / window title, or the installer or ZIP filename).
  • Windows version (e.g. Windows 11 24H2).
  • Setup vs portable and roughly where the app lives.
  • Display scaling (125%, 150%, …) and how many monitors you use for the game.
  • Active profile name only (e.g. default) — not the full profile JSON.
  • One short paragraph: expected vs. actual — numbered repro steps if you can (“1. … 2. …”).
  • Whether Autocrypter, chest counter, or Epic Attack (beta) was active.

2. Zip these log files (usually safe)

From your TotalCrypter user_data folder:

  • Portable / typical: user_data next to TotalCrypter.exe.
  • Installed under Program Files: often %LOCALAPPDATA%\TotalCrypter\user_data\ (Windows uses this when the install directory is not writable).

Include if present:

  • totalcrypter.log — main log.
  • chest_counter.log — only if the chest counter is part of the problem.
  • fatal_startup.log — only if the app dies very early; it may sit under the same user_data, under %LOCALAPPDATA%\TotalCrypter\user_data\, or as TotalCrypter_fatal_startup.log in your user profile. Search your PC for the filename if unsure.
  • totalcrypter_runtime_adaptation.json — optional, small file.

Name the archive something like TotalCrypter_debug_2026-05-16.zip and attach it to email only if the mailbox allows the size; otherwise use a trusted file share and paste the link.

3. Do not send unless we ask

  • totalcrypter_settings.json — can contain Telegram bot tokens and sensitive paths.
  • License keys, payment card data, or passwords.
  • Full profiles\*.json — large and rarely needed; we will ask for a redacted export if necessary.

4. Optional extras

One screenshot of the error or relevant UI (black out unrelated personal info). Numbered steps to reproduce (“1. … 2. …”).

Sending a debug package?

Use the contact form with version, scaling, and a tight log ZIP — no secrets.

Contact support