Forge Bot
Describe a weapon to the AI chat you already use. It interviews you, writes a recipe, and Karsus Codex turns the recipe into a real item.
What is this?
Forge Bot is a bring-your-own-AI forge. Copy our prompt into ChatGPT, Claude, Gemini, or whatever you already talk to. Your AI interviews you about the weapon you want — one question at a time — then writes a recipe: a small JSON document describing the item exactly.
Paste the recipe back and Karsus Codex validates every field, hands back plain-English errors your AI can fix, and lands a good recipe in the weapon wizard for one last look before the build.
Everything on this page works without an account. Importing a recipe needs one — that's where your item gets saved.
We can do this the easy way, or the... easier way.
Larian's official toolkit is a real modding tool, built for professionals, by professionals. That means, like most tools for professionals, it can be hard to navigate for the beginner. While I admire the people who use it with ease, it just wasn't for me. But I still want to make cool stuff!
I figured other people might feel the same, and thus Karsus Codex was born... a wizard for making items. But then I realized it could be even easier, and added Forge Bot, a way to build via chat.
Way one: talk to your AI
Describe the weapon to whatever AI you already use. It writes the recipe, you paste it back here. Fast, no forms, and you never see a dropdown. The prompt provided keeps the JSON formatted correctly, and if it's not, we'll just tell you.
Weapons, for now.
Way two: click through the wizard
Screens, lists, a final summary page before you save the item. No JSON anywhere, and it reaches the parts of the game the recipe format hasn't grown into yet.
Weapons, armor, rings, cloaks, boots, and so on.
Wanna know how? Here's what to do.
Copy one prompt into your AI
There's a prompt sitting on the Forge Bot import page. Copy it, paste it into Claude, ChatGPT, pick your poison. It tells your AI to go read the capability document (the machine-readable list of every weapon type, effect, and passive we can actually build), and then interview you about the weapon you want - one question at a time. If your AI can't browse the web, the same page has the document sitting right there to paste instead. That document is what stops your AI confidently inventing a damage type that has never existed (+1d4 emotional pain isn't a thing; looking at you, Claude).
/api/recipe/capabilities weapon_types 33 · dagger, rapier, greatsword, ...Ask for the thing you actually want
Describe it in concrete terms - a +1 greatsword with frost damage - or skip the stats and just explain what you want. Your AI writes the recipe; in the meantime, karsuscodex.com sits idly by, awaiting your triumphant return. That is to say, we outsourced this step to you, which is either reassuring or suspicious depending on your temperament.
"a rapier that drinks a little health when I crit. tragic disgraced-noble energy. rare, but not so strong it's embarrassing"
Paste it back, review it, get your file
Drop the JSON on the site. If something's wrong we hand back a plain-English error written so you can paste it straight back into the same chat. It'll fix it and you paste again. That loop is the whole thing, really. Once we have valid JSON, it submits and you land on the wizard's review step, so you get one last look - and a chance to fiddle - before you hit build. You can keep editing it to your heart's content in the wizard, or just throw it out and start again. And not even feel bad about it, because it's simple.
When it's valid, you're just a click or two away from downloading it - or you can add it to a mod with other items you made, or from the shared library. Either way, you get a .pak file, ready for your BG3 Mods folder.
Right, you have a .pak. Now where does it go?
On Windows and Mac, the .pak goes in your Baldur's Gate 3 Mods folder, and the in-game Mod Manager takes it from there. Console? Sorry. Truly. We'd help you out if we could - once we get Mod.io integration, maybe?
Documentation coming soon: how to push your creation up to Nexus Mods and mod.io, so other people can play with it too.
OK, so I pasted the JSON and hit the button...
Everything lands in the wizard.
Whether you talked to your AI or clicked your way here, this is the last screen before a mod exists. A valid recipe opens right here, already filled in, so you can see what your AI actually committed you to, and change your mind about any of it.
Check out the wizard - login requiredThings you should know
We think sharing is good
That's the real reason accounts exist. Your items live in your library, where you can come back to tweak them, rebuild them, or bundle them into mods. Everything starts private; mark an item public and it joins the shared library for other people to play with.
Forge Bot builds weapons only, for now
Armor, spells, and consumables are the obvious next things. They are not here today. Saying otherwise would just waste your evening.
It won't balance your game for you
If you generate a dagger that does 4d12 psychic damage, gives you crit immunity, and 30 AC, that's not our fault, and we hope you enjoy.
Patch days can break things
Patches can break things. Ours, or Larian's.
No custom art, meshes, or sounds
Neither Forge Bot nor the wizard currently supports uploading your own art, or generating any. Listen, even Karsus has limits, and we're actually not Karsus anyway.
Why Karsus Codex?
The website exists because I understand the web better than I understand the BG3 Mod Maker tool; Simply put, I got frustrated trying to use the actual toolkit, and figured it would be way easier to use a website like this one, if only it existed. So I spent hundreds of hours to build something to save me dozens of hours. Classic engineering move. You're welcome.
Enough with the blah blah blah, Istik. Let's make something.
TLDR - Make items, easily, for free, from idea to download in a couple minutes. The hardest part is gonna be finding your Mods folder, but we believe in you. Worst case scenario: you end up with a rapier you don't like. We think that's a pretty good deal.