Class Order - Revision history

Exspes at 22:13, 28 August 2021

2021-08-28T22:13:47Z

← Older revision		Revision as of 22:13, 28 August 2021
Line 131:		Line 131:

	Not all class list options apply to all classes. As usual, some common sense is needed. If you have a tank with cc in its /class list orders, there is nothing we can do for you here.		Not all class list options apply to all classes. As usual, some common sense is needed. If you have a tank with cc in its /class list orders, there is nothing we can do for you here.

			= editing =
			class orders are edited like any list in Entropy.

			<code>/edit lsOrderClassBase xtarget add</code>

			would add xtarget building and checking to the out of combat portion of the character.

Exspes at 22:10, 28 August 2021

2021-08-28T22:10:13Z

← Older revision		Revision as of 22:10, 28 August 2021
Line 36:		Line 36:
	Once the Main Order has been completed, this will be executed 1 time before releasing the class code back to the main macro loop.		Once the Main Order has been completed, this will be executed 1 time before releasing the class code back to the main macro loop.

	~~<nowiki>~~= options =~~</nowiki>~~		= options =
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 127:		Line 127:
	\|cycle any modes that are enabled		\|cycle any modes that are enabled
	\|}		\|}
	~~<nowiki>~~= notes =~~</nowiki>~~
			= notes =

	Not all class list options apply to all classes. As usual, some common sense is needed. If you have a tank with cc in its /class list orders, there is nothing we can do for you here.		Not all class list options apply to all classes. As usual, some common sense is needed. If you have a tank with cc in its /class list orders, there is nothing we can do for you here.

Exspes at 22:09, 28 August 2021

2021-08-28T22:09:32Z

← Older revision		Revision as of 22:09, 28 August 2021
Line 36:		Line 36:
	Once the Main Order has been completed, this will be executed 1 time before releasing the class code back to the main macro loop.		Once the Main Order has been completed, this will be executed 1 time before releasing the class code back to the main macro loop.

			<nowiki>= options =</nowiki>
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 127:		Line 127:
	\|cycle any modes that are enabled		\|cycle any modes that are enabled
	\|}		\|}
			<nowiki>= notes =</nowiki>

			Not all class list options apply to all classes. As usual, some common sense is needed. If you have a tank with cc in its /class list orders, there is nothing we can do for you here.

Exspes at 22:06, 28 August 2021

2021-08-28T22:06:01Z

← Older revision		Revision as of 22:06, 28 August 2021
Line 45:		Line 45:
	\|melee		\|melee
	\|		\|
	\|		\|/melee
	\|-		\|-
	\|heal		\|heal
	\|		\|
	\|		\|/heal
	\|-		\|-
	\|burn		\|burn
	\|		\|
	\|		\|class burn() routine
	\|-		\|-
	\|misc		\|misc
	\|		\|
	\|		\|class misc_combet() routine
	\|-		\|-
	\|dot		\|dot
	\|		\|
	\|		\|/dot
	\|-		\|-
	\|nuke		\|nuke
	\|		\|
	\|		\|/nuke
	\|-		\|-
	\|debuff		\|debuff
	\|		\|
	\|		\|/debuff
	\|-		\|-
	\|item		\|item
	\|		\|
	\|		\|/clickitem
	\|-		\|-
	\|pet		\|pet
	\|		\|
	\|		\|sends pets in and swarm for active combat
	\|-		\|-
	\|swarm		\|swarm
	\|		\|
	\|		\|class specific swarm pets like bst and mage
	\|-		\|-
	\|manarecover		\|manarecover
	\|		\|
	\|		\|shared mana_recover() routine
	\|-		\|-
	\|alliance		\|alliance
	\|		\|
	\|		\|borked atm
	\|-		\|-
	\|staminarecover		\|staminarecover
	\|		\|
	\|		\|shared stamina_recover() routine
	\|-		\|-
	\|checkminion		\|checkminion
	\|		\|
	\|		\|pet class pet checker thingie
	\|-		\|-
	\|xtarget		\|xtarget
	\|		\|
	\|		\|sorts/builds xtargets
	\|-		\|-
	\|taunt		\|taunt
	\|		\|
	\|		\|taunt stuff
	\|-		\|-
	\|agro		\|agro
	\|		\|
	\|		\|agro routines
	\|-		\|-
	\|harmonious		\|harmonious
	\|		\|
	\|		\|knight harmonious routine
	\|-		\|-
	\|cc		\|cc
	\|		\|
	\|		\|mez routine
	\|-		\|-
	\|gather		\|gather
	\|		\|
	\|		\|aa mana gather routine
	\|-		\|-
	\|mode		\|mode
	\|		\|
	\|		\|cycle any modes that are enabled
	\|}		\|}

