Several of the addon’s systems read their content from JSON files, so a server owner or pack
maker can add, rebalance or replace content without writing any code and without rebuilding
the mod. Everything on this page is done with an ordinary Minecraft datapack.
| System | Folder | Hot-reloads |
|---|---|---|
| Titles | titles/ |
Yes |
| Records | records/ |
Yes |
| Crates | crates/ |
Yes |
| Forge recipes | forge_recipes/ |
Yes |
| Nation achievements | nation_achievements/ |
Yes |
| Nation perks | nation_perks/ |
Yes |
| Nation missions | nation_missions/ |
Yes |
| Nation spawner tiers | nation_spawner_tiers/ |
Yes |
Everything else — skills, magic, races, synergies — is defined in code and cannot be added by
datapack. You can still tune most of their numbers in the server’s config files.
All paths are relative to your datapack’s data/elitetensura/ folder:
my_pack/
├── pack.mcmeta
└── data/
└── elitetensura/
├── titles/
│ └── my_title.json
├── records/
│ └── my_record.json
└── crates/
└── my_crate.json
A minimal pack.mcmeta for Minecraft 1.21.1:
{
"pack": {
"pack_format": 48,
"description": "My Elite Tensura content"
}
}
Drop the folder (or a zip of it) into your world’s datapacks/ directory, or into the pack’s
global datapack folder if your launcher supports it.
Run /reload in game. Every system listed above re-reads its folder immediately — you do not
need to restart the server to test a change.
Two things to know about reloads:
id of a fileFor every system, the file name is the id. titles/frost_walker.json defines a title whose
id is frost_walker. There is no "id" field inside the file — if you add one it is ignored.
Ids are referenced by other content (a title requiring another title, a mission granting a
perk), and by admin commands, so pick stable names and avoid renaming files later.
Built-in content and datapack content live in the same registry. To replace a built-in entry,
create a file with the same id and set "replace": true:
{
"display_name": "Slime Slayer",
"rarity": "epic",
"replace": true,
"requirements": [ { "type": "kill", "entity": "tensura:slime", "count": 500 } ],
"bonuses": []
}
Without "replace": true the built-in definition wins and your file is ignored. This is
deliberate — it stops a stray file from silently changing progression.
To remove a built-in entry entirely, override it with something harmless: give it
requirements no one will meet, or an empty bonus list.
/reload, then check the server log. Malformed JSON is reported with the file name.The built-in content follows a power budget per rarity — see the table on the
Titles page. If you want custom content to feel like it belongs, aim for the
same budget at the same rarity. Bonuses stack with everything else a player has equipped, and
players can run up to 10 titles at once, so a single overtuned title compounds fast.