Templates are only useful if they start you in the right world. Vibeforge organizes templates by workload so Minecraft servers and Voxel Game sessions stay coherent, runnable, and easy to iterate.
TL;DR
- Workloads are the “output type” (Minecraft server vs Voxel Game session).
- Templates are curated starting points inside a workload.
- Choose a template based on the first-session loop you want, not a giant feature checklist.
- Start here: browse templates or pick a workload.
What is a workload?
A workload is a category of runnable output: it defines what we deploy, how players join, and what “done” means.
- Minecraft: a hosted Minecraft server baseline (config + add-ons + join details).
- Voxel Game: a runnable voxel session with a coherent world pack + join instructions (beta).
Why templates are split by workload
Minecraft and voxel sessions look similar from the outside (“a world friends can join”), but the deployment, tuning, and iteration constraints are different. Splitting templates by workload keeps the defaults stable and the instructions unambiguous.
- Better reliability: the template assumptions match the runtime.
- Fewer dead ends: you don’t pick a Minecraft template when you meant a voxel session.
- Cleaner iteration: prompts and “what changed” stay comparable across runs.
Minecraft templates
Minecraft templates start from a stable server baseline and suggest compatible building blocks (plugins/mods, rules, and performance defaults). See Minecraft templates or the Minecraft workload page.
Voxel Game templates (beta)
Voxel templates optimize for a fast prompt-to-play loop: coherent pack, runnable session, join instructions, then iterate. See Voxel templates or the Voxel Game workload page.
How to choose a template
- What’s the first 5 minutes? Explore? Build? PvP? Progression?
- Who’s playing? Friends, a community, or an open server?
- What’s “success”? “Two friends can join and understand what to do in 60 seconds.”
- What can wait? Start small, prove join works, then add complexity.
Iterate safely after you deploy
The goal is not infinite creativity. The goal is a reliable loop: prompt → runnable session → join proof → iterate.
- Change one thing at a time so you can tell what improved.
- Prefer defaults that keep worlds playable under load.
- Keep a rollback plan (backups + known-good template).
Start browsing templates
Pick a workload and start from a stable baseline: browse templates. For early access updates, join Discord.
Ready to build a server or world?
Join the waitlist for early access. Pick a workload, start from a template, and iterate by chatting.