resourcepack.ai
DOCS

Resource packs

Exporting

Exporting turns your pack into a file you can install, upload to a server, or hand to a friend. You don't need to export to test a pack: Sync sends it straight to your game (see the Quickstart).

Which export do I need?#

There are several export targets, one for each place a pack can go. Pick by where it's going:

You want toChoose
Use it in your own Java game, or send it to every player from server.propertiesMinecraft: Java Edition
Use it in a Bedrock world or RealmMinecraft: Bedrock Edition
Give it to Bedrock players on a Java server running Geyser (without RP Engine)Bedrock players on a Java server
Use your Dialogs without RP EngineDialogs (minecraft:dialog)
Add it to a server running ItemsAdder, Nexo, Oraxen, CraftEngine or Model EngineThat plugin's name, on the Plugin Support tab

Running RP Engine, our plugin? You don't need any of these for your server: Distribution sends the pack to your players for you.

Exporting a pack#

Open the pack and press Export (or right-click its card and choose Export), then pick a target. The file is built on the spot from what's in the pack right now, and downloads.

All the targets#

The Export dialog has two tabs.

Default Pack is for files you install or serve yourself, with no other plugins involved:

ExportFileUse it for
Minecraft: Java Edition.zipThe ordinary resource pack. Goes in resourcepacks, or on a server
Minecraft: Bedrock Edition.mcpackThe Bedrock version, converted. Open it on any Bedrock device to import it
Bedrock players on a Java server.zipThe .mcpack plus the item list Geyser needs, for a server running Geyser without RP Engine
Dialogs (minecraft:dialog).zipYour Dialogs as a vanilla datapack

Plugin Support is for servers running another plugin that makes custom items and builds its own resource pack. What you get isn't a resource pack: it's your content in that plugin's format, and the plugin builds the pack from it.

ExportFileUse it for
Model Engine.zip of .bbmodelAnimated models on a server running Model Engine or BetterModel
ItemsAddercontents folderA server running ItemsAdder
Nexo.zipA server running Nexo
Oraxen.zipA server running Oraxen
CraftEngine.zipA server running CraftEngine

Every plugin export includes a README.txt listing each item id, anything that couldn't be carried over and why, and any model left out because it hadn't finished generating.

Animations need RP Engine

In the Java .zip, a model shows but stands still: vanilla Minecraft can't play model animations. Playing them needs RP Engine on the server. Bedrock can play animations itself, so the .mcpack keeps them.

Installing the Java pack#

Put the .zip in your resourcepacks folder and turn it on in Options › Resource Packs:

# Windows
%APPDATA%\.minecraft\resourcepacks
 
# macOS
~/Library/Application Support/minecraft/resourcepacks
 
# Linux
~/.minecraft/resourcepacks

To send it to everyone on a server, upload the file somewhere players can download it and set resource-pack (its link) and resource-pack-sha1 in server.properties. That needs nothing of ours installed, and the file keeps working if you never open Studio again.

Bedrock#

Bedrock uses a different pack format, so the .mcpack is a conversion. Open it on any Bedrock device and it imports itself; then turn it on under the world's Resource Packs.

In a world on its own, a .mcpack shows your Block and Item reskins, Sounds, Armor and Icons. Custom items, models and 3D Armor need a server: a Java server running Geyser (with RP Engine for all of it, or with the Bedrock players on a Java server export for custom items). GUI screens, the HUD, Shaders, Dialogs, Emotes and Vehicles don't exist on Bedrock and are left out. Bedrock and Geyser has the full list and the steps for each route.

Dialogs as a datapack#

A Dialog is a menu screen with real buttons. Minecraft keeps Dialogs in a datapack (a world's data folder), not a resource pack, so they have an export of their own:

pack.mcmeta
data/studio/dialog/<id>.json          each dialog
data/studio/dialog/<id>.<page>.json   each page after the first

Put the zip in your world's datapacks folder and restart the server (/reload isn't enough, because dialogs are loaded with the world). Then open one with /dialog show @s studio:<id>. Dialogs need Minecraft 1.21.6 or newer.

The pictures inside a Dialog are in the Java pack, so players also need the Java pack exported at the same time, or the screen is blank. If you keep a resource pack of your own, the dialog editor's JSON › minecraft:dialog › Resource pack (.zip) downloads just that dialog's pictures and fonts; see Dialogs › Without RP Engine.

