How to Make Cyberpunk 2077 Mods With AI

You can make Cyberpunk 2077 mods with AI by choosing one small change, matching it to a mod type (a Cyber Engine Tweaks Lua script, a TweakXL YAML tweak or a redscript hook), giving an AI assistant the author documentation and your exact versions, and testing every draft against the game’s logs. The assistant writes the text. You check it, because assistants invent function names.

This guide is for PC players who have already installed mods and want to build a small one of their own. The code samples below come from the framework authors’ documentation and are linked where they appear. They are not AI output we tested in the game, which is the point: whatever your assistant drafts needs the same check.

What AI can and cannot make for Cyberpunk 2077

An AI assistant produces text, so it fits mods that are text files: Lua scripts for Cyber Engine Tweaks (CET), YAML tweaks for TweakXL and scripts for redscript. It does not fit mods that are art. Meshes, textures and animations are built in tools such as WolvenKit, an open-source tool for reading and writing the game’s file formats. An assistant can explain the steps around that work, but it cannot make the 3D model.

Two limits apply to every route:

• The assistant has never run your game. A draft that looks right in a chat window can still fail on your patch. The game’s own logs decide whether it works.
• Names must be exact. Game scripts use exact class and function names, and assistants sometimes write plausible ones that do not exist. Check every name against NativeDB, the database of classes and functions that the RedModding wiki lists among its CET resources.

Pick the mod type that fits your idea:

If you are unsure, start with a TweakXL tweak or a CET hotkey. Both are a few lines long, both are easy to remove, and a failure shows up quickly.

Before you start: a safe test setup

1. Back up your saves from C:\Users\<Username>\Saved Games\CD Projekt Red\Cyberpunk 2077\ and keep a manual save from before any mod.
2. Install only the framework your route needs, from the author’s release page for your game version, then launch the game once to confirm it still starts. The PC install guide covers file placement, and the dependency checker lists what each framework needs.
3. Write down your versions: the game patch (this site covers Patch 2.5) and the framework release you downloaded. You will paste them into your prompt.
4. Test on a spare save, and keep one ZIP of your mod folder every time it works so you can return to the last good copy.

Step 1: Pick one small change

Write the idea as one sentence with a result you can see:

When I press the key I bound, the game adds 1,000 eddies to my inventory. Nothing else changes.

That sentence has a trigger, one effect and a limit. It also gives you the success check for step 4.

Scope is what separates a first mod that works from one that never does:

Then choose the mod type from the cards above. A key press or a small window points to CET. Changing values on existing records points to TweakXL. Changing how the game’s own scripts run points to redscript. The Scripting Cyberpunk wiki is the RedModding wiki’s home for CET and redscript documentation.

Step 2: Brief the AI with real documentation

Most failed AI mods fail at the brief, not at the code. An assistant asked for “a Cyberpunk mod that gives money” has to guess the framework, the game version and the function names. A good brief removes the guesses:

Copy this and replace the Goal and Environment lines with your own:

Act as a Cyberpunk 2077 modding assistant. Write one Cyber Engine Tweaks mod.

Goal: When I press a hotkey I bind in CET, add 1000 eddies to my inventory.
Success check: my eddies go up by 1000 once per key press and nothing else changes.

Environment:
- Cyberpunk 2077 Patch 2.5, PC, Windows
- Cyber Engine Tweaks (release I downloaded: <version>), no other mods
- File: bin/x64/plugins/cyber_engine_tweaks/mods/eddie_hotkey/init.lua

Reference (follow these, do not guess):
- https://wiki.redmodding.org/cyber-engine-tweaks/cet-functions/hotkeys/registerhotkey
- https://nativedb.red4ext.com

Rules:
- Use only functions that appear in the references above.
- Print one line when the mod loads so I can see it in the CET console.
- At the end, list every function or class you are not sure exists.
- Return the full init.lua and a three-line install note. No other files.

The same shape works for the other routes. For TweakXL, give the assistant the YAML Tweaks wiki page. For redscript, give it the wiki’s hook guide. Prefer these maintained pages to a 2021 video or forum post: the game and the frameworks have changed since, and an assistant follows whichever source you hand it.

When the draft comes back, ask for a check before you install anything: “Show every game function you used and where I can confirm it exists.” Then look each one up in NativeDB yourself.

