Follow us:

LogoErmes Logic

Whatsapp

Email Us

[email protected]

Central Guard Dynamic - Static DLL & guard_token.dat

Description

Central Guard Dynamic - Static DLL, guard_token.dat and OZT Encryption

This document explains the latest Central Guard Dynamic workflow, including the new static DLL system, the external guard_token.dat file, multi-key management, LUA compatibility and OZT file encryption.

Latest Update
Central Guard Dynamic now uses a static DLL with an external guard_token.dat file. The DLL does not need to be replaced or patched every time you create or add new protection keys. You only need to associate the DLL once with the protected client.
Requirements
  • A clean DLL available in: DLL_Default
  • The latest Central Guard Dynamic version
  • The generated guard_token.dat file
  • The protected client files, folders or OZT resources
1. New static DLL workflow

Starting from this update, the DLL is static and reusable. It must be associated only once with the protected client.

  • The DLL no longer needs to be replaced every time new keys are created.
  • The DLL no longer needs to be patched again just to add new protection keys.
  • After the first association, the DLL should remain the same.
  • New keys and protection metadata are managed through guard_token.dat.
Important
Do not replace the DLL for every new protection key. After the DLL has been associated once, update or regenerate only guard_token.dat when you create or add new keys.
2. What is guard_token.dat?

guard_token.dat is the external encrypted token file used by Central Guard Dynamic. It contains the protection data required by the DLL to validate and decrypt protected files at runtime.

  • It stores the encrypted guard information used by the DLL.
  • It allows keys to be updated without replacing the DLL.
  • It must be distributed together with the protected client.
  • It must match the associated DLL and the protected files.
Critical
If guard_token.dat is missing, invalid, corrupted or not matching the protected configuration, the protected client will not start correctly.
3. Adding or creating new keys

When you create a new key or add additional keys, you do not need to replace the DLL.

  • Create or add the new key inside Central Guard Dynamic.
  • Regenerate or update guard_token.dat.
  • Replace only the old guard_token.dat with the new one.
  • Keep the already associated DLL unchanged.
Recommended update method

For future key changes, send only the updated guard_token.dat file to the client. The DLL should be replaced only when a new DLL version is explicitly required.

4. OZT file encryption

This version also adds support for OZT file encryption.

  • You can now protect OZT resources together with the other encrypted client files.
  • OZT files can be encrypted as part of a folder or as selected individual files.
  • The encrypted OZT files require a valid guard_token.dat to be used by the protected client.
5. DLL association and IP rules

The DLL association must be performed only once, unless you need to change important DLL-level data.

  • If you do not need to change the IP or replace the DLL version, keep using the current associated DLL.
  • If you need to change the IP, start again from a clean DLL in DLL_Default.
  • If you are using a DLL from an earlier update, replace it once and redo the association process.
6. Multi-Key System

The multi-key workflow is still supported, but new key data is now managed through guard_token.dat.

  • You can use multiple protection keys for different files, folders or resources.
  • New keys should be added by updating or regenerating guard_token.dat.
  • This reduces the risk of key conflicts and avoids unnecessary DLL replacement.
7. Usage scenarios
Creator skin and external content
  • Use the customer’s already associated DLL.
  • Add your own protection key through Central Guard Dynamic.
  • Generate or update guard_token.dat.
  • Distribute the encrypted content together with the updated token file.
Personal use

For personal use, we recommend keeping a consistent key strategy.

Benefits:

  • You avoid unnecessary DLL replacement.
  • You can update protected files by regenerating only guard_token.dat.
  • You can add future protected content more safely.
8. Key backup

The generated key is saved in:

  • key_generated.txt
Critical
Store it safely. If the key is lost, it cannot be recovered.
9. Trial license limitations

With a trial license:

  • You can only view the program structure.
  • Buttons EncryptAll and DecryptAll will be enabled only with an active license.
10. Update recovery

If the update fails for any reason:

  • Open ver.txt.
  • Set the version value to 0.1.0.
  • Restart Central_Guard_Dynamic.exe.

The updater will try to download and apply the latest version again.

Video tutorials
© Ermes Logic All rights reserved.