BABUNI.DEV

ROAR / Design

ROAR: Design

ROARR — interaction and presentation design

The little surprise

ROARR is designed around a player action rather than a scheduled spectacle. A familiar combat button can suddenly be accompanied by a roar, flex, cheer or playfully bored response. This lets the player retain direct control of combat while the character acquires an occasional independent-looking expressive moment.

The response uses WoW built-in emotes. No custom avatar animation, dedicated audio asset, widget, or complex command window is shipped.

Frequency and probability

Two controls change the cadence:

A failed chance roll still consumes the cooldown in source. This means chance 40; cd 12 is not “a 40% roll on every press”: a failed attempt delays the next eligible roll by twelve seconds. Whether that is the desired game feel is left open to the creator.

An on/off switch lets the player silence reactions without losing slot or chance preferences. The watch switch prints slot IDs and is meant as a temporary configuration aid, not a permanent player overlay.

Output vocabulary and social tone

Token Expressive role
ROAR Battle excitement and loud assertion
CHARGE Momentum and aggressive enthusiasm
CHEER Celebration and encouragement
BORED Comic contrast with the fight
FLEX Pride and swagger

The variety is small but effective: even BORED contributes personality by interrupting battle intensity with an incongruous emotion. Which of the five tokens is chosen is random and unweighted.

User journey

Enter /roarr watch, discover the slot, set it, optionally adjust chance and cooldown, turn off watch mode and play normally. /roarr tutorial offers a short reminder; /roarr info reports the live configuration. All feedback appears in the chat frame, prefixed ROARR:.

Accessibility and client-specific unknowns

Text setup can be challenging if slot numbering changes between bar layouts; the discovery switch helps. Test whether the five emotes make sense in the player's client/locale and whether spam prevention and UI messages remain comfortable. There is no evidence of accessibility testing or broad client validation in the repository.

Naming

The outer GitHub repository is roar; the final addon is ROARR. Display and usage text should prioritize the installed /roarr command while the history explains why the two names coexist.

Document information

Creative author: Babuni.dev

View source