Frequently asked questions

Codder is an AI coding assistant from Bulgarian Legion, specialised in application, systems, database and World of Warcraft emulator development. It is built for C, C++, C#, Java, Python, Lua, SQL, Bash, PowerShell, CMake and configuration formats.

TrinityCore master, TrinityCore 3.3.5, AzerothCore 3.3.5 and MaNGOS 3.3.5. It treats them as four separate ecosystems with different APIs, database layouts and conventions, and will ask which one you are on when the answer would differ.

No. Web and web-application development is outside its supported scope. It will say so and offer the nearest thing it can help with. Questions about a server application that happens to speak HTTP are fine.

No. It reviews and reasons about code. It does not compile, execute, deploy, connect to a database or touch your server, and it is instructed never to claim otherwise.

Chat history is the transcript of one conversation. Memory is a small set of durable facts about how you work — your core, branch, operating system, compiler, database and conventions — which carries across every conversation.

Only durable statements from your own messages, and only after they pass a filter. Passing chatter is not stored, and anything resembling a password, key, token or connection string is rejected outright. Content inside uploaded files is never turned into memory.

Yes. The Memory page lets you view, edit and delete every stored memory, clear them all at once, or switch memory off entirely. Turning it off stops both collection and retrieval.

A project holds persistent context — target core, branch, operating system, compiler, database, namespace and your own custom instructions. Every conversation in that project inherits it, so Codder stops asking.

Source (.c, .cpp, .h, .hpp, .cs, .java, .py, .lua), SQL, logs, patches, CMake files and configuration (.conf, .conf.dist, .ini, .json, .yaml, .xml). Text formats only — archives and binaries are rejected.

No. Uploaded content is wrapped in a trust fence with an unguessable per-request delimiter and labelled as data. A source file containing "ignore all previous instructions" is analysed as text, not obeyed.

Only you. Ownership is enforced in every database query, and administrators see counts and metadata — never the content of your conversations.

Any conversation, project, file or memory, at any time. You can also delete your account entirely, which removes your conversational content and anonymises your record; only the minimum billing rows required for accounting are retained, without personal identifiers.

Yes. Free includes a real daily allowance, Standard reasoning, projects, memory and file uploads, so you can evaluate Codder on genuine work before paying anything.

A stronger configured model, a larger context window, higher output limits, more retrieved memories and project files, priority in the generation queue, and deeper analysis instructions. All of it is enforced on the server.

No. When a generation fails for a reason on our side, the message is automatically refunded to your allowance and the interface says so.