BABUNI.DEV

ROARRunlimited / Concept

ROARRunlimited: Concept

ROARRunlimited — concept and creative direction

When one roar is not enough

Earlier ROAR/ROARR addons let the player pick one action-bar button to occasionally trigger a built-in emote. ROARRunlimited expands that idea from one watched action into a configurable collection of independent expressive triggers. A different button can have a different personality rhythm: frequent enthusiasm on one action, rarer celebration on another.

The source implements this through numbered configurations (“instances”), each pairing a WoW action slot with a probability and a cooldown. The numbering is a convenient reference in slash commands, not a cap of one or two predefined buttons. The player retains control of every actual action.

The original repository description says ROARRunlimited “plays battle-themed emotes from multiple watched action slots.” Its README finishes with the creator's metaphor of turning the action bar into a war drum. This supports the artistic goal without requiring us to invent an original design dialogue.

Experience principles embodied in code

A meaningful evolution across the committed code

The first December 2025 source indexed entries directly by watched action-slot ID. A subsequent revision indexed entries by instance number, allowing slot assignments to be changed while chance/cooldown values remain associated with a named configuration. In January 2026 a further source revision normalized old saved entries and reduced the pool to four native emotes, removing BORED. These changes are supported by actual diffs; they are not proof of a recorded author vote, a specific design disagreement, or a tested release process.

What still needs author input

The code allows more than one instance to watch the same physical action slot, potentially producing multiple emotes on one press. Whether this is creative flexibility or an edge case to prevent is for Babuni.dev to decide. The current documentation does not implicitly approve restricting it.

This repo should be preserved as a distinct step in the broader ROAR addon family, but direct migration or inheritance beyond demonstrated similarities requires evidence.

Document information

Creator: Babuni.dev

View source