Debugging first
Paste a compiler error, a crash log, an ASSERT failure or a SQL error. Codder reads the evidence, names a probable root cause and changes what is broken — not the whole file.
The first AI Coder from Bulgarian Legion
Codder
Built for developers. Made for serious code. Codder is a specialist assistant for systems, database and World of Warcraft emulator development — and it knows that TrinityCore, AzerothCore and MaNGOS are not the same thing.
Free plan, no card required. Codder can make mistakes — review and test generated code before deploying it.
worldserver crashes on boss pull. Stack showsUnit::GetVictimreturning null in my ScriptedAI. TrinityCore 3.3.5.
CodderTrinityCore 3.3.5
Root cause: the AI is dereferencing the victim inside UpdateAI before checking it. On 3.3.5 the target can be cleared mid-combat — evade, feign death, or a taunt-immune despawn — so the pointer is valid atEnterCombatand null a tick later.
// guard before every victim access
void UpdateAI(uint32 diff) override
{
if (!UpdateVictim())
return;
events.Update(diff);
}UpdateVictim() both re-acquires a target and returns false when there is none, which is why it replaces a bare null check here.
Illustrative example. Codder reviews and reasons about code — it does not compile or run it.
What people ask Codder
- Create a TrinityCore master CreatureScript for this encounter.
- Why is this AzerothCore module crashing during PlayerLogin?
- Convert this TrinityCore 3.3.5 SQL to the correct current schema.
- Analyse this worldserver crash log.
- Optimise this C++ function without changing its behaviour.
Capabilities
A coding assistant, not a chatbot
Codder is tuned for one job: helping you write, understand, debug and maintain real software.
Branch-aware answers
TrinityCore master and 3.3.5 are not the same core. Codder works out which one you are on from your project, your code and your history, and refuses to mix their APIs.
Memory that you control
Your OS, compiler, core branch, database version and coding conventions carry across conversations. Every memory is visible, editable and deletable — or switched off entirely.
Projects as context
Give a project its core, branch, toolchain, database and namespace once. Every conversation in it inherits that context, so Codder stops asking.
Reads your files
Upload .cpp, .h, .sql, .lua, .conf, CMakeLists.txt, patches and crash logs. Uploaded content is treated strictly as data — never as instructions to the model.
Reasoning you can dial up
Standard for quick work. Deep and Max buy a stronger model, a larger context window, higher output limits and queue priority — real backend differences, not an animation.
WoW core expertise
Four ecosystems, kept apart
Most assistants treat every emulator as one blurred codebase. Codder holds a separate model of each core, and will ask which one you are on rather than guess when the answer would differ.
TrinityCore (master)
Modern emulator development against the current branch — DB2 hotfixes, present-day packet structures and the ScriptMgr surface as it exists today.
- DB2 and hotfixes
- Modern ScriptMgr
- Current packet layout
- C++17 and later
TrinityCore 3.3.5
Wrath of the Lich King scripting and core work — DBC data, the classic ScriptMgr registration, BossAI and EventMap encounter patterns.
- DBC data
- ScriptedAI and BossAI
- EventMap and TaskScheduler
- SmartScripts
AzerothCore 3.3.5
Module-first 3.3.5 development — hooks, module CMake wiring, .conf.dist configuration and the script classes AzerothCore adds on top of its TrinityCore ancestry.
- Module architecture
- Extended hook surface
- Module CMake and config
- Eluna where installed
MaNGOS 3.3.5
Legacy emulator development — the original MaNGOS architecture, ScriptDev2 conventions and a database layout that is genuinely its own.
- ScriptDev2 conventions
- realmd auth database
- Legacy C++ style
- Distinct class surface
Languages and formats
Systems work, not web pages
Codder covers application, systems, database and game-server development. Website and web-application building is outside its supported scope — it will say so plainly rather than produce something it is not built for.
- C
- C++
- C#
- Java
- Python
- Lua
- SQL
- Bash
- PowerShell
- CMake
- JSON
- YAML
- XML
- Config files
How memory works
Tell Codder once
Chat history and memory are separate systems. History is the transcript of one conversation. Memory is the small set of durable facts about how you work — and it follows you into every new chat.
- 1
You mention it once
You say your source is on TrinityCore master, you build with Visual Studio 2022, and your database is MySQL 8.4.
- 2
Codder keeps what lasts
Durable facts are stored. Passing chatter is not — and credentials never are: anything that looks like a password, key or connection string is rejected outright.
- 3
Only what is relevant comes back
Memories are retrieved by relevance to the question in front of you, not dumped wholesale into every request.
- 4
You stay in control
The Memory page lists everything Codder remembers. Edit it, delete it, clear all of it, or turn memory off completely.
Things Codder remembers about you
Primary development target is TrinityCore master branch.
core preference
Builds on Windows 11 with Visual Studio 2022.
environment
World database runs MySQL 8.4.
project fact
Prefers scripts over core modifications where possible.
coding style
Wants the root cause stated before any code.
communication
Example of the Memory page. Yours starts empty.
Plans
Pay for capability, not for theatre
Paid plans change what happens on the server: a stronger model, a bigger context window, higher output limits, deeper reasoning and queue priority.
Free
Evaluate Codder on real work.
Free/month
- 30 messages per day
- 450 per month
- 12K context window
- Standard reasoning
- 1 project · 25 memories
- 128 KB per upload
Plus
PopularDeep reasoning and room to work.
€9/month
- 200 messages per day
- 3,000 per month
- 48K context window
- Standard · Deep reasoning
- 10 projects · 150 memories
- 512 KB per upload
Pro
Max reasoning on the strongest configured model.
€24/month
- 800 messages per day
- 12,000 per month
- 128K context window
- Standard · Deep · Max reasoning
- 50 projects · 500 memories
- 2048 KB per upload
Full comparison on the pricing page.
Security and privacy
Your code stays yours
Private by default
Conversations, projects, files and memories are scoped to your account. Ownership is enforced in the query, not as an afterthought.
Uploads are data
File content is fenced as untrusted input. Instructions hidden inside a source file or log are treated as text to analyse, never as commands.
Nothing is executed
Codder reads and reasons about your code. It does not compile it, run it, or connect to your servers — and it will never claim it did.
Delete what you like
Remove a chat, a project, a memory, all memories — or your entire account, along with its conversational content.
FAQ
Questions
Does Codder understand the difference between TrinityCore master and 3.3.5?
Yes, and it treats them as separate cores. Codder works out which branch you are on from your project settings, your stored preferences and signals in your code, and asks when the answer would genuinely differ. It will not hand you master-branch API for a 3.3.5 server.
Can Codder build me a website?
No. Web and web-application development is outside Codder supported scope. It focuses on application, systems, database and World of Warcraft emulator development — C, C++, C#, Java, Python, Lua, SQL, Bash, PowerShell, CMake and configuration formats.
What is the difference between Standard, Deep and Max?
Real backend differences. Deep and Max route to a stronger configured model, allocate a larger context window and higher output limits, retrieve more memories and project files, and get priority in the generation queue. The reasoning mode is enforced on the server, not hidden in the interface.
Does Codder compile or run my code?
No. Codder reviews and reasons about code; it does not execute it, connect to your database or touch your server. It is instructed never to claim otherwise, and it will tell you what needs verifying on your side.
What happens to files I upload?
They are stored privately against your account, outside any web-served directory, and are readable only by you. Their content is passed to the model as clearly fenced data, so instructions hidden inside a source file or log cannot redirect Codder.
Is the Free plan actually usable?
Yes. Free includes a genuinely useful daily allowance, Standard reasoning, projects, memory and file uploads, so you can evaluate Codder on real work before deciding whether to pay.
Can I delete my data?
Any conversation, project, file or memory, at any time. You can clear all memories at once, switch memory off entirely, or delete your account — which removes your conversational content and anonymises your record.
What are we building or fixing today?
Create an account, tell Codder which core you are on, and start with the bug that is actually blocking you.