Set up Oraxen on your Minecraft server

Oraxen adds custom items, blocks, glyphs (custom textures that show wherever text appears), paintings and music discs to a Paper server without any mods for your players. You describe each item in a text file, and Oraxen builds a resource pack from your textures and models and sends it to players when they join. Oraxen is a paid plugin, bought from SpigotMC or BuiltByBit, so you install the jar by hand rather than from the Plugins tab store.

Checked against Oraxen 1.220.1, released 14 October 2026, whose documentation lists Paper, Purpur and Folia on Minecraft 1.20.1 to 26.3, and whose SpigotMC page lists Java 21 as a requirement.

What you need

• A Paper server. Oraxen works with most Paper forks such as Purpur and Folia, but it is a Paper plugin and cannot load on Spigot or CraftBukkit.
• Java 21. Oraxen is built for Java 21, and a server on Java 17 cannot load it. Our panel picks Java from the Minecraft version: Java 17 up to Minecraft 1.20.4 and Java 21 or newer from 1.20.5. So use Minecraft 1.20.5 or newer, up to 26.3, which you can pick in the JAR Manager. A server on 1.20.1 to 1.20.4 runs Java 17, so Oraxen cannot load there.
• No CommandAPI. Oraxen's SpigotMC page still says it requires CommandAPI, but Oraxen 1.220.1 registers its commands with its own code, and its source and build files never mention CommandAPI. Read the Console on the first start for anything it reports as missing.
• On Paper 1.21.2 and newer Oraxen does not need PacketEvents. Older servers use PacketEvents for packet-based features, and Oraxen's documentation gives no install steps for it, so Paper 1.21.2 or newer is the simple route.
• The jar from your purchase. The latest release on the project's GitHub page has no jar attached, so the store's GitHub button cannot fetch it.

Take a backup in the Backups tab before you start, as Create and restore backups explains.

Install it

1. Download the jar from the page where you bought it: the SpigotMC listing or BuiltByBit.
2. Open the File Manager, go into the plugins folder and click Upload. The jar is about 3 MB, well under the browser upload limit.
3. Open the Console tab and click Restart, or Start if the server is stopped.
4. Type plugins in the console. Oraxen should be green.

The first start creates plugins/Oraxen with a settings.yml, an items folder for item files and a pack folder for textures and models. It also writes the default items and pack assets that ship with the plugin.

How players get the pack

Oraxen uploads the pack it builds, and players are sent it when they join. By default it uses Oraxen Atlas, a free hosting service run by the Oraxen team. In settings.yml that is type: polymath with server: atlas.oraxen.com. Atlas needs no extra port. It is blocked in Russia and China, so players there need another host.

Leave that setting alone unless you have a reason. The self-host option makes your server serve the pack from port 8080, which must be reachable from outside, and plans can differ in how many extra ports they include. See Add an extra port to your server.

Add your first item

Oraxen reads item files from plugins/Oraxen/items. An item picks a base material and points at a model file in the pack folder:

my_item:
  material: IRON_SWORD
  pack:
    model: weapons/swords/ice_sword

Put the model JSON in plugins/Oraxen/pack/models/weapons/swords and its texture in pack/textures. Use lowercase letters and underscores in every file name. Then run oraxen reload all in the console to rebuild the pack and reload everything.

In the game, /oraxen give <targets> <item> hands out an item and /oraxen inventory opens a browser of all items. The root command uses the permission oraxen.command, which everyone has by default, and these two add oraxen.command.give and oraxen.command.inventory.view. Oraxen does not declare those two, so Paper gives them to operators only. Make yourself an operator in the Players tab, under Operators, to use all three.

Common problems

• The pack does not apply. Read the Console for Oraxen errors, then delete plugins/Oraxen/pack/pack.zip and run oraxen reload pack.
• You already have a resource pack. Put its zip or folder in plugins/Oraxen/pack/uploads and reload. Oraxen merges it, and the last pack processed wins when files clash.
• Updating. Back up the plugins/Oraxen folder, swap the jar in the File Manager, restart and read the changelog for config changes.