Category:EventMacro Conditions State: Difference between revisions

From OpenKore Wiki
Jump to navigation Jump to search
(Created page with "=== Conditions === {{Template:Eam_Conditions}} ===== State ===== {{Template:Eam_Conditions_State}} Category:EventMacro_Automacros")
 
No edit summary
 
Line 1: Line 1:
=== Conditions ===
{{Template:Eam_Automacros}}
{{Template:Eam_Conditions}}
{{Template:Eam_Conditions}}
===== State =====
{{Template:Eam_Conditions_State}}
{{Template:Eam_Conditions_State}}


[[Category:EventMacro_Automacros]]
[[Category:EventMacro_Automacros]]

Latest revision as of 22:18, 3 July 2019

Automacros

At this point, you can define macros and call them, typing 'eventMacro <macro name>' in OpenKore's console input.

Automacro is an automatic trigger for calling your macros, just like blocks in config.txt are automatic triggers for certain AI actions.

Automacro block consists of:

Automacro does not trigger if there is currently running macro in exclusive mode. Otherwise, automacro clears macro queue (which means that all currently running macros are stopped) before call.

The point of automacro is that you use them to check for certain conditions and call your macro when all conditions are fulfilled.

All possible conditions are listed on the category page.

Conditions

  • Conditions are separated into 2 categories: state and event.
  • Most conditions set special variables when the automacro activates.
  • Most conditions accept variables in their code.
  • Each automacro can only have one event condition.
  • Most state conditions can be used more than once in each automacro.
  • Each condition will have it's detailed explanation below.
  • eventMacro has a modular condition system, each file inside eventMacro/Condition is a condition.
State
  • State conditions have a defined status of true or false.
  • An automacro will only activate when all of it's state conditions are true.