Complete Priority Hierarchy
When multiple sources attempt to set a player's view or simulation distance, the following priority order determines the outcome. A higher P number always wins.
| Priority | Source | Example |
|---|---|---|
| P8 (highest) | Admin manual command | /auroraoptimizer viewdist set player Steve 10 |
| P7 | Immunity permission | auroraoptimizer.immune |
| P6 | Distance cap permission | auroraoptimizer.viewdistance.max.12 |
| P5 | WorldGuard region flag | aurora-exempt or aurora-aggressive on the region |
| P4 | World-level override | config.yml heuristics.worlds.<world> |
| P3 | Player-level override | config.yml heuristics.players.<uuid> |
| P2 | Active optimization profile | /auroraoptimizer profile set aggressive |
| P1 (lowest) | Base heuristic rules | config.yml heuristics.triggers.* |
Conflict Resolution Examples
/auroraoptimizer viewdist set player Steve 10— Steve receives VD=10. This P8 override prevails over everything, including caps, profiles and regions.- Steve holds
.immune— no automatic optimization is applied to him at all, regardless of server state. (P7) - Steve has
.viewdistance.max.12and a policy requests VD=6 — Steve receives VD=6. The cap is not exceeded, P6 does not intervene. - Steve has
.viewdistance.max.8and a policy requests VD=10 — Steve receives VD=8. The request is clamped to the cap. (P6 beats P2) - Steve is inside a region with flag
aurora-exempt— no optimizations are applied in that region. (P5)