Troubleshooting
Compile failed
Why a manual Compile can fail on a project that was Ready, how to read the errors, and when Fix with AI is free.
Updated
On this page
#Why did Compile fail on a Ready project?
Compile builds the current files. The usual reasons it fails after the project was Ready:
- The files changed after verification: you edited something, or a chat change hasn't finished verifying.
- Something outside the code: a dependency repository was unavailable, or the build timed out (5 minutes for plugins, 10 for mods). Try Re-check.
If the files are exactly what Codexe delivered and the build still fails, that's Codexe's problem to fix, and it's free.
#What to do
- Read the error list in the Compile result: each error shows the file and line.
- Press Fix with AI:
- files unchanged since Codexe delivered them: a free internal repair runs (you'll see Fixing an issue…);
- files changed: the errors are sent to the chat as a normal message (uses tokens).
- If you just edited a file to fix it yourself, press Re-check.
#Reading common errors
| Error | Meaning |
|---|---|
cannot find symbol | A class, method or variable doesn't exist in the API version you're building against, or an import is missing. Say your server version. |
package … does not exist | A dependency is missing from pom.xml / build.gradle. Name the plugin or library you use. |
incompatible types | A method returns something different in this API version. |
Could not resolve … | A dependency version doesn't exist, or its repository isn't one Codexe can reach. |
release version 21 not supported | The project targets a newer Java than the build used. The Java version comes from the Minecraft version; state it clearly. |
#It builds but doesn't work in-game
Compile proves the code builds, not that the feature behaves correctly. Describe the in-game behaviour in the chat. See Common platform errors.