General troubleshooting

Before trying anything else, please make sure that your Windows and your graphics driver are up-to-date – this actually helps in around 50% of all cases. If you need instructions, you can find them in the red box under the general troubleshooting guide's section.

Step 0: Go to your install directory

Go to your Cyberpunk 2077 game directory, since all paths given in this guide will be relative to that folder.

Example:

For that reason, the Redmodding Discord can only support you the most recent version.

If there's a mismatch, then you can find a warning in the following file:

If you don't have that file, proceed to Step 2.

Go to your Cyberpunk 2077 and check the following subfolder:

It should have at least the following files:

If you do not have these folders, then CET isn't installed correctly. Head to and start with step 3.

If everything looks okay in step 1, check if you have a file cyber_engine_tweaks.log inside the cyber_engine_tweaks folder from the previous screenshot.

No log file means that CET isn't starting up.

• The easiest fix is to .

• If you did that and it didn't help, check your antivirus. Most likely, it is protecting you from scary things like Cyber Engine Tweaks. Disable it.

• If that didn't help either, update everything - Windows, your drivers, etc. You can find links and instructions in the red box on the .

• If you do have it, you can open it and try to make sense of the error message. You can find more information on that , or find help in the #cet-suppport channel on our .

1. If you are using Vortex, turn it off (it will get angry otherwise)

2. Complete either of the following steps inside your :

   • rename bin/x6/plugins to plugins_ or

1. Find the file \bin\x64\plugins\cyber_engine_tweaks\bindings.json and delete it.

2. Start the game.

3. You should now see a popup asking you to bind a key. Otherwise, read on.

Click into the "Binding..." field.

If that doesn't help, make sure to turn off all your overlays (Discord, Steam, Microsoft Game Bar, Random Useless Bloatware) or start Cyberpunk in the Windowed Borderless mode.

If you're experiencing performance issues with CET, first make sure to as per the instructions to rule out side effects from old files.

If that doesn't make the problems go away, make sure to update Windows and your graphics driver as per the red box under Troubleshooting's section.

If that doesn't help, you can find us in #cet-support on the . Please note that people there will first suggest everything else from this guide, so you might as well get it out of the way first.

Make sure to update Windows and your graphics driver as per the red box under Troubleshooting's section, as this is the only chance you have of getting rid of your crashes.

This is a known issue with AMD cards, and it's not something the CET developers can fix. Everyone who could fix it is informed, but such things take time. If you're on an AMD card, you can try running your game in Windowed Borderless mode. Otherwise, you just have to live with the crashes.

Please ensure the following:

1. If you have modified your game's .exe file yourself, the mod will not work - to undo this, delete the file and verify your game through GOG, Steam or Epic to download a fresh copy of the newest exe.

2. Update your game. You are using a patch that is not supported. Only current versions are supported. (current version is 1.6)

3. You used the old version of the mod and still have the old files installed. Delete bin/x64/plugins/ and reinstall the mod.

Install - if nothing happens, please make sure all of your overlays and monitoring programs are disabled. There is a list of known programs that cause issues below. If you find one not on the list, contact Arsenic_Touch via the discord.

Cyber Engine Tweaks no longer comes with a config file, one is generated when you first launch the mod.

When first launching cyber engine tweaks, it will prompt you to pick a keybind. Tilde is no longer the default. Keyboard input is blocked until a keybind is chosen. If you do not see the pop up, look below for further troubleshooting steps.

Certain programs conflict with the hook that Cyber Engine Tweaks use to display the console - to avoid this, disable any software with overlays that may impact the mod (some examples below). This includes crashing the game or not launching at all. OBS graphics-hook32.dll and graphics-hook64.dll can also interfere. Do a search of your windows files to see if you have a program running them. For rivatuner, you can also open the Global file with notepad++, which is located in RivaTuner Statistics Server\ProfileTemplates and add cyber_engine_tweaks.asi to the end of the decimal in the line: InjectionDelayTriggers

1. Open Windows Security

2. Go to Apps & Browser control on the left tabs

3. Click Exploit protection settings Under the Exploit Protection section

Credit to discord user @rachmanov1c @OrBy

Please verify that:

1. Your version of Cyberpunk is compatible with the newest release on GitHub or Nexus (this can be seen in the menu, underneath "Quit Game")

2. You have the most recent version of the mod from or

3. The has been followed correctly

