How-To Guides
Complete tasks, start to finish — each one ends with something working on your screen.
The rest of this manual is organized by thing: a page per widget, a page per frontend, a page per config file. That is the right shape when you know what you’re looking for and the wrong shape when you don’t. These guides are organized by goal instead.
Each one walks a single job end to end, and each one crosses features on the way. Building a hunting layout touches the window catalog, five shell zones, three widget types, and a saved layout file — four manual sections you’d otherwise have to find and sequence yourself. The guide sequences them for you.
They teach a path. The feature pages own the facts, so every step links back to the page behind it — when you want the full field list for a widget, follow the link rather than expecting a guide to repeat it.
The guides
Build a hunting layout Reach for this when your default screen is still the six windows it shipped with and you want the screen you’ll actually fight in — vitals, roundtime, targets, and a compass, saved so you can get it back.
Make your health bar shout when you’re hurt Reach for this when you’ve died to a health bar you didn’t look at, and you want your screen to demand attention instead of waiting for it. (Nothing blinks — the guide explains what actually happens instead.)
Set up highlights and sound alerts Reach for this when the line that matters — your bounty creature, a bleeder, someone saying your name — scrolls past in the same color as everything else.
Put VellumFE on your phone Reach for this when you want your character on a second screen beside the keyboard, or in your hand away from the desk.
Wire a hotbar for combat Reach for this when you’re retyping the same attack, stance, and spell-prep sequence every hunt and want them as buttons that gray out while they’re on cooldown.
Before any of them
Every guide assumes you are connected and looking at a session. If you are not there yet, start with Installation and First Launch, then come back.
Each guide is tabbed by frontend — Desktop GUI, Terminal (TUI), Mobile — and the tabs move together across the whole page, so picking your frontend once at the top carries through to the end. Where a frontend genuinely can’t do the task, its tab says so plainly and points at what it does instead.
See also
- Frontends — all five, and how to choose between them
- Widgets — the reference for everything a window can hold
- Customization — layouts, highlights, keybinds, themes, skins
- Command Reference — every dot-command in one table