Exspes at 21:59, 28 August 2021

2021-08-28T21:59:54Z

@@ Line 39: / Line 39: @@
 {| class="wikitable"
 |+
-!2
+!Order Name
+!
 |-
+|
+|
+|
+|
 |-
+|
+|
+|
+|
 |-
+|
+|
+|
+|
 |}

Exspes at 21:53, 28 August 2021

2021-08-28T21:53:55Z

← Older revision		Revision as of 21:53, 28 August 2021
Line 35:		Line 35:
	== Post Order ==		== 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.		Once the Main Order has been completed, this will be executed 1 time before releasing the class code back to the main macro loop.


			{\| class="wikitable"
			\|+
			!2
			!
			!
			!
			\|-
			\|
			\|
			\|
			\|
			\|-
			\|
			\|
			\|
			\|
			\|-
			\|
			\|
			\|
			\|
			\|}

Exspes at 21:46, 28 August 2021

2021-08-28T21:46:03Z

← Older revision		Revision as of 21:46, 28 August 2021
Line 19:		Line 19:
	\|lsOrderClass		\|lsOrderClass
	\|-		\|-
	\|Post ~~Ooder~~		\|Post Order
	\|		\|
	\|lsOrderClassPost		\|lsOrderClassPost

Exspes at 21:45, 28 August 2021

2021-08-28T21:45:05Z

← Older revision		Revision as of 21:45, 28 August 2021
Line 1:		Line 1:

			Class orders determine what each class will do when the macro main loop releases to the class. Each class can go through 4 stages depending on how you have it set up for in and out of combat and what /cc modes you have set for it.
	~~All classes operate in~~ 4 stages:
	= Class Orders =		= Class Orders =
	{\| class="wikitable"		{\| class="wikitable"
Line 7:		Line 6:
	!		!
	!List Variable		!List Variable
	!
	\|-		\|-
	\|Base Order		\|Base Order
	\|		\|
	\|lsOrderClassBase		\|lsOrderClassBase
	\|
	\|-		\|-
	\|Pre Order		\|Pre Order
	\|		\|
	\|lsOrderClassPre		\|lsOrderClassPre
	\|
	\|-		\|-
	\|Main Order		\|Main Order
	\|		\|
	\|lsOrderClass		\|lsOrderClass
	\|
	\|-		\|-
	\|Post Ooder		\|Post Ooder
	\|		\|
	\|lsOrderClassPost		\|lsOrderClassPost
	\|
	\|}		\|}


	== Base Order ==		== Base Order ==
	Base Order will be checked at the start of every class call. It is checked inside and outside of combat.		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.		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 ==
	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 %		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 %

Exspes at 21:43, 28 August 2021

2021-08-28T21:43:22Z

@@ Line 3: / Line 3: @@
 All classes operate in 4 stages:
 = Class Orders =
-- Base Order::lsOrderClassBase
+{| class="wikitable"
-- Pre Order::lsOrderClassPre
+!Order
-- Main Order::lsOrderClass
-- Post Order::lsOrderClassPost
+!List Variable

Exspes at 21:39, 28 August 2021

2021-08-28T21:39:48Z

← Older revision		Revision as of 21:39, 28 August 2021
Line 3:		Line 3:
	All classes operate in 4 stages:		All classes operate in 4 stages:
	= Class Orders =		= Class Orders =
	Base Order::lsOrderClassBase		- Base Order::lsOrderClassBase
	Pre Order::lsOrderClassPre		- Pre Order::lsOrderClassPre
	Main Order::lsOrderClass		- Main Order::lsOrderClass
	Post Order::lsOrderClassPost		- Post Order::lsOrderClassPost