Step 3: Put the files in the right folder

Here is what a correct CET hotkey looks like. It is the example from the CET wiki’s registerHotkey page, and a good draft from your assistant should resemble it:

registerHotkey('give_money', 'Give Money', function()
    Game.AddToInventory('Items.money', 1000)
end)

According to that page, hotkeys must be registered at the root level of init.lua, outside any event, and you bind the key afterwards in CET’s Bindings tab, where the label (“Give Money”) is what you see.

A TweakXL tweak is shorter still. The YAML Tweaks wiki shows a record name followed by the property to set:

Vehicle.v_standard2_archer_bandit_player:
  enableDestruction: false

For redscript, the wiki recommends wrapping a method rather than replacing it, because several mods can wrap the same method and still work together. This is the hook guide’s skeleton, with your own code going where the comment is:

@wrapMethod(DamageSystem)
private func ProcessLocalizedDamage(hitEvent: ref<gameHitEvent>) {
    wrappedMethod(hitEvent);
    // your custom code goes here
}

If you use a different file name or folder from these examples, tell the assistant. It will otherwise assume its own.

Step 4: Test and read the logs

Launch the game and check the success condition from step 1. If it does not work, the logs say why. Where to look depends on the route:

Then run the loop:

1. Copy the exact error line and a few lines around it.
2. Paste it with your current file and say: “This error appeared on Patch 2.5. Change only what the error requires and explain the change.”
3. Replace the file, reload and test again.

Two habits save the most time. Change one thing per round, so a new error has one possible cause. And if the assistant offers a different function name every round, stop guessing and look the class up in NativeDB yourself. If three rounds get you nowhere, shrink the goal: a mod that does one small thing and works beats one that tries three. If the game will not launch at all, take your file out and follow the flatline crash fix to find the cause.

Step 5: Package it with a README

Once it works, make it easy for someone else to install and remove:

• A folder layout that mirrors the game folder. Zip it so the player extracts it into the game root, as the install guide describes for other mods. For the CET example, the ZIP holds bin/x64/plugins/cyber_engine_tweaks/mods/eddie_hotkey/init.lua.
• A README with what it does, requirements with versions, the game patch you tested on and the date, install steps, uninstall steps (delete the file or folder), known issues and credits.
• Only claims you tested. “Tested on Patch 2.5 with this CET release” is useful. “Works with everything” is not.
• A version number, such as 0.1.0, and a re-test after each game patch. Frameworks move with patches, and older releases stop working.
• A note on AI use. Say which parts the assistant drafted and that you tested them.

Step 6: Share it

• On this site. Open Share something in the Community and sign in. An existing link is not required for original work, and every submission is reviewed before it is published, so add your README text, the version and screenshots of it working in the game.
• On a mod site. Nexus Mods asks uploaders to tag generative-AI use accurately. Shacknews’ report on its July 2026 update describes tags for AI-Generated Content, AI Media and AI Assisted. Check the site’s current rules before you upload.
• Keep it free. CD PROJEKT RED’s Fan Content Guidelines allow reasonable donations but not paywalls or paid-only access.
• Credit others. If your mod builds on someone else’s work, link to it and follow its permissions instead of re-uploading it as your own.

A mod made on these routes is a PC mod. PlayStation 5 and Xbox Series X|S use the in-game Mods menu instead, covered in the PS5 and Xbox guide.

Mistakes to avoid when you make Cyberpunk 2077 mods with AI

• Trusting a name you have not looked up. Check every class and function in NativeDB.
• Following an old tutorial. Give the assistant current documentation and your patch number.
• Changing five things at once. One change per test keeps the log readable.
• Running anything extra. These mods are text files. If an assistant tells you to download and run a program to “install” one, stop and ask where it comes from.
• Testing on your main save. Use a spare one.
• Publishing code you cannot explain. Ask the assistant to explain each line, and read the answer.

Frequently asked questions

Next steps

You now have a repeatable way to make Cyberpunk 2077 mods with AI: one small change, a brief that cites the docs, a test against the logs. Start with the smallest version of your idea. Once your first hotkey or tweak works, read the PC install guide to see how other mods are laid out, use the dependency checker to document your requirements, and share the result in the Community.