If you are trying to make your setup "portable" (easy to move to another server), here is the best workflow:
version: '3.8'
services:
minecraft:
build: .
ports:
- "25565:25565"
volumes:
- ./world:/minecraft/world
- ./plugins/ItemsAdder/output:/minecraft/plugins/ItemsAdder/output
restart: unless-stopped
With this setup, you can literally git clone your repository on a new VPS, run docker-compose up -d, and your ItemsAdder server is live.
If you are a developer, you should treat your ItemsAdder configuration as code. Using Git makes your setup ultra-portable. itemsadder portable
Before diving into the how, let's look at the why. Most server admins treat their ItemsAdder setup as a "dirty" installation—fraught with absolute paths, missing dependencies, and fragmented resource packs.
Now you must define what my_portable_chair_placed is. This is the actual block that sits in the world. If you are trying to make your setup
You define this in the blocks section of the config (usually the same file).
blocks: my_portable_chair_placed: # What the block looks like (Model engine model or vanilla block) material: BEDROCK # Using a solid base material # If using custom models: specific_properties: model_path: "blocks/furniture/chair"# This ensures it drops the item back to the player drop: silktouch: false looting: false item: my_portable_chair # The item name defined in Part 2.1 # Settings for how the block behaves hardness: 1 # How hard it is to break break_sound: block.stone.break
"ItemsAdder Portable" emerges as a compact, user-friendly iteration of ItemsAdder — a popular Minecraft plugin that lets server owners add custom items, blocks, GUIs, and textures without modifying client files. The “Portable” variant reframes that capability around mobility, minimal setup, and rapid deployment, targeting server admins who need flexibility: pop-up events, temporary servers, LAN play, mod-lite demos, or cross-server testing. version: '3