Repository navigation
Customization
Part of the Create: Storage wiki.
Parts of Create: Storage can be customized without code. This page explains which kind of pack does what, and links to the reference pages:
| Page | Pack type | What it covers |
|---|---|---|
| Tags | Datapack | Disabling upgrades, ore mining, refill blacklist, storage network, and more |
| Jukebox Buffs | Datapack | Which buffs each music disc gives with the Jukebox Upgrade |
| Backpack Models | Resource pack | Backpack models, textures, and Portable Workshop flywheels |
| Config Reference | Config file | Every server and client config option |
| I want to… | Go to |
|---|---|
| Disable a backpack upgrade in my pack | Tags → disabled_backpack_upgrades |
| Make the Ore Mining Upgrade recognize a modded ore | Tags → ore_mining_block |
| Stop the Refill Upgrade from refilling an item | Tags → refill_blacklist |
| Stop the Symmetry Wand mirroring a block | Tags → symmetry_wand_blacklist |
| Add a modded block to the storage network | Tags → storage_network_block |
| Give a music disc Jukebox Upgrade buffs, or change them | Jukebox Buffs |
| Retexture or reshape the backpacks | Backpack Models |
| Move, resize or remove the Portable Workshop flywheels | Backpack Models → Workshop flywheels |
| Change the magnet range, health bonus, network range… | Config Reference → Server config |
| Turn off Jukebox buffs entirely | Config Reference → jukebox_upgrade |
| Turn off Jetpack Modifiers (including Elytra Boost) | Config Reference → jetpack_upgrade |
Datapacks change gameplay data: tags, recipes, and Jukebox buffs. They are loaded by the server, so every player gets the same result.
my_pack/
├── pack.mcmeta
└── data/
└── fxntstorage/
├── tags/item/disabled_backpack_upgrades.json
└── jukebox_songs/cat.json
pack.mcmeta for Minecraft 1.21.1:
{
"pack": {
"pack_format": 48,
"description": "My pack's Create: Storage tweaks"
}
}-
Installing: put the folder (or a
.zipof it) in the world'sdatapacks/folder. Modpacks usually ship it through a global datapack mod (e.g. Paxi or Open Loader) or as KubeJS data, so it applies to every new world. -
Applying changes: run
/reload. No restart is needed. -
Namespaces: a file's location decides what it changes. A tag file belongs at
data/<tag namespace>/tags/..., so to add to a Create: Storage tag the file goes underdata/fxntstorage/, even in your own pack. -
Tags merge: a tag file adds its values to the mod's tag. Add
"replace": trueonly if you want to throw the mod's default values away.
Everything on the Tags page can also be done from a KubeJS server script (kubejs/server_scripts/):
ServerEvents.tags('item', event => {
event.add('fxntstorage:disabled_backpack_upgrades', 'fxntstorage:backpack_flight_upgrade')
})
ServerEvents.tags('block', event => {
event.add('fxntstorage:ore_mining_block', 'mymod:tin_ore')
})Resource packs change how things look: models and textures. They are loaded by each player's client.
my_resource_pack/
├── pack.mcmeta (pack_format 34 for 1.21.1)
└── assets/
└── fxntstorage/
├── models/block/backpack.json
└── textures/block/backpack.png
-
Applying changes: press
F3 + Tin game. - A server can't force a look on players unless it sends the resource pack as a server resource pack.
Numeric limits and on/off switches live in two config files rather than packs. See the
Config Reference for every option and where each file lives. To ship your own defaults in a
modpack, put a copy of the server config in defaultconfigs/.