Project Settings

The gear icon in the Code Studio: per-project AI model and rules, build tool, Java and Minecraft version, publishing and connectors, by project type.

Where to find them

Open any project in the Code Studio and click the gear icon in the toolbar. Settings are stored per-project and override your global defaults.

The seven sections a plugin shows, grouped under two headings: Project (Info, Build, Editor, AI) and Ship (Publish, Connectors, Styling) — in the app each carries a small icon. A web app swaps Publish for Site & SEO and drops Styling; a Discord bot drops Styling. On a phone the sidebar becomes a list of full-width rows under the same two headings; tap one and that section opens on its own screen.

The sections — and why you never see all of them at once

There are eight sections in the code, but the sidebar filters them to your project type, so no project ever shows all eight:

Info — name, version, description, author and website (and your project's icon, once it has one)
Build — build tool, Java version, Minecraft version and what the plugin targets
Editor — editor options for this project
AI — model, Rules, reasoning effort and the Skills picker
Publish — how the project appears if you share it, and where the icon generator lives
Connectors — the services this project may use: GitHub, a verified sending address, a Discord webhook — see Project Connectors
Site & SEO — web apps and Arcade games only, and it replaces Publish rather than sitting beside it: how the published site introduces itself to search engines and link previews
Styling — how your plugin's in-game chat messages look, so it is dropped on web apps, games and Discord bots. Everything else keeps it — configs, datapacks, Skript, YAML and even a README project all still show the tab

In practice: a plugin shows seven, a web app six (Site & SEO instead of Publish, and no Styling), a Discord bot loses Styling. The first four are grouped under Project and the rest under Ship.

Build, Editor and AI carry a small ! mark in the sidebar when they override your global defaults, and the sidebar footer counts how many sections do.

Styling — presets for how your plugin talks

The Styling section deserves a word of its own, because it is more than a colour picker: it is a preset — font style, colour prefix, border and bullet glyphs, and the overall vibe — written into your plugin's messages.yml and GUI titles. That is what your players actually see in chat.

The preset you pick here is one setting for your whole account, not for this project: it is where the AI Guided wizard starts your next plugin, and the same picker there lets you change it for that plugin. Requests in a project that is already open do not read it, so changing it here does not restyle this project — ask the chat for the new style instead. (The hint under the picker still says otherwise.) Besides the built-in presets there are community presets, and you can upload and share one of your own.

The Styling tab

Styling is about your plugin's voice in the game, not about web pages. You pick a font style, a colour prefix, a border glyph, a bullet glyph and an overall vibe, and those are written into the plugin's messages.yml. You can also upload a preset of your own and share it.

The AI tab is a list of Rules now

The AI tab used to have two big text boxes — AI Instructions and Project Context. Both are gone. In their place is Rules: a list of short cards, one rule each, in two scopes:

Global rules — ride along in every project you own. "Always answer in English" belongs here, and you write it once.
Project rules — apply to this project only, and win when the two disagree.

You add one with the dashed add a rule row at the foot of either list. Each card saves the moment you click it — the dialog's Save Changes button is only for the model picker above and the AI Thinking override below. See AI Instructions for how to write good ones.

If you had text in the old boxes, nothing was thrown away: the vault offers to turn it into cards, and does not clear the old text until you press the button.

A rule that says what this project is — "a Paper 1.21 shop plugin using Vault" — is still worth writing; it just goes in as a project rule like any other, rather than into a separate box. Do not confuse it with Connecting a Chat to a Project in AI Chat: that feature only tells a conversation your project's name and its top-level file and folder names, and it does not send your code.

The Build tab in full

Beyond the build tool and the Java and Minecraft versions:

What does this target? — tick every platform your plugin is for, from nine: Bukkit, Spigot, Paper, Purpur, Pufferfish and Folia, plus the proxies Velocity, BungeeCord and Waterfall. All the servers together still make one jar; adding a proxy makes two, and a line underneath says which you are getting. Decide this early; see Plugin Generator for why it is not a late switch
Main class path — the class the server loads. It is not filled in for you: the box is empty behind a greyed-out example until you or the AI put something in it, and it is only worth touching if you have restructured the project by hand
Custom dependencies — Maven coordinates and uploaded jars; see Custom Dependencies
Auto-compile after each change — builds the project every time the AI finishes editing, so you find out about a break immediately instead of at the end
Stop on compile error — on by default. When a build fails you see the errors and the AI waits, instead of starting an auto-fix by itself, so a failed build cannot turn into a build-fix-build loop that spends your credits

The Publish tab in full

This is the tab that decides how your project looks to everyone else, and most of it is never seen until someone opens your public page:

Store links — your SpigotMC resource URL (a URL only; there is no username field for SpigotMC), your BuiltByBit / MC-Market username and resource URL, your Discord username and server invite, and your GitHub repository. They are saved with the project, but nothing shows them yet: they do not appear on your public project page
The icon generator — this is where an icon is made: a background style and a Generate Icon button. See Plugin Icons
Store description — one description, one Generate button, and a format switcher: Plain text, BBCode (for BuiltByBit, MC-Market and SpigotMC) and Markdown. You edit the Markdown version; the other two are made from it, and switching format costs no AI call
Manual .jar upload — for when you built the file yourself instead of using Cloud Build. Up to 100 MB, and it is scanned before it is stored. The file is recorded on the project as a build, marked as a manual, unverified upload, and that build becomes your project's download — read Uploading Your Own Build for what it accepts

What you can configure

AI model — pick a different model for this project only (e.g. a more capable model for tricky logic, a faster one for speed)
Rules — global and project, as cards; see above
Reasoning effort — Model default, Off, Minimal, Low, Medium, High or Max (only some models support this)
Skills — apply any of your skills to this project
Build tool — Maven or Gradle. You can change it at any point, but switching after code exists means the build files have to be regenerated, so decide early where you can
Java version — the JDK the build targets
Minecraft version — target API version
Author / version — written into plugin.yml and pom.xml

Renaming — three depths on a Java project

The project name is not changed here but in the toolbar: click the name at the top-left of the Code Studio (a pencil appears when you hover it) and a Rename project dialog opens. On a project that does not compile, that is the whole story — type the name, press Rename.

On a plugin or mod the button reads Continue and a second screen asks how far should the rename go?, because the name is also written into your code:

Project name only — renames the label. Source files, package and main class stay untouched — safe and reversible
Project + main class name — also renames the JavaPlugin main class and updates plugin.yml's main entry. The package path stays the same
Project + main class + package — the full refactor: the package segment, the main class, plugin.yml, and every import rewritten. Use it when you want a clean identity

The Info tab does one related thing: when plugin.yml names a different plugin from your project, it shows Name mismatch detected with a Sync button that renames the project to match the file.

Global defaults live in Profile → Preferences → AI Assistant. Project settings always win when both are set.

Also in Code Studio (IDE)

Next in Code Studio (IDE): Editor & Themes
Starting out: Starting a New Project — Four ways to start a project: Quick Create, AI Guided, Advanced Mode and Import from ZIP. Which one suits you, and why simpler project types show three.
Building web apps: Web App Studio — Real web apps with pages, accounts and data — dashboards, shops, booking systems.
Building web apps: The Template Shelf — Ready-made web apps to start from, in a room of their own at /templates.
Building web apps: A Cinematic Website Opening — A page that tells a story as the visitor scrolls, made in the web app wizard's Motion step. What the three cards cost, how the Frames board works, and when credits are taken.

3 of 37 in Code Studio (IDE) · Last checked 18 September 2026 · Previous: Your Projects List