1. Make sure cyber engine tweaks and your mods are installed with hardlink If hardlink doesn't show up under vortex, make sure the Vortex Mods folder is on the same partition as the game mods folder. This explains it .

2. Make sure you're using the most up to date vortex plugin for cyberpunk 2077. Check the channel on the discord for the latest information.

There are six possible solutions to this:

1. Ensure your game is in - Cyberpunk will usually make itself the topmost application on your screen if in fullscreen.

2. Ensure you don't have any or monitoring software running such as Rivatuner, Fraps, etc.

3. Make sure your game is up to date and you are using the latest version of Cyber Engine Tweaks and that you installed it properly. (do a clean install by deleting the plugins folder, LICENSE, global.ini, version.dll files if you are running into a problem)

1. Delete the bindings.json file located inbin/x64/plugins/cyber_engine_tweaks/ and start your game, the overlay will to choose a new keybind should come up. If it doesn't, check the known list of programs that can interfere.

If you see in your log that your game is freezing on CRender and you have problem like this you should try steps provided below.

1. If you are using mod manager disable CET temporarily, if you are not using mod manager then follow guide. 2. Launch the game without CET and disable FSR/DLSS 3. Install/Enable Cyber Engine Tweaks and launch the game, the problem should be gone.

Please ensure you attempt deleting and reinstalling the mod before submitting an issue! Alternatively, . Additionally, please check to ensure your issue has not already been reported!

If you cannot find your problem listed, with the following:

• Your configuration file

• Your Cyber Engine Tweaks version and your Cyberpunk 2077 version

• Your log file

• Your OS version

The various scripting wikis have been merged into a new wiki, please go there for scripting documentation about Redscript, CET, or general information of how to interact with the game systems through scripting:

Old links for this wiki are kept alive as redirects to their location in the new wiki, however scripting aspects for CET will no longer be available in this wiki.

Console UI

The console tab is where you type commands to use cheats and other useful functions.

Console Buttons

What the buttons and checkboxes do in the Console tab:

The console uses script language, you may want to look up how to use it before proceeding. There are some guides here to get you started:

First Launch

After installing CET, you can open the console overlay with the corresponding key.

Open the Console tab to run Lua scripts or engine functions. To find out what you can do here, keep reading.

Spreadsheets

To find all the codes you can enter, check

