Skip to content
Using Codexe

Downloads and artifacts

How to download a project's source as a ZIP or the built JAR, when a JAR exists, and what each project type produces.

Updated

On this page
  1. Source (ZIP)
  2. Built JAR
  3. What each type produces
  4. No JAR?

Every project can be downloaded as a ZIP of its source, at any time. Java plugins and mods can also be downloaded as a built JAR once their current files build.

#Source (ZIP)

Download in the project toolbar (and Source ZIP in Settings → Download) gives you every file of the project as a ZIP. This works for every project type at any time. The source is yours: you can build it yourself, host it or keep editing it elsewhere.

#Built JAR

Java projects (Spigot/Paper/Folia/BungeeCord plugins, Fabric/Forge mods) can also be downloaded built, with Download JAR:

  • If the current files already built successfully (during verification or a Compile), you get that JAR immediately.
  • Otherwise Codexe compiles first and then gives you the JAR. If the build fails you get the errors instead of a JAR.

The JAR is named after the project, for example SimpleHomes.jar. Codexe checks it before handing it over: it must contain compiled classes and the descriptor your server or loader needs.

#What each type produces

TypeWhat you download
Plugins (all Bukkit-family, Folia, proxy)Source ZIP, and a plugin JAR for plugins/
Fabric / Forge modsSource ZIP, and a mod JAR for mods/
DatapackZIP of the datapack folder (pack.mcmeta + data/), for world/datapacks/
SkriptZIP with the .sk files, for plugins/Skript/scripts/
Discord botZIP of the bot project (run it with Python or Node.js)
Static website / ReactZIP of the site or app
Blockbench modelZIP of the project files

#No JAR?

A JAR only exists for Java project types, and only when the build succeeds. See Download missing or no JAR.

Downloads and artifacts | Codexe Docs