Introducing Terminus Config Sharing

What is a config in Terminus?

A config is a saved snapshot of your entire setup at a point in time: which modules are turned on, every value and slider inside them, your keybinds, and how your HUD is arranged on screen. Instead of rebuilding your setup from memory every time you switch modes or reinstall, you save it once and reload it in a click. Think of it less like a settings file and more like a loadout you can name, keep, and swap.

This has always been a small annoyance in the minigame space specifically. A BedWars setup and a SkyWars setup want different things, and re-tuning half a dozen modules by hand every time you switch queues gets old fast. Config sharing exists to remove that friction entirely.

Why a config system matters for BedWars and SkyWars

BedWars and SkyWars are close cousins but they do not reward the same setup. BedWars is tighter and more defensive, with bed protection and generator control shaping most fights. SkyWars is looser, with more open mid-air and island combat and less reason to babysit a structure. A HUD layout and set of values tuned for one tends to feel wrong in the other.

Saving and switching your own configs

1. Tune your setup for one mode

   Get your modules, values, keybinds, and HUD arranged the way you want for a specific mode, say BedWars.

2. Save it as a named config

   Give it a name that tells you what it is for later, like "BW Defense" rather than something generic. Future you will thank present you.

3. Repeat for your other mode

   Build a second config for SkyWars, or for any other setup you keep switching in and out of, like a practice or duels config.

4. Switch instantly between queues

   Load the matching config the moment you change modes. No slider-hunting between games, no half-remembered values.

Sharing configs with other players

A config that works well does not have to stay on one account. Terminus configs can be shared with other users, so a setup you spent an evening dialing in can help someone else skip straight to something that already works, and you can pull in a setup someone else has already proven out for a mode you are new to. It turns tuning from a solo chore into something the wider Terminus community contributes to together.

Built without the scripting-engine overhead

Some clients ship a full embedded scripting runtime like GraalVM so users can write their own automation on top of the client. Terminus deliberately skips that layer. Running a scripting runtime adds real startup time and memory overhead whether or not you ever write a script, and for a client built specifically around fast-paced minigames, a light footprint and quick launch matter more than an optional feature most players never touch. Config sharing gets you most of the practical benefit, saved and swappable setups, without carrying that weight.

FAQ