This project is abandoned and its default file will likely not work with the most recent version of World of Warcraft. Whether this project is out of date or its author has marked it as abandoned, this project is no longer maintained.
A highly configurable in-game layout creation tool for Grid.
Main Features:
Group filters which allow you to create groups by Role (Tank, Melee, Healer, Ranged), Raid Group, Name Lists, Out of Zone and/or Offline, and Guild, as well as a catch-all filter (Everyone). You can allow repetitions, or have players appear only in the first group for which they match the filter.
Sorting within groups by Name, Raid Index, Class, or Role. You can also choose to have yourself appear at the beginning or your group, or even to manually specify names that you wish to appear first if present.
Pet group class filters that allow you to see pets only for the classes you want.
Colored group borders that tell you what type of group you are looking at (the colors can be customized).
Layouts you create are saved and can be assigned within the GridLayout options to be the default for whichever party type you want (e.g. solo, group, raid10, raid25).
Roles are determined using both player talent spec and also Blizzard role information. You may choose to give priority to Blizzard information, in which case talents are only used to disambiguate for classes that have both a melee and a ranged damage spec (i.e. shamans and druids).
Quickly change layouts by left clicking the Grid icon on the minimap. This feature is off by default. A checkbox to turn on this option appears in the Grid configuration UI, next to the option to enable the minimap icon.
Limitations:
When using role filters, a default role based on class will be assigned until the module can inspect the unit or Blizzard role data becomes available.
Zone information is not available in 5-man parties, so the out-of-zone filter will not be used.
The flexibility comes at a cost: group composition cannot be updated in combat. Generally speaking, all that this means is that you may not want to use this module in Battlegrounds, where raid composition could change in combat and you could have brief periods where you are missing newly added players. In PvE you would have to try really hard to make this an issue.
I ended up writing my own Grid layout plugin that narrowly does the one thing that I used GCL for, which was to group by role. The plugin is GridLayoutByRole.
I'm using a layout with several groups (1 group = 1 raid group =1 line). How can I change the space between these groups, I want them stuck together as much as possible.
Every time I join a LFR the layout doesn't apply correctly so I have to switch away from GCL Group 25 to something else and back again. Then it works perfectly. But it is kinda annoying since tanks often manage to pull before I switch layout and bakc.
I notice very often that this addon does not correctly identify which spec/role people have in a raid. I keep 3 groups - "Blizzard Tanks", "Healers", and "Everyone", and it seems like if I join into an existing raid the "Healers" group is empty. This makes me wonder if there should be a "Blizzard Healers" group, since "Blizzard Tanks" tends to work better for me?
I may take a browse through the code and see how difficult it would be to add this.
So, I haven't ever seen this addon mis-identify a spec. What it sounds like is that the addon is not receiving inspect data at all, at least some of the time. Classes have a default spec until the real one can be determined, and that is always a dps spec. So if your healers are showing up as dps, it almost surely means the addon is not receiving inspect data for them.
The most useful information to track down the problem would be to know what other addons you are running, since there are a few addons that intentionally interfere with inspects.
If you can tell me, also, when players are in the wrong roles, does it happen when you enter a raid while in combat, or are you in another zone when it happens? Does it stay that way, or does it eventually correct itself?
Last off, there are a couple of relevent options already in the addon that should almost entirely correct what you are seeing, although I hope you will still track down the core problem. There is an option to use or not use Blizzard role data. If this is checked, then, if inspect data is missing, but healers are set in the right Blizzard role, they should appear as healers. The situation with tanks is a little more complicated, and I won't go into it unless you ask me to.
In fact, if you have the option set to use blizzard role data, and blizzard roles are set correctly, the only characters that will still sometimes be in the wrong role are those that have both a ranged and a melee spec, i.e. druids and shamans. But I wouldn't recommend ignoring that remaining issue. Knowing who is ranged and who is melee is obviously really often very important.
There is also an option to give preference to the blizzard role setting. I personally would never use this. This addon is how I know what spec players are REALLY in. If my tank is still in his dps or healing spec, or my healer is still specced boomkin, it's evident on my screen, and I can say something when even they may not have realized. I can't tell you how many disasters have been averted that way.
Could someone help me with an issue with this addon please?
I have Grid configured to automatically switch my profiles when I change my current spec. And every time after I respec, except the first one in a game session, I would get this error message:
Message: Interface\AddOns\Grid\GridFrame.lua:605: attempt to perform arithmetic on local 'g' (a nil value) Time: 06/22/14 17:40:09 Count: 4 Stack: (tail call): ? Interface\AddOns\Grid\GridFrame.lua:605: in function `SetBarColor' Interface\AddOns\Grid\GridFrame.lua:810: in function `SetIndicator' Interface\AddOns\Grid\GridFrame.lua:1619: in function `UpdateIndicator' Interface\AddOns\Grid\GridFrame.lua:1592: in function `UpdateIndicators' Interface\AddOns\Grid\GridFrame.lua:1542: in function `UpdateAllFrames' Interface\AddOns\Grid\GridFrame.lua:1504: in function `PostReset' Interface\AddOns\Grid\GridCore.lua:244: in function `Reset' Interface\AddOns\Grid\GridCore.lua:620: in function `ResetModules' Interface\AddOns\Grid\GridCore.lua:462: in function `?' ...ibDataBroker\CallbackHandler\CallbackHandler-1.0.lua:147: in function <...ibDataBroker\CallbackHandler\CallbackHandler-1.0.lua:147> [string "safecall Dispatcher[3]"]:4: in function <[string "safecall Dispatcher[3]"]:4> [C]: ? [string "safecall Dispatcher[3]"]:13: in function `?' ...ibDataBroker\CallbackHandler\CallbackHandler-1.0.lua:92: in function `Fire' ...\AddOns\Broker_Currency\libs\AceDB-3.0\AceDB-3.0.lua:462: in function `SetProfile' ...AddOns\Grid\Libs\LibDualSpec-1.0\LibDualSpec-1.0.lua:193: in function `CheckDualSpecState' ...AddOns\Grid\Libs\LibDualSpec-1.0\LibDualSpec-1.0.lua:351: in function <...AddOns\Grid\Libs\LibDualSpec-1.0\LibDualSpec-1.0.lua:336>
This only happens when GCL is turned on.
I LOVE this addon, btw. Even need to manually /reload UI on every respec wouldn't make me stop me using it :)
As you can see there are some missing ["g"] values. Apparently Grid don't save color components if they are equal to 1. So I've just added this line to every ["color'] record: ["g"] = 0.9999
But it is still weird how Grid works well with this issue, and stops working once I turn GCL on :-/
Are you working on fixing this up for the new version of Grid's Flex mode? (Doesn't work at all at the moment)
Edit: When loading in Flex with the new grid version, it puts everyone in the tank group regardless of settings (as far as I found). Not sure if there was an error message or not.
I don't know what I'm doing wrong but I cant seem to find out. I'm trying to make it for a 25 Man where the far left i ahve the 2 tanks in there own group then healers in the next 2 groups then dps the rest but it doesnt seem to work like that in the group filter. Can you help me out at all?
Yes. Each filter captures ALL raid members of that type. What you want is to define the column / row size to 5 if it isn't already at 5. If you have 6 or more healers, it will look like two groups of healers, if you have less, then it will look like one group. So set the filter to g1 = tanks, g2 = healers, g3 = damagers. You can also set g3 = group1, g4 = group2, etc, and you will have the dps organized by group, but the tanks and healers will not be included because they were captured in the first two groups.
If you're using GridConfigurableLayouts solely for the group-by-role layout, you can try GridLayoutByRole.
can you update it for 6.0.2 ? pleas
I ended up writing my own Grid layout plugin that narrowly does the one thing that I used GCL for, which was to group by role. The plugin is GridLayoutByRole.
@jlam
Can you share your fixed version, please?
I have this fixed for WoD in my local checkout of the repository. I switched over to using LibGroupInSpecT for the role queries.
Hi,
I'm using your addon but if i update grid to 6.0.2 version i cant use yours. Are you going to update it ?
Hi,
I'm using a layout with several groups (1 group = 1 raid group =1 line). How can I change the space between these groups, I want them stuck together as much as possible.
Thanks
Every time I join a LFR the layout doesn't apply correctly so I have to switch away from GCL Group 25 to something else and back again. Then it works perfectly. But it is kinda annoying since tanks often manage to pull before I switch layout and bakc.
I notice very often that this addon does not correctly identify which spec/role people have in a raid. I keep 3 groups - "Blizzard Tanks", "Healers", and "Everyone", and it seems like if I join into an existing raid the "Healers" group is empty. This makes me wonder if there should be a "Blizzard Healers" group, since "Blizzard Tanks" tends to work better for me?
I may take a browse through the code and see how difficult it would be to add this.
Hiya.
So, I haven't ever seen this addon mis-identify a spec. What it sounds like is that the addon is not receiving inspect data at all, at least some of the time. Classes have a default spec until the real one can be determined, and that is always a dps spec. So if your healers are showing up as dps, it almost surely means the addon is not receiving inspect data for them.
The most useful information to track down the problem would be to know what other addons you are running, since there are a few addons that intentionally interfere with inspects.
If you can tell me, also, when players are in the wrong roles, does it happen when you enter a raid while in combat, or are you in another zone when it happens? Does it stay that way, or does it eventually correct itself?
Last off, there are a couple of relevent options already in the addon that should almost entirely correct what you are seeing, although I hope you will still track down the core problem. There is an option to use or not use Blizzard role data. If this is checked, then, if inspect data is missing, but healers are set in the right Blizzard role, they should appear as healers. The situation with tanks is a little more complicated, and I won't go into it unless you ask me to.
In fact, if you have the option set to use blizzard role data, and blizzard roles are set correctly, the only characters that will still sometimes be in the wrong role are those that have both a ranged and a melee spec, i.e. druids and shamans. But I wouldn't recommend ignoring that remaining issue. Knowing who is ranged and who is melee is obviously really often very important.
There is also an option to give preference to the blizzard role setting. I personally would never use this. This addon is how I know what spec players are REALLY in. If my tank is still in his dps or healing spec, or my healer is still specced boomkin, it's evident on my screen, and I can say something when even they may not have realized. I can't tell you how many disasters have been averted that way.
Could someone help me with an issue with this addon please?
I have Grid configured to automatically switch my profiles when I change my current spec. And every time after I respec, except the first one in a game session, I would get this error message:
Message: Interface\AddOns\Grid\GridFrame.lua:605: attempt to perform arithmetic on local 'g' (a nil value)
Time: 06/22/14 17:40:09
Count: 4
Stack: (tail call): ?
Interface\AddOns\Grid\GridFrame.lua:605: in function `SetBarColor'
Interface\AddOns\Grid\GridFrame.lua:810: in function `SetIndicator'
Interface\AddOns\Grid\GridFrame.lua:1619: in function `UpdateIndicator'
Interface\AddOns\Grid\GridFrame.lua:1592: in function `UpdateIndicators'
Interface\AddOns\Grid\GridFrame.lua:1542: in function `UpdateAllFrames'
Interface\AddOns\Grid\GridFrame.lua:1504: in function `PostReset'
Interface\AddOns\Grid\GridCore.lua:244: in function `Reset'
Interface\AddOns\Grid\GridCore.lua:620: in function `ResetModules'
Interface\AddOns\Grid\GridCore.lua:462: in function `?'
...ibDataBroker\CallbackHandler\CallbackHandler-1.0.lua:147: in function <...ibDataBroker\CallbackHandler\CallbackHandler-1.0.lua:147>
[string "safecall Dispatcher[3]"]:4: in function <[string "safecall Dispatcher[3]"]:4>
[C]: ?
[string "safecall Dispatcher[3]"]:13: in function `?'
...ibDataBroker\CallbackHandler\CallbackHandler-1.0.lua:92: in function `Fire'
...\AddOns\Broker_Currency\libs\AceDB-3.0\AceDB-3.0.lua:462: in function `SetProfile'
...AddOns\Grid\Libs\LibDualSpec-1.0\LibDualSpec-1.0.lua:193: in function `CheckDualSpecState'
...AddOns\Grid\Libs\LibDualSpec-1.0\LibDualSpec-1.0.lua:351: in function <...AddOns\Grid\Libs\LibDualSpec-1.0\LibDualSpec-1.0.lua:336>
This only happens when GCL is turned on.
I LOVE this addon, btw. Even need to manually /reload UI on every respec wouldn't make me stop me using it :)
I've fixed this issue by editing my SavedVariables/Grid.lua. It contained this record:
["Default"] = {
["unit_healthDeficit"] = {
["useClassColors"] = false,
["enable"] = false,
["color"] = {
["r"] = 0.4,
["b"] = 0.7529411764705882,
},
},
["alert_lowHealth"] = {
["threshold"] = 34,
["color"] = {
["b"] = 0.2313725490196079,
["r"] = 0.0001,
},
},
...
},
As you can see there are some missing ["g"] values. Apparently Grid don't save color components if they are equal to 1. So I've just added this line to every ["color'] record: ["g"] = 0.9999
But it is still weird how Grid works well with this issue, and stops working once I turn GCL on :-/
<<reply 2190466="">>
It was my pleasure. This is an excellent Grid layout addon that I've used for over a year now.
Thanks jlam. Had a look and have tagged your change as a release.
<<reply 2174106="">>
I've commited a fix for this in r117 so you can grab the latest alpha to get this working again. We will need to wait for MSaint to tag a new release.
Are you working on fixing this up for the new version of Grid's Flex mode? (Doesn't work at all at the moment)
Edit: When loading in Flex with the new grid version, it puts everyone in the tank group regardless of settings (as far as I found). Not sure if there was an error message or not.
I don't know what I'm doing wrong but I cant seem to find out. I'm trying to make it for a 25 Man where the far left i ahve the 2 tanks in there own group then healers in the next 2 groups then dps the rest but it doesnt seem to work like that in the group filter. Can you help me out at all?
Yes. Each filter captures ALL raid members of that type. What you want is to define the column / row size to 5 if it isn't already at 5. If you have 6 or more healers, it will look like two groups of healers, if you have less, then it will look like one group. So set the filter to g1 = tanks, g2 = healers, g3 = damagers. You can also set g3 = group1, g4 = group2, etc, and you will have the dps organized by group, but the tanks and healers will not be included because they were captured in the first two groups.
Does that clarify it? I can try again if not.
Hi folks. It's been a rough year and some, but I'm back and will look at this and fix it up for 5.4.
Hi folks. Been away a long time for reasons waaayyy beyond my control. I'll have a look at the addon and get it working and updated.