Skip to content

CYBER ENGINE TWEAKS // CONFIGURATION DEEP-DIVE#

> LOADING MODULE: cyber_engine_tweaks.dll > STATUS: NOMINAL

Misty

A walkthrough for configuring Cyber Engine Tweaks (CET) — one of the core frameworks bundled in the Preem Team collection — and for reading its console log when something goes wrong.

"Life is so powerfully beautiful. So much more powerful than death" — Misty

Who this is for

Anyone running the Preem Team collection who wants to understand what CET does and how to tweak its settings safely.

What is CET?#

Cyber Engine Tweaks is a scripting framework that lets mods hook into the game engine at runtime. It also ships with an in-game console overlay used for debugging, running commands, and managing loaded mods.

Most of the collection's gameplay and UI mods depend on CET being installed and configured correctly.

Opening the console#

  1. Launch the game with the collection installed.
  2. From the main menu or in-game, press the default bind: ` (backtick) or ~. Or whatever key you used when the First Boot - Set CET Keybinds prompt appeared "

  3. The CET overlay should appear over the game, dimming the background.

  4. Console opens with the default hotkey or the hotkey you set

  5. Mod list tab shows all installed CET-dependent mods
  6. No errors appear in red text in the console log

Changing the hotkey

If ` conflicts with your keyboard layout, edit bin/x64/plugins/cyber_engine_tweaks/config.json and change the bind field under "console_key".

Key configuration options#

CET's behavior is controlled through config.json in its plugin folder. The most commonly adjusted options:

{
  "console_key": "grave",
  "enable_debug": false,
  "font_size": 16,
  "remove_binding_limit": true
}

{
  "enable_debug": false,
  "remove_binding_limit": true
}

Keeps overhead low and avoids flooding the log with debug noise — the configuration the Preem Team collection ships with by default.

{
  "enable_debug": true,
  "remove_binding_limit": true
}

Turns on verbose logging. Useful when following steps from Troubleshooting, but noisy for normal play — turn it back off afterward.

Don't hand-edit while the game is running

Changes to config.json are only read on launch. Editing it mid-session won't do anything until you restart the game, and in rare cases can cause CET to fail to save its own state on exit.

Reading the console log#

If something's crashing, the CET log is usually the first place to look.

  1. Open the CET overlay (`).
  2. Navigate to the Log tab.
  3. Scroll to the bottom — the most recent entries are what you want.
  4. Look for lines in red or containing [error] / [fatal].

Common fatal error

[error] Failed to load module: <modname>.lua
This almost always means a mod version mismatch. Check Common Problems for the fix.

"The console doesn't lie. It just doesn't always tell you the whole truth either." — CET maintainers