Buff status colour #1425


Closed
  • Kreynz created this issue Feb 15, 2026

    What version of Grid2  are you using (Version is displayed in General/About Tab) ?

    3.0.24 and 3.0.29-beta

     

    What game client version, classic or retail, windows or mac and language are you using ?

    Retail

     

    What steps will reproduce the problem?

    Changing the version of grid2

      
    Did you try having Grid2 as the only enabled addon and everything else disabled?

    No

      

    Was it working in a previous version? If yes, which was the last good one?

    Yes

      

    Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (`/console scriptErrors 1`) or install [BugSack](https://mods.curse.com/addons/wow/BugSack).

      

    Please provide any additional information below.

     

    In version 3.0.24, it is possible to colour the frames using a buff status using "Buffs from Blizzard Unit Frames". This will set the colour of the raid frames if any trackable buff exists.

     

    In version 3.0.29-beta, this same method no longer works, instead the frames will take on the buff status colour even when no trackable buff exists. 

     

     

     

     

  • Kreynz edited description Feb 15, 2026
  • michaelsp posted a comment Feb 15, 2026

    Working fine here, there are no relevant changes  about the buffs coloring between 3.0.24 and 3.0.29 versions.

  • Kreynz posted a comment Feb 15, 2026

    What do you think is causing it on my end then? I am doing nothing except changing the version of grid, and on 3.0.29 it does not work, while it works on 3.0.24?

     

    Version 3.0.29, colouring with no trackable buffs active.

     

     

    On 3.0.24 in the exact same scenario, it is working correctly.

     

     

    With this buffs status, as a colour status for the health-multibar. 

     

     

    This is my profile I am using - https://wago.io/mr4WRg6Dw

  • michaelsp posted a comment Feb 15, 2026

    Found the issue, it will be fixed in next beta.

  • Kreynz closed issue Feb 15, 2026
  • Kreynz posted a comment Feb 15, 2026

    Thanks! 

  • michaelsp posted a comment Feb 16, 2026

    This issue should be fixed in version 3.0.30-beta


To post a comment, please login or register a new account.