• CET Console Commands for Patch 2.x (source: #cet-support on redmodding Discord)

For the most common commands, see below.

If you want to find a specific item, look for how to find the hash code for the .

Use Game.AddToInventory

Use Game.SetLevel

Formerly Game.SetAttribute

Formerly Game.GiveDevPoints

All vehicle commands are documented on the VehicleSystem page linked below.

You can print V's current coordinates to the CET console with the following command:

You will need to know the coordinates of where you want to go in the game world, some popular . Replace X, Y, and Z with your coordinates. Coordinates can also be found in the nodeData of .streamingsector files.

For a more cohesive list of quest facts, check the .

I've installed this mod but nothing happens.

1. Make sure that CET works fine without any mods installed.

2. Make sure the mod that you are installing is compatible with the latest CET.

I've made sure the above are true but the mod still won't function.

You need to bind a hotkey in the Hotkeys tab of the CET overlay. Check how-to here.

I've bound the hotkeys but the hotkeys do nothing when I press it.

The hotkeys only work when the CET overlay is closed.

I've bound the hotkey and I've closed the CET overlay but still, nothing happens.

You need to press the hotkey combination in the right order. For example Ctrl + Shift + S is different from Shift + Ctrl + S

You need to open the CET overlay to interact with anything using your mouse.

You need to change the default font of CET in order for the characters to show properly. You can follow this guide .

Click for the ultimate guide.

1.20.0 - 06/08/2022

Support for patch 1.6

Added

• TweakDB.CreateRecord, TweakDB.CloneRecord, and TweakDB.DeleteRecord now support TweakDBID as a parameter type

-- Get the sticky frag grenade record
sticky_grenade = TweakDB:GetRecord("Items.GrenadeFragSticky")

-- Create a clone of "Items.GrenadeFragSticky" with the name "Items.GrenadeFragStickyNew"
TweakDB:CloneRecord(sticky_grenade:GetID() + "New", sticky_grenade:GetID())

-- Get the new record
sticky_grenade_new = TweakDB:GetRecord("Items.GrenadeFragStickyNew")
-- or
sticky_grenade_new = TweakDB:GetRecord(sticky_grenade:GetID() + "New")

-- manipulate the new record as needed

-- delete record many different ways
TweakDB:DeleteRecord(sticky_grenade_new:GetID())
TweakDB:DeleteRecord(sticky_grenade:GetID() + "New")
TweakDB:DeleteRecord("Items.GrenadeFragStickyNew")

Changes and fixes

• Updated usedhashes.kark to the new URL

• Moved to OpenResty Lua JIT

Support for patch 1.52.1 (made up name, they didn't bother to name it AGAIN)

Support for patch 1.52

• Fix crash on Windows 7.

• Fix LoadTexture overwriting the previously loaded texture.

Support for patch 1.5 hotfix 2

• ImGui.LoadTexture(string path) returns a texture loaded from an image on disk in the mods' directory.

• ImGui.Image(texture) displays a texture loaded with the LoadTexture function.

  Full Api is as follows, note that you may omit parameters after texture and default values will be used (Texture texture, ImVec2 size, ImVec2 uv0, ImVec2 uv1, ImVec4 tintColor, borderColor)

• Added stb to load images.

• Fixed bad screen skip fix.

Support for patch 1.5 v2

• Changed the archive hashes to use the wolvenkit KARK files for TweakDB editing

• red4ext updated to 1.3.1

Support for patch 1.5

• red4ext updated to 1.3.0

• mimalloc updated to 2.0.3

• sqlite3 updated to 3.37.0+200

Special thanks to WopsS, psiberx and Sombra for their help with this patch!

• exEntitySpawner does not work.

• No pedestrian patch is not tested.

• Fix cursor not getting locked to the game.

• Fix skip start screen patch not working.

Support for patch 1.5

• exEntitySpawner does not work.

• No pedestrian patch is not tested.

• Feel free to tell us any other issue that may arise on github/discord.

• mimalloc updated to 2.0.3

• sqlite3 updated to 3.37.0+200

• Improve the d3d12 hook to fix a crash when using ReShade < 5.

• Improve the d3d12 hook to avoid conflicts with other overlays.

Contains: and

• Fixed random crashes when overridden method has a script reference parameter.

• Fixed random crashes when working with game structs.

• Fixed random crashes for very frequently called overrides (such as GameObject.OnGameAttached and GameObject.OnDetach on game reload).

• Added the ability to add new free flats to TweakDB.

Contains: , , and

• Fix bad allocation causing crashes when using some RTTI types

• When using Override() the handler receives the original function (or next in the override chain) as the last parameter

• The wrapped function can be called multiple times

• If any of the overrides fail then the entire override chain also fails

• Observers can be called before and after the target function using ObserveBefore() and ObserveAfter()

• Observe() is an alias for ObserveBefore()

• All observers are guaranteed to be called even if overrides and other observers fail

• It's possible to observe and override static class methods

• Full name should be used when overriding a scripted static method

• Use weak handle for self in overrides. This should decrease the number of unreleased references and make CET less dependent on garbage collection.

• Reuse overridden functions on mods reload. This fixes a potential issue with the native function registry, which has a hard limit on the number of registered functions.

• Support out params in overrides.To properly handle out params in overrides:

• Added support for mods deployed as a symlink for the mod directory

• Added Lua function to check if the mod archive is installed:

• Use FromVariant(variant) to extract the value

• Use ToVariant(value) to pack the value when the type is unambiguous

• Use ToVariant(value, type) when the type is ambiguous or you wanna force the type

• The type of the array is resolved from the first element when possible

• Added event for early TweakDB changes:

Contains: , , and

• Fixed directx12 hooking not working when overlays were present.

• Fixed symlink deployment with Vortex.

• Drop second implementation of Scripting::ToRED() which was very outdated. This was limiting what overridden functions can return.

Will output

• Stricter check of the passed context when calling the RTTI function. Prevents unwanted crashes when invalid value passed as self / this. In particular, it prevents crashes when a dot is accidentally used instead of a colon.

• Support for ISerializable strong and weak references. This opens access to some new classes, but not all of them.

• Workaround for parameterized struct constructor. Previously, fields of a reference type could be corrupted right after construction.

• Support of nulls for strong and weak references.

Assignment example:

Parameter example:

• IsDefined helper function as in redscript. Checks if reference is not null and valid. Can be used on game object's field and lua variable.

• EnumInt helper function as in redscript.

• Support for CRUID type.

• Support for gamedataLocKeyWrapper type.

Support for patch 1.31

Contains:

• Updated to Imgui 1.84.2

Support for patch 1.30 second edition.

Contains:

• Fix disappearing footsteps (1.16.1 regression).

• Alternative syntax for CName and TweakDBID conversions without .new()

• Direct access to global functions.

• Throw Lua errors from RTTI calls as the Lua script will do.

Will print the full callstack in the log:

• Fix channel logs not printing the message.

• Added a new channel "DEBUG" that always prints even when game logs are disabled.

• Re-added TweakDB printing.

• Register global PlayerPuppet.OnAction

Support for patch 1.30 - huge thanks to everyone who helped with this and all testers!

Contains: , , , and

• Fix crash when calling functions that have optional parameters not defaulted.

• Fix crash when using RegisterInputListener from an observer.

Contains: , , , , , , and

• Whitelisted collectgarbage to let scripts force release game references.

• Added exEntitySpawner to spawn entities easily

• Fixed a crash that would occur on machines without ASLR enabled by enabling LuaJIT's GC64 option.

• Fixed nested RTTI calls that would crash the game due to memory release of the previous call's memory.

• Fix the disable anti AA and async compute patches.

• Fix for TweakDB default values.

Contains: , , , , ,

• All game classes are directly accessible by name. For example, entEntityId, PlayerPuppet.

• All game enums are directly accessible by name. For example, gamedataStatType.BaseDamage, gameGameVersion.Current.

• Added WorldFunctionalTests

• Added Imgui.GetStyle()

• Added support for ResourceAsyncReference. Allows editing of TweakDB props of that type by the mods.

• Fixed disappearing footsteps issue.

  • The issue still can occur if the mods do not properly release the player reference.

• The GetMod() is only available after onInit as there is no guarantee that the required mod will be loaded before this event.

• Global fallback table is used now for all mod environments. No need to whitelist what's defined there.

• Aliases like Game['GetPlayer'] = Game['GetPlayer;GameInstance'] aren't needed in autoexec.lua. All global and class functions are automatically resolved by short name now.

• Added implicit class to strong reference conversion.

• Patch for the Minimap flicker

Support for patch 1.22

Fixed

• Crash when using TweakDB:Update in an Observe/Override callback

• Direct3d12 command queue could be null sometimes

• Error logging from Observe/Override callbacks

• Redundant Lua environment passing

Added

• Strings can now be implicitly cast to a TweakDBID when the scripting framework expects a TweakDBID

Support for patch 1.21

Fixed

• Lua scripting errors with functions returning some values with out params

• GameOptions.Toggle() now works

• Fix falsy "Unknown error" when calling a global that returns nil

Added

• Equality comparison to some types (Vector3, Enum, TweakDBID,...)

• Concatenation for TweakDBID

Fixed

• Regressions with GameOptions

• Wrong version info returned back by GetVersion()

• Problems with Console widget history

• 3rd party licences missing

Added

• Modal popups for unsaved changes into Bindings and Settings widget

• Modal popup on first launch asking user explicitly to bind some hotkey for toggling Overlay

• Option to enable removing of dead binds (default is on)

• Option to enable ImGui assertions to make sure mods are not breaking something (default is off)

Changed

• Nicer formatting of headings inside Bindings widget (replace characters that are not alphanumeric by space and autocapitalize each word)

• Reworked Settings menu (options are now split into two categories - Patches and Dev)

• Reworked Bindings menu (separated hotkeys and inputs into two categories)

Added support for patch 1.2.

Fixed

• os.remove and os.rename were not working properly.

• The debug menu patch would not show the menus.

• Fixed dofile, loadfile and loadstring.

• Lua environment would not be applied correctly to some callbacks.

Changed

• Key bindings were improved.

  • Support for scroll wheel.

  • registerInput for single inputs. This handler is similar to registerHotkey, but function now takes one boolean argument denoting if input was pressed/released.

Added

• Re-added the SMT patch for AMD CPUs that did not get a performance boost after CDPR's patch.

• Added Lua's bit32 library.

• TweakDB additions:

Fixed

• Fix memory allocation errors due to missing argument.

• Fix Observe/Override sometimes affecting scripts when they shouldn't.

• Fix crash when using multiple mods.

Fixed

• Crash on game exit when a reference had not been garbage collected by the lua vm.

• Missing enum value CellPadding in Imgui Lua (Pull Request: ).

• Crash when using Override/Observe on pure script functions.

• Crash when reloading mods using Override/Observe.

Changed

• Memory optimization for calls.

• Replaced the hacky thread safety used for the Lua VM with TiltedCore's Lockable<T>.

Added

• API changes to support Imgui 1.81 and added missing ColorButton overloads.

• Override has now 2 overloads to simplify usage, this will completely remove the original function or add one if it doesn't exist:

  • Override(typeName, fullFunctionName, shortFunctionName, function)

Changed

• Upgrade Imgui 1.80 to .

• Fixed Override so that it can override at runtime after scripts have been loaded.

• Revert Lua caching of functions as the new override method will work regardless.

Fixed

• Fix game crash when a script used "require" on a malformed file.

Added

• Override function to either listen to a function or to replace a game function. Despite its name it can also be used to extend a type by adding a new function. Usage is as such:

The first parameter is the class type, second the full name of the function, the third is the short name (usually they are the same), the fourth boolean is used to specify if this is a replacement of the function or not, if set to true it will replace entirely the original function, if set to false, your function will be called before the original function is called. The last parameter is your handler function, note that the parameters are passed according to the RED script definition.

Removed

• Telemetry, the experiment gave us the data we wanted, obviously a lot of people use the mod and we are very happy about that! We are sorry this caused so much drama, it wasn't the intention and quite frankly we still don't really understand why.

Changed

• Calling RED functions used to be cached, given that functions can be overridden at any time the cache has been removed, it's a bit slower but shouldn't be visible in the real world.

• Using the up and down arrows in the console now retrieves the command history

• Added Telemetry so we know how many people use CET (can be disabled in settings), note that we do not store any information we just count the number of players

• Fix TweakDBID issues with large arrays

• Fix TweakDBID crash when using specific functions

Changed

• Updated to game version 1.12

• Updated RED4ext.sdk to the latest

Proper sandboxing ():

• Each mod is (right now) assigned sqlite3 database implicitly, accessible through db lua object (will be changed later to on-demand through info in metadata file)

• Introduced proper sandbox with LuaSandbox helper class

• Bytecode cannot be loaded now (native modules included)

More ImGui stuff(, , , ):

• Enabled ImGui keyboard navigation. (ctrl + tab to switch window, arrow keys to navigate)

• Removed the deprecated power argument in Drag and Slider widgets, replace it with the newer ImGuiSliderFlag (breaking change)

• Made the argument open

TweakDB binding ()

• TweakDB:GetFlat(...)

• TweakDB:SetFlat(...)

• TweakDB:GetRecord(...)

• TweakDB:Query(...)

Changed

• Major vulnerability in the game's save loader fixed

Changed

• Updated to game version 1.11

• Updated RED4ext.sdk to the latest

• Updated to spdlog 1.8.2

• Replaced pattern search with much faster library

• Fix issue when resizing game window (eg. resolution change in Options)

• Fix issue causing game window to stop rendering and freeze on last frame

• Fix ImGui.CalcTextSize overloads (now, second parameter is removed from all, as it did not make sense for Lua anyway)

• Fix Windows 7 flatlining

• Added jsonsupport to Lua

• Added support for the latest patch 1.10

• UI with settings will now ask you for a console key on first launch, you can edit it later

• Mods can now request hotkeys via registerHotkey, the user can pick what key they want to use in the menu

• Scripting is now handling memory correctly, calling Game.GetPlayer() every frame is fine now

• Game doesn't crash when exiting anymore

• dofile is now deprecated, use only mods please, it will be removed entirely in the next update

You can find a .

For a list of console commands for beginners, check out the page:

Checkout the for your first steps:

Check or , for example

Hotkeys

The Hotkeys tab is where you manage all the hotkeys of the mods you installed.

• Binding hotkeys for a mod is the same as how you bind the hotkey for the CET Overlay.

• You can unbind a hotkey by pressing the UNBIND button behind it.

• To save the changes, press the Save button.

• Undefined hotkeys appear in red text. Unsaved changes appear in yellow text.

Remove the following folders/files:

• <cyberpunk install path>/bin/x64/plugins/

• <cyberpunk install path>/bin/x64/global.ini

• <cyberpunk install path>/bin/x64/LICENSE

• <cyberpunk install path>/bin/x64/version.dll

• Removing Cyber Engine Tweaks will not undo any edits made to your character and your save files.

• If you have added items to your inventory, you will not be able to remove them once you have removed this mod. Please ensure you have done so using the first.

• Saves made with the patch should be completely fine without it, thought that might change once proper mods start coming out

The Cyber Engine Tweaks Overlay is the interface that is used to display and set various settings, and configure mods hotkeys.

Additionally, the most advanced mods will also display their own settings window in this overlay. It contains different tabs:

The Settings tab is where you change the Overlay open/close hotkey, and toggle the tweaks to Cyberpunk2077's game engine.

See the following section for more information about the configuration file generated using this UI.

This is a basic guide to using the mod within Proton (aka Linux).

Please make sure your game works in proton first, before installing this mod.

Enabling proton Experimental (Optional)

While this isn't a required step, it's useful for performance.

Right click the game in Steam and select 'Properties'. Go to the 'Compatibility' tab and tick 'Force the use of a specific Steam Play compatibility tool'.

In the dropdown, select 'Proton Experimental'.

Setting up the mod with ProtonTricks

Please note - this method requires the use of Steam. For other options, see below.

First, follow the steps to install the mod. These are in the wiki.

Run protontricks 1091500 --gui, you may get an error saying "You are using a 64 bit WINEPREFIX", you can ignore this. Press 'Ok' when this error appears.

Choose the option 'Select the default wineprefix', then 'Run winecfg'. In the window that opens, select the 'Libraries' tab. In the dropdown on 'New override for library', select version. Click Add, then Apply and Ok.

You can now exit out of Protontricks and start your game. Check to see if the log exists after you run the game. If it's there, you've successfully installed the mod.

If you have issues with the mod still not working or the game just crashing, you can try this: re-open Protontricks like you did before, choose the option 'Select the default wineprefix', then 'Install a Windows DLL or component'. Tick vcrun2022 and press Ok. If a window pops up, then go through the steps to install that runtime (just click next really), otherwise just wait until the Protontricks screen comes back. Now exit out of Protontricks and try launching the game. DON'T do this without first checking if the mod works without this step, since installing vcrun2022 has been observed breaking game installs before, preventing the game from ever launching again and requiring a re-install.

NOTES: You will also need to install d3dcompiler_47 with winetricks to get it to work now, contribution on how to do this would be much appreciated!

If vcrun2019 breaks your install, it's been reported it can be fixed without reinstalling by deleting the contents of/steamapps/compatdata/1091500.

Please note, this method still requires the use of Steam. You must install Cyberpunk 2077 and then add it to your Steam library by following the .

Search for the game APPID with: $ protontricks -s name_of_the_game_on_your_steam_lib

like:

$ protontricks -s Cyberpunk 2077

copy the APPID from the terminal then run:

$ protontricks "APPID" --gui

From now on, you can follow the Setting up the mod with ProtonTricks instructions.

For users running on the GOG version of the game, via launcher like , or , those running from the direct GOG Galaxy Windows application through Wine, or those directly using the Game libraries, Protontricks won´t be helpful in your case, as Protontricks will notice that you don´t have the game on Steam.

Instead, use Winetricks in which Protontricks is derivated from. Please note that you may need to install first, either through the official website or through your distribution's app store.

Lutris users may perform the following steps to activate the mod:

Authenticate with GOG Galaxy by clicking on the small profile icon to the right of the GOG entry. You will then be presented with a list of your owned games. Select Cyberpunk and install it - this will install the base version of the game with no other options selected. You may right click on the game icon after installation and choose the option to install the Phantom Liberty DLC if desired. Once installation is complete, select Cyberpunk 2077 and click on the Winetricks 'wine flute' icon along the bottom of the Lutris window. In the expanded menu, select 'Winetricks'.

Choose the option 'Select the default wineprefix', then 'Run winecfg'. In the window that opens, select the 'Libraries' tab. In the dropdown on 'New override for library', select version. Click Add, then Apply and Ok.

Alternatively, you may run Winetricks in itself if you use your default prefix, or from your custom prefix via: WINEPREFIX=<Location of your WinePrefix directory> winetricks --gui via the terminal.

From now on, you can follow the Setting up the mod with ProtonTricks instructions. If you want to verify in Winetricks has correctly taken in account your custom Wine directory, click on Browse files to see if it brings you to the designated folder.

• This window shows any output done using Redscript's Log/LogChannel function, either coming from the games scripts themselves or from a Redscript mod.

Summary

This page documents CET's in-game Tweak Editor.

Wait, this is not what I want!

• To learn what the TweakDB is, read the page on Cyberpunk 2077 Modding

• For an introduction on TweakDB modding with CET, check the Simple Gameplay Mod guide

• For further information, refer to the section on the scripting wiki

After opening CET with the key that you bound during the , you can find it in the "TweakDB Editor" tab. Here you can browse and update the TweakDatabase in real time.

Cyber Engine Tweaks is a framework that allows modders to interact with the game's internal functions using Lua. It also provides a user-interface with a console and additional tools to assist developers.

GETTING STARTED

For information on how to install Cyber Engine Tweaks, check out the link below.

USAGE

Learn how to use each Cyber Engine Tweaks tabs.

MODDING

Everything you need to know to create your own mod for Cyber Engine Tweaks.

If you wish to contribute to the main repo, try to follow the coding style in the code, otherwise not much to say, don't use code that is not yours unless the license is compatible with MIT.

This page tells you how to install Cyber Engine Tweaks - or you can check the .

1. Make sure Cyberpunk 2077 is updated to the latest version

2. Make sure you installed the latest

3. Make sure you run the game in Windowed Borderless

General Instructions

Key notes on upgrading existing mod for the CET 1.14+:

• Don't use Game object and any game types before onInit.

• Don't use GetMod() before onInit.

• Don't pass excessive params to game functions. If the max number of params is 3, then passing 4 params will result in an error.

• Update Observe() / Override() handlers so they accept self as the first param. Previously, some observers lacked the self param:

• If your mod stores player reference then unset it when game session ends.

  • An unreleased reference can lead to bugs such as disappearing footsteps.

  • Accessing Game.GetPlayer() in onUpdate will not cause the issue.

• Use corresponding getters for game systems instead of GetSingleton(). For example, Game.GetTeleportationFacility() instead of GetSingleton('gameTeleportationFacility').

New scripting capabilities were introduced in CET 1.14 to make it more convenient and simple:

• All game classes are directly accessible by name. For example, entEntityId, PlayerPuppet.

• All game enums are directly accessible by name. For example, gamedataStatType.BaseDamage, gameGameVersion.Current.

All new scripting features are optional. You're not required to rewrite an existing mod using these features.

The new API allows code that is also valid redscript or very close to its redscript counterpart. Thus, it simplifies the research and the transition to / from the redscript.

For example, this line looks exactly the same in Lua and in the redscript:

Constructing objects

Old API:

New API:

Constructor with initialization

Old API:

New API:

Scripted static call

Old API:

New API:

Shorthand static call

Old API:

New API:

Working with enums

Old API:

New API:

Variants

Use a text editor to open the config file at <cet install path>/config.json to adjust the settings.

In this page, we use this example JSON snippet to guide you through adjusting the settings:

{
    // other lines
    "font": {
        "base_size": 16.0,
        "language": "Default",
        "oversample_horizontal": 3,
        "oversample_vertical": 1,
        "path": ""
    },
    // other lines
}

Change font

Locate this line under the "font" curly brace:

"path": ""

Add the path of the font you want to change to between the double-quotes. For example, if you want to change the font to Comic Sans, just change this line into:

Note: You should use slash (/) instead of backslash (\) for the path.

Some mods may have implemented multilingual support. But the non-English characters will display as a question mark "?". This is because the default font only contains .

To display a language that only uses ASCII characters (such as French, German), all you need to do is to change the font to one with a wider range (Literally any font).

To display a language that uses non-ASCII characters (such as Chinese, Russian), besides changing the font, you also need to change this line in the config file under the "font" curly brace:

Here is a table of the "language" options and their descriptions.

For example, to display Chinese all you need to do is:

The result (using the Sim Hei / 黑体 font):

The config file can be found in: <cet install path>/config.json

The config file is structured with two JSON layers, we use the format <first level>.<second level> to represent the key.

Consider the example JSON snippet below, the key for the base size of the font is noted as font.base_size, which carries a value of 16.0.

These are the 0old Cyber Engine Tweaks config file patches for reference.

A guide on how to change the font and font size for Cyber Engine Tweaks and mods based on Cyber Engine Tweaks. And how to display non-English characters.