How to build a tree
Double-click empty space or press + Skill to add a skill. Drag skills to arrange them. To make one skill require another, drag the yellow dot under the first skill onto the second. Click a line and press Delete to remove a requirement. Select a skill to set its name, icon, cost, number of ranks, required player level and effects. A skill can need all of its requirements, shown as solid lines, or any one of them, shown as dashed lines, which is how tech trees often offer two routes to the same goal.
Play mode
A tree can look fine on paper and still feel bad. In play mode you are a player: pick a level, see how many points you have and click skills to buy ranks. Locked skills are faded and skills you can buy have a dashed outline. Try level 5, 15 and 30. Can a player reach the first strong skill early? Is there a real choice, or is one path always best? Can a max level player buy everything, or do they have to choose?
Using the tree in your game
The JSON holds every skill with its id, cost, ranks, level, requirements and effects, plus its position so you can draw the tree in your own UI. The Pro scripts for Godot 4 and Unity read the same JSON and give you can_unlock, unlock, refund and rank, plus get_state and set_state for save files. Effects are kept as text lines like damage +10% so your own code decides what they do.
Is my tree uploaded?
No. Everything runs in your browser and your tree is saved on this device.