On a server without RP Engine, the parts that change per player don't work: {placeholders} show as typed, settings switches stay on their default, live heads, inventory slots and bars are empty, and /rp clicks do nothing. The editor's JSON › minecraft:dialog view lists which of those a dialog uses.

Model Engine and BetterModel#

Model Engine and BetterModel are server plugins for animated models. This export gives them your 3D Models as Blockbench files, one .bbmodel per model, with every texture it uses packed inside.

blueprints/
  your_model.bbmodel
README.txt

Model Engine: copy the files into plugins/ModelEngine/blueprints/, run /meg reload, then /meg summon <model> to look at one. Command names vary between Model Engine releases, so run /meg on its own for your version's list.

BetterModel: reads the same files. Copy them into plugins/BetterModel/models/ and reload BetterModel.

Checkerboard models mean the pack isn't being sent

Model Engine writes its textures to plugins/ModelEngine/resource pack/ and stops there. Players who aren't sent that pack see the model as a black-and-magenta checkerboard. If ItemsAdder runs on the same server, add this to ItemsAdder's config.yml, then /meg reload, /iazip and rejoin:

merge_other_plugins_resourcepacks_folders:
  - "ModelEngine/resource pack"

Otherwise, merge that folder into whatever pack your server already sends.

What to expect:

  • Models only. Block textures, item sprites, GUIs and icons belong in the Java zip or one of the other plugin exports.
  • Bones keep their tree. A child bone sits inside its parent, so it moves with it. A model with no bones gets one root bone.
  • A hitbox bone is added, sized to the model. Redraw it in Blockbench for a different collision box. Mount and seat bones (mount, p_*) are not written.
  • Animations don't start on their own, and Model Engine has no command to play one. It plays a few names automatically as entity states (idle, walk, jump, death, spawn), so an animation named Idle loops on any summoned model. Names are snake_cased, so "Idle Wave" becomes idle_wave and won't auto-play. Anything else needs MythicMobs, Model Engine's API or a plugin such as MEGAnim.
  • Triggers don't come across. On loop, on click and on range are RP Engine ideas. The README.txt lists each model's animation names as exported.

If a rig looks wrong in game, open its .bbmodel in Blockbench: what you see there is what Model Engine renders.

ItemsAdder#

ItemsAdder is a server plugin for custom items, blocks and furniture. It builds and sends its own resource pack, so this export is your pack as ready-made ItemsAdder content, with the config written for you.

contents/<your-pack>/
  configs/items.yml            furniture, items and custom blocks
  configs/font_images.yml      icons and GUI overlays
  resourcepack/assets/
    <your-pack>/               your models, textures, icons and sounds
    minecraft/                 the vanilla files your pack replaces
datapacks/<your-pack>_dialogs/ your dialogs, if any
RPEngine/content/<your-pack>/  the same dialogs, for RP Engine
README.txt

Merge the zip into plugins/ItemsAdder/. It already contains contents/, so unzipping it inside contents/ gives you contents/contents/ and ItemsAdder finds nothing. Then:

/iazip                                  rebuild the pack
/iaget <namespace>:<item>               give yourself one
/iagive <player> <namespace>:<item>     give someone else one

Ids are lowercased with other characters turned into underscores: a model called "Floating Sword" in a pack called "My Pack" is my_pack:floating_sword.

In your packBecomes
3D modelFurniture: right-click the floor with it to place it, hit it to break it. Its hitbox is barrier blocks measured from the model
3D itemAn item with a custom model, held rather than placed (on PAPER; change material in items.yml if you like)
Custom blockAn ItemsAdder note-block block: hardness 2, stone sounds, drops itself, faces whoever placed it if directional
VehicleFurniture with one seat you can sit in, not drive
2D custom itemAn item built from its sprite
IconA font_image, with a character ItemsAdder chooses. Use its ItemsAdder placeholder
Sound<your-pack>:<event>, playable with /iaplaysound. A sound replacing a vanilla one still replaces it
GUI replacing a vanilla screenA vanilla file replacement
GUI overlayA font_image, with its ready-made title string (such as :offset_-176::gui_bank_vault:) in the README.txt
Block or item reskinA vanilla file replacement
DialogA datapack folder and an RP Engine folder

The export never writes the files ItemsAdder owns (paper.json, blockstates, the default font) and sets no CustomModelData, so it can't clash with content you already have.

