Class Order: Difference between revisions

From Entropy
No edit summary
No edit summary
Line 3: Line 3:
All classes operate in 4 stages:
All classes operate in 4 stages:
= Class Orders =
= Class Orders =
- Base Order::lsOrderClassBase
{| class="wikitable"
- Pre Order::lsOrderClassPre
!Order
- Main Order::lsOrderClass
!
- Post Order::lsOrderClassPost   
!List Variable
!
|-
|Base Order
|
|lsOrderClassBase
|
|-
|Pre Order
|
|lsOrderClassPre
|
|-
|Main Order
|
|lsOrderClass
|
|-
|Post Ooder
|
|lsOrderClassPost
|
|}  





Revision as of 21:43, 28 August 2021


All classes operate in 4 stages:

Class Orders

Order List Variable
Base Order lsOrderClassBase
Pre Order lsOrderClassPre
Main Order lsOrderClass
Post Ooder lsOrderClassPost


Base Order

Base Order will be checked at the start of every class call. It is checked inside and outside of combat. Its purpose is specific to each class. Some classes check xtarget settings, some check if their pets are still fit for combat, Some check ammunition, and so on. Things that classes need that you don't want to waste time on while in active combat.


Pre Order

Pre order is checked at the onset of an engage, not to the point to /cc engage %, even if the mob is 100%, this is the first part checked. This list order will get continually checked until the mob reaches your engage %

Main Order

Main Order is the actual combat routine. Once an engage has reached your engage point, this loop will be maintained until the mob is dead or you force a stop, or the assist changes target.

Post Order

Once the Main Order has been completed, this will be executed 1 time before releasing the class code back to the main macro loop.