How hekili/hekili works
Main Components
a. Core System Components:
• Core Engine (Core.lua, State.lua)
• Event Handler (Events.lua)
• Class Management (Classes.lua)
• Target System (Targets.lua)
b. Specialization Components:
• Class-specific Modules (TheWarWithin directory)
• Priority Lists (TheWarWithin/Priorities/*.simc files)
c. User Interface Layer:
• Main UI (UI.lua)
• Options Panel (Options.lua)
• Popup Components (UI/PopupSlider)
d. Game Version-Specific Modules:
• Dragonflight
• Shadowlands
• BfA
• Legion
• Wrath
• TheBurningCrusade
[User Interface Layer]
• ↕
[Core Engine Layer]
• ↕
[Specialization Layer]
• ↕
[Game Systems Integration]
Component Relationships
• Core Engine ←→ Event Handler (bidirectional)
• Core Engine → State Management
• Event Handler → Class Management
• Core Engine → Priority System
• UI Layer → Core Engine
• Specialization Modules → Priority Lists
Detailed Component Breakdown
Core Engine:
[Core Engine]
• State Management
• Event Processing
• Priority Calculation
• Action Recommendation
Specialization System:
[Spec System]
• Class Modules
• Priority Lists
• Rotation Logic
Integration Points
Clear integration points with:
• WoW API
• SpellFlashCore Library
• Configuration System
• The modular nature of the addon
• Clear separation between core functionality and spec-specific logic
• The event-driven architecture
• The priority calculation pipeline
Remember to:
• Keep the main flow clear and easy to follow
• Related components together
• Clear data flow directions
• Version-specific boundaries