eras.yml: the server-wide timeline.nodes.yml: the upgrades players unlock.
Add an Era
Add eras undereras in eras.yml.
- Use an internal id without spaces, such as
STEAM. display-nameis the readable name.ordercontrols the era order. Every era should have a unique number.goalmakes the era fundable with/evolve contribute.- Eras without
goalare not normal contribution targets. blocked-materialsuses Bukkit material names, such asELYTRA.effectsuses potion effect ids, such asspeed,haste, orresistance.
PRIMITIVE as the first era unless you are intentionally rebuilding the full timeline.
Add a Node
Add nodes undernodes in nodes.yml.
- The node id, such as
steam_engine, is used by commands and requirements. eramust match an era id fromeras.yml.requirementsare parent node ids that must be unlocked first.lockoutsare nodes blocked after this one is unlocked.rewardsare console commands. Use<player>for the player name.moneycosts require Vault plus an economy provider.items.materialmust be a valid Bukkit material name.
- the server has reached that node’s era,
- all required parent nodes are unlocked,
- the player is not locked out of the node,
- all costs can be paid.
Position the Tree
Each node has adisplay position:
x: left and right.y: height.z: depth away from the tree origin.
config.yml to scale or move the whole tree:
/evolve tree after edits to check spacing. Use /evolve clear to remove the projection.
Edit Existing Nodes In-Game
Node Studio can edit existing nodes without opening YAML:- display name,
- description,
- requirements,
- lockouts,
- costs.
nodes.yml.
Customize Visuals and Text
Use these files:config.yml: tree colors, hitboxes, animation, layout, editor GUI slots, contribution suffixes.lang.yml: messages, command output, hologram text, and GUI item text.
