# SpartanUI

## [be05c2f](https://github.com/Wutname1/SpartanUI/tree/be05c2f979262d19a65df703538c5770d4c9ec3f) (2025-10-21)
[Full Changelog](https://github.com/Wutname1/SpartanUI/commits/be05c2f979262d19a65df703538c5770d4c9ec3f) [Previous Releases](https://github.com/Wutname1/SpartanUI/releases)

- UnitFrames: Fix raid frames 13+ not initialized (proper fix)  
    PROBLEM:  
    Raid frame buttons 13+ were created but not initialized with UI elements.  
    ROOT CAUSE:  
    The raid header was configured with startingIndex=-10, which only created 10 frames initially. When the raid grew beyond 12 members, the secure header system dynamically created additional buttons (13+), but these bypassed oUF's initialization process since they were created after the initial SpawnHeader call.  
    SOLUTION:  
    Changed startingIndex from -10 to -40 in raid.lua GroupBuilder. This forces the secure header to create all 40 possible raid frames upfront during addon initialization. All frames now go through the proper oUF initialization pipeline (initialConfigFunction -> walkObject -> initObject -> CreateUnitFrame), ensuring complete styling.  
    CHANGES:  
    - raid.lua: Changed startingIndex from -10 to -40 to create all frames upfront  
    - SpawnFrames.lua: Simplified uninitialized button handling (now just logs if it occurs)  
    This is the proper fix - by creating all frames initially rather than dynamically, we ensure consistent initialization for all raid members.  