Things to know:

  • Vanilla replacements apply to every player. Delete any you don't want from resourcepack/assets/minecraft/ and run /iazip again.
  • Re-export after editing a GUI. The overlay's title string is measured from its art, so an old title won't line up with new art.
  • Animated models arrive static. ItemsAdder doesn't play keyframes.
  • Sounds replacing vanilla ones go in a sounds.json that ItemsAdder merges with its own. ItemsAdder releases older than December 2023 don't merge it; on those, delete that file or ItemsAdder's custom block sounds go quiet.
  • Dialogs need Minecraft 1.21.6+, and /iazip before anybody opens one. With RP Engine 0.2.1 or newer, merge the zip's RPEngine/ folder into plugins/, run /rp reload, and open one with /rp dialog <your-pack>:<id> <player>; RP Engine fills in placeholders, settings, bars and inventories. Without it, move the datapack folder into your world's datapacks/, restart, and use /dialog show <player> studio:<id>; nothing per-player is filled in. A dialog synced from the editor won't work on an ItemsAdder server, because its characters clash with ItemsAdder's.

Nexo and Oraxen#

Nexo and Oraxen also build the pack themselves. These two exports are the same content written in each plugin's format.

Nexo/                                      Oraxen/
  items/<your-pack>/items.yml                items/<your-pack>/items.yml
  glyphs/<your-pack>/glyphs.yml              glyphs/<your-pack>/glyphs.yml
  pack/external_packs/<your-pack>/           pack/uploads/<your-pack>/
datapacks/<your-pack>_dialogs/             datapacks/<your-pack>_dialogs/

Unzip it straight into plugins/, then:

/nexo reload all                    /oraxen reload all
/nexo give <player> <item>          /oraxen give <player> <item>
In your packBecomes
3D modelFurniture: hold it, or right-click a block to place it, with a hitbox measured from the model
VehicleFurniture with the vehicle's seats, to sit in
Custom blockThe plugin's own note-block block
2D custom item, 3D itemAn item, keeping its name and base item
Vanilla item in 3DThe vanilla item, reskinned
IconA glyph: <glyph:<pack>_<icon>> in the plugin's text, :icon: in chat. It keeps its character
GUI overlayA glyph, with its title string (such as <shift:-48><glyph:my_pack_gui_shop>) in the README.txt
Pause-menu buttonsThe redrawn buttons
SoundsMerged in under your event names
Block, Item, Armor or GUI reskinA vanilla file replacement
DialogA datapack folder

Both plugins merge fonts, sounds.json and language files, so the export sits beside what your server already has. It sets no CustomModelData and picks no block states; the plugin chooses those and writes them back into items.yml.

Dialogs go in your world's datapacks/ folder, then restart and use /dialog show <player> studio:<id> (Minecraft 1.21.6+). Vanilla replacements apply to every player: delete any you don't want from the pack folder's assets/minecraft/ and reload.

Some things only RP Engine can draw while the game runs, so they can't be expressed in these plugins' config. The README.txt names each one your pack has: shader objects, 3D Armor, model animations (models place as still furniture), driving (vehicles are furniture you sit in) and dialog settings switches (they open, but only RP Engine remembers a choice).

CraftEngine#

CraftEngine builds its pack from one folder per pack. This export is that folder.

CraftEngine/resources/<your-pack>/
  pack.yml
  configuration/items.yml          items, furniture and blocks
  configuration/images.yml         icons, GUI overlays and chat emoji
  configuration/categories.yml     a category in the item browser
  resourcepack/                    models, textures, sounds, replacements
datapacks/<your-pack>_dialogs/

Start CraftEngine once before you unzip

CraftEngine only installs its own default packs into an empty resources/ folder, and custom blocks need them. Unzip into a server that has already started with CraftEngine.

Unzip into plugins/, then:

/ce reload all                       rebuild and resend the pack
/ce item get <your-pack>:<item>      give yourself one
/ce                                  the item browser, with your pack as a category

It maps the same way as Nexo and Oraxen, with these differences:

  • Custom blocks are real CraftEngine blocks, with their own hardness and drop. CraftEngine picks the block state.
  • Furniture can be turned by sneak-clicking it with an empty hand.
  • Icons are images (<image:<pack>:<icon>>) and also chat emoji typed as :icon: in chat, books, signs and anvils. GUI title strings use <shift:-48><image:my_pack:gui_shop>.
  • Characters are pinned. images.yml holds one invisible image, <your-pack>:reserved, that keeps the characters your pack uses for spacing and dialog art free. Leave it in, or another pack's emoji can land on one of them.
  • It doesn't use CraftEngine's bundled templates, so it still loads if you've removed default_templates.

Dialogs and the RP Engine-only features work as described for Nexo and Oraxen.