Get the most out of Conny.
Think of Conny as a developer you just brought on. Tell it who you are, what your server is and what you’re after, and the work gets a lot better.
How Conny works
Conny reads your files, logs and console, makes a change, then checks whether it worked. What it can’t do is log in and play. So when something can only be judged in game, like how a fight feels or whether a build looks right, you’re its eyes.
Start by saying hi
A new developer would ask you these on day one. Answer them up front and Conny won’t have to guess.
-
Tell Conny about yourself.
In your first chat, say how long you’ve run servers, whether you code, and how you like to work.
I've run servers for 3 years and I don't code. Keep explanations short, and always back up before big changes.
-
Tell it about each server.
What kind of server it is, and where it’s at: still an idea, in development, or live with a handful of players or a few hundred.
This is a survival server with a player economy. It's live, with about 40 players most nights.
- Bring your team in. Memory belongs to the workspace, so whatever one of you teaches Conny, it remembers for everyone. Invite people from People → Members.
- Connect GitHub. When Conny writes a custom plugin, its source code lives in your own GitHub organization. If the server ever goes, you still have the code. How to connect GitHub.
Pick a tier
Conny has three intelligence tiers. Higher tiers think harder and use more of your allowance.
- Basic is for when you know exactly what you want and just need it done, like “give Steve VIP.”
- Balanced is where most work should happen: small and medium plugins, most fixes, and config or creative setup.
- Thorough is for the hard stuff: complex plugins, digging into a tricky problem, or systems with lots of moving parts like an economy. It’s noticeably smarter, and it uses your allowance much faster.
Not sure? Start on Balanced, and switch up if Conny starts going in circles. You’ll find the tier next to the send button 1.
Keep chats short
The longer a chat gets, the slower and pricier each reply becomes, and the more Conny has to keep track of. A few habits help:
- Stick to one topic per chat. When you move on to something different, start a new chat. Memory comes with you, the clutter doesn’t.
- Keep an eye on the Context bar 2. It shows how full the chat is.
- Compact when a feature’s done 3. Conny boils the chat down to what matters and carries on. Don’t leave it to auto-compact, which only kicks in at the limit, usually halfway through something.
Plan big jobs first
Before a new plugin or a big change, start with “let’s plan…”. Conny lays out how it would do it, you change what you don’t like, and only then does it build. Ten minutes of planning saves a lot of fixing.
Memory
- Say “remember”. When you settle something, like a decision, a quirk of your setup or what players call a place, tell Conny to remember it. Every future chat starts out knowing it, and so do your teammates’.
- Check the Memory page once in a while 1. Conny can get things wrong, or hold on to things that have since changed. Fix or delete those 2, because old memory leads to bad guesses.
Big builds take longer
Conny is built to be efficient. It runs on models picked for good results at a fair price, not the most powerful ones money can buy. That covers nearly everything you’ll do with a server.
Most of the time, Conny checks its own work. It changes a config, restarts, reads the console and sees whether it worked. If not, it tries again. That loop of try, check, fix is what makes an agent good at its job.
Some work breaks that loop. Conny can’t join your server, so it can’t watch a minigame round play out, see an animation or look at a model. It only finds out something went wrong when you tell it. That’s why big plugins with lots of systems working together, like minigames, complex world animations and custom models, are the hardest thing to ask for. They’re full of edge cases, and without seeing them Conny is working half blind. Fix one thing it can’t test, and something else can quietly break.
They can still be done. Here’s how we’d go about one:
- Plan it properly first. Start with “let’s plan…” and go through every system, plus what should happen when things go wrong: a player leaves mid-round, two players grab the same item, the server restarts during a game.
- Use Thorough. This is exactly what it’s for.
- Build one system at a time. Treat each one as its own feature. Build it, test it, compact, then move on to the next, instead of asking for the whole plugin at once.
- Be Conny’s eyes. Test each piece in game and tell Conny exactly what you did, what you expected and what actually happened, plus any errors in chat or the console. Expect a lot of back and forth. That’s normal for this kind of plugin.
Try it on your server
Sign in, connect your server, and tell Conny a bit about yourself.