Skip to content
Using Codexe

Compile

Compile runs a real, fresh build of the project's current files, the same build Codexe uses to verify projects, and shows the log, the errors and the resulting JAR.

Updated

On this page
  1. Which projects have Compile
  2. What Compile does
  3. Verified vs modified projects
  4. When the build succeeds
  5. When the build fails
  6. Does Compile use tokens?
  7. Limits

Compile is real. When you press it, Codexe builds the project's current files from scratch in an isolated build environment. It never shows a cached "success" from an earlier build.

#Which projects have Compile

Compile is available for Java projects:

TypeBuild tool
Bukkit / Spigot / Paper (Java), FoliaMaven
Bukkit / Spigot / Paper (Kotlin)Gradle
BungeeCord / VelocityMaven
Fabric, ForgeGradle

Datapacks and Skript don't compile. Codexe checks them by loading them on a real test server during delivery (see Datapacks and Skript). Discord bots, websites and Blockbench models have nothing to compile.

#What Compile does

  1. Takes the project's files exactly as they are now, including your own edits.
  2. Chooses the Java version from the Minecraft version in your build files (Java 17 for older versions, 21 for 1.20.5 and newer, 25 for 26.x), or higher if the project setting asks for it.
  3. Runs the build (Maven package, or Gradle build) with dependencies from the official repositories.
  4. Checks the output is a real plugin or mod: the JAR must contain compiled classes and the right descriptor (plugin.yml, bungee.yml / velocity-plugin.json, fabric.mod.json, mods.toml).
  5. Streams the log and shows the result in the project chat.

It's the same build Codexe runs when it verifies a project before calling it Ready, so "Ready" and "Compile passes" describe the same thing.

#Verified vs modified projects

  • Unchanged since Codexe verified it: Compile should pass, because the same files already built.
  • You edited files, or the AI changed them in chat: Compile tells you whether the new version builds.

#When the build succeeds

The result shows Download JAR. See Downloads.

#When the build fails

The result lists the errors with file and line, plus two buttons:

  • Fix with AI: if the files are exactly what Codexe delivered, Codexe repairs them for free with its internal repair. Otherwise the errors go to the chat as a normal follow-up. See Auto Repair.
  • Re-check: runs Compile again, for example after you edited a file.

#Does Compile use tokens?

No. Compiling doesn't use tokens. Only the AI uses tokens (generations and chat messages).

#Limits

  • Plugin builds stop after 5 minutes and mod builds after 10. The first mod build can take several minutes because Gradle and the mod toolchain download their dependencies.
  • Compile is paused while Codexe itself is verifying or repairing the project.
  • Builds run isolated from the internet except for the official dependency repositories, so a build script that downloads from an unknown site will fail. See Security.
Compile | Codexe Docs