Skip to main content
Evolve+ is configured through YAML files in plugins/EvolvePlus. For step-by-step examples, see Customization.

Files

Eras

Each era is defined under eras.
Important fields:
  • order: Determines progression order.
  • goal: Money required for global contribution progression.
  • requirements: Node ids associated with this era’s intended milestone path.
  • blocked-materials: Materials blocked until later eras.
  • effects: Potion effects applied while the era is active.

Nodes

Each node is defined under nodes.
Node fields:
  • name: Display name in the tree and editor.
  • description: Marketplace-facing and in-game description.
  • era: Era the node belongs to.
  • requirements: Parent nodes required before unlock.
  • lockouts: Mutually exclusive nodes to lock after unlock.
  • rewards: Console commands executed after unlock.
  • display: Floating tech tree position.
  • costs: Money, XP, and item requirements.

Contribution Suffixes

Configure player-friendly amount suffixes in config.yml.
This lets players type commands such as /evolve contribute 1m.

Discord Webhooks

Evolve+ can post rich Discord webhook embeds for era transitions, node unlocks, and contributions.
After setting the webhook, run /evolve discord test. Keep mention-era-transitions disabled unless you intentionally want Discord role pings when a new era starts.

Hologram Layout

The floating tech tree is controlled under hologram.
Use display positions in nodes.yml for individual node placement and the hologram.layout section for global scaling, offsets, and interaction tuning.

Database

For local testing, Evolve+ can run in memory. For production, MongoDB is recommended.
Redis is optional and only needed for cross-server synchronization.