w/wowunlockers
Menu

Public rotation framework and profiles

BadRotationsOfficial source verified

BR

#9Rotation ranking

BadRotations offers free combat routines with public code and class-by-class status, though many profiles target older patches and all need a separate Lua unlocker.

Public sourceUnlocker requiredProfile-specific support

Listed price

Free; unlocker separate

View repository

Compatible unlocker and maintained profile required

Public source codeWhat the check mark meansEdited by M1Sources checked Why this rank

Overview

BadRotations is a free Lua rotation project maintained by CuteOne and community contributors, with an object manager, ground-spell support, a healing engine, profile-specific controls and a debug interface. It needs a separate Lua unlocker to run. [1][8]

More about this product

The README describes BadRotations as a developer playground and lists each routine's author, target patch, coverage, maintenance and raid readiness. Those entries help you judge the available profiles, many of which target old patches or carry limited, development or unknown status. [1]

CuteOne declined to build a dedicated unlocker in a 2017 issue, leaving BadRotations to supply the framework and profiles while a separate unlocker provides game access and any protection it claims. [8]

Before you buy

  • Many profiles target old patches or are marked partial, in development or of unknown readiness.
  • The README can receive an automatic date refresh even when nobody has changed the combat code.
  • The project makes no claim to cover every current spec, and we have not independently tested its security.

Pricing and access

BadRotations framework and public profiles

FreeNo paid subscription stated

Public framework and community profiles

Required: Separate supported Lua unlocker

More on BadRotations framework and public profiles

A compatible unlocker adds a separate expense, and the free project offers no paid-support response guarantee.

[1]

The framework and public profiles are free, with a compatible unlocker needed separately. The README asks for permission before taking or selling its code.

Classes, scripts and modules

Scroll sideways to see all columns.

NameCoverageDetails
Druid / Feral - CuteOneRotation profilesDruid 1.12 and 2.5.5; Feral 5.4.8 and 12.0.0Free
Details: Druid / Feral - CuteOne

The May 26, 2026 matrix lists full maintenance and 100% author-rated coverage, but leaves readiness unknown.

[1]
Hunter, Demon Hunter, Evoker, Monk, Paladin, Rogue, Shaman, Warlock, Warrior and DK entriesMixed community profilesPatch targets and maintenance differ by profileFree
Details: Hunter, Demon Hunter, Evoker, Monk, Paladin, Rogue, Shaman, Warlock, Warrior and DK entries

Affliction and Demonology are in development at 50%, Fury leveling is at 20%, and Enhancement is marked unsuitable for raids. The Mage and Priest headings do not establish that finished profiles exist.

[1]

Requirements

Scroll sideways to see all columns.

Game branchSystem / regionCoverage and limits
Retail profiles with mixed patch targetsProfile-specificWindows via Daemonic or NN; macOS via Tinkr, as listed in wikiNo complete regional matrixFeral targets patch 12.0.0, while many other profiles still list 10.x or 11.x. Daemonic advertises Retail support, but your chosen profile also needs to match the client. [1][2][4]
Classic, TBC and MoP-oriented profilesProfile-specificDepends on unlocker supportNot specifiedThe listed targets are 1.12 and 2.5.5 for Druid, 2.5.1 for Hunter, and 5.4.8 for Feral and Subtlety, which do not by themselves establish support for current official servers. [1]

Community and support

CuteOne maintains the public repository, with GitHub issues and the linked Discord listed as the places to report problems.

BadRotations GitHubGitHub / Public source, issues and pull requestsBadRotations DiscordDiscord / The invite is public, but we did not attempt to join.BadRotations wikiDocumentation / Public
Support details

The README welcomes contributors and beta testers and asks for Lua errors through GitHub or Discord, while warning that the old Slack channel is checked infrequently. [1]

The project asks for permission before taking or selling its code, so the public repository should not be read as a grant of unrestricted commercial reuse. [1]

Features and plugins (2)
  • Object manager, healing engine and ground-spell support [source]
  • Profile controls, debug interface and public class-profile status matrix [source]

These details come from the linked published sources; we have not tested the software ourselves.

Privacy and security

Public source makes BadRotations available for inspection, but we have not independently tested its performance or security. Its historical ban reports do not establish a current detection.

Update record

The commit history records code maintenance without measured recovery times after game patches. Regenerating the README can also give it a new timestamp without changing every profile. [3][1]

Update log and evidence (3)

The newest commit, fc5b82408444d44d6e496b037d004a2ed261dcc9, regenerated the README on May 26, 2026 at 22:12:02 UTC, immediately after code change 74dd3e6b9b6a72dfa66ae4d8578fb80470a89167 at 22:11:57 UTC.

  1. 2026-05-26
    Code commit 74dd3e6b9b6a72dfa66ae4d8578fb80470a89167 covers API, UI and Feral work, initial specialization resolution, expansion flags and TBC Hunter UI handling.[3]
  2. 2026-05-26
    Commit fc5b82408444d44d6e496b037d004a2ed261dcc9 refreshes the generated README and profile matrix.[3]
  3. 2026-04-21
    The update adds API documentation annotations and CI handling for empty Lua-check results.[3]
  • The project has no fixed maintenance schedule or record pairing outages with verified recovery times.
  • Profile coverage percentages come from the authors' own ratings, without independent testing.

Ban reports and history

A contributor associated July 2020 bans with automatic interrupts, and an outside provider later included BadRotations in a claim about September 2020 public-addon bans. Neither report establishes a current detection.

About these reports

The evidence comes from an original GitHub discussion and a dated statement by another provider, neither of which supplies a complete affected-account list or demonstrates the detection method.

What do the cause labels mean?
2020-07-08Contributor-reported bans

Contributor reports five bans among BR auto-interrupt users

Moderate for the report; cause unproven

Contributor cxmplex opened pull request 938 after reporting five bans on the EWT forums that all involved automatic interrupts. [5][6]

Full report, cause and response

Affected scope: BadRotations users discussed on EWT forums

  • The pull request invited discussion of a proposed change to interrupt behavior.
  • It closed without being merged, and the record does not establish that the proposed change fixed the reported problem.
  • The issue did not reproduce the original EWT account reports.
Cause: Behavior/server-side signalsExplain the labels

The contributor suspected repeated combat behavior, but the proposed change neither establishes Blizzard's detection method nor rules out another part of the setup.

Suspected by contributor, not demonstrated [5][6]
Provider response
A contributor proposed changing interrupts, but we found no maintainer conclusion establishing what caused the bans.
Date precision
Report date unless stated otherwise

Sources [5][6]

2020-09Retrospective provider claim

External provider attributes bans to public add-ons

Moderate for attribution; technical details absent

UnitedSolutions said on December 25, 2020 that a September wave had affected platforms using public add-ons, naming BadRotations among them. [7]

Full report, cause and response

Affected scope: Public add-on ecosystem, including BadRotations by name

  • The statement treats this as separate from UCS's claimed targeted wave in January 2019.
  • No exact September date, affected-account count, hash, leak or technical proof accompanies the claim.
  • The claim comes from another platform's representative, with no acknowledgment by BadRotations' maintainers in the reviewed record.
Cause: UnknownExplain the labels

Naming public add-ons does not establish whether Blizzard identified a file, code signature, API pattern or server-side behavior.

Unknown [7]
Provider response
We found no direct response from BadRotations' maintainers.
Date precision
Month; retrospectively reported

Sources [7]

Comments and ratings

If you have used BadRotations, this is the place to share how it went. The ratings here come from readers and are separate from the editorial ranking.

Loading ratings...
Log in to comment

You can join without an email address; we generate a nickname and a Login Key for you to keep.

Latest comments

References

  1. [1] BadRotations README and profile matrixCuteOne and contributors / Public source / Checked: 2026-09-12
  2. [2] Getting BadRotations to workBadRotations maintainers / Provider documentation / Published: 2025-01-11 / Checked: 2026-09-12
  3. [3] BadRotations exact commit historyCuteOne / GitHub / Commit metadata / Checked: 2026-09-12
  4. [4] Daemonic supported add-onsDaemonic / Platform documentation / Published: 2026-09-03 / Checked: 2026-09-12
  5. [5] Contributor reports five bans and proposes interrupt changescxmplex / BadRotations / Original contributor report / Published: 2020-07-08 / Checked: 2026-09-12
  6. [6] Discussion of proposed interrupt changescxmplex / BadRotations / Original contributor comment / Published: 2020-07-08 / Checked: 2026-09-12
  7. [7] UCS representative discusses September 2020 public-addon bansUnitedSolutions / elitepvpers / External platform-provider statement / Published: 2020-12-25 / Checked: 2026-09-12
  8. [8] CuteOne declines to build an unlockerCuteOne / GitHub / Maintainer statement / Published: 2017-02-12 / Checked: 2026-09-12
Back to the directory