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.
GridStatusRole + GridIndicatorSideIcons show tank/healer/ranged/melee from inspected spec (will be fix,bugzard work at v4.0.3). GridStatusDungeonRole + GridIndicatorSideIcons show Blizzard role check.
Ok! I'm finally home and at a computer! I've looked in to what is possible, and I've mapped out some changes.
Rather than pushing out a quick improvement, I'm going to take a couple of days and produce a solution that gives the user some control over what info is used (blizztanks, rolecheck info, talent info) and how to prioritize it, and I am going to completely re-write how roles are determined and who gets inspected when. I'll try to remember to post here when I get an alpha out, but in any case, check the wowace page in two or three days. I should have something worth testing by then.
1x ...\GridConfigurableLayouts\GridConfigurableLayouts.lua:1379: attempt to index global 'header' (a nil value): ...\GridConfigurableLayouts\GridConfigurableLayouts.lua:1151: in function <...\GridConfigurableLayouts\GridConfigurableLayouts.lua:1146>: <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-6:92: in function `SendMessage' Grid-1.40000.1370\GridRoster.lua:243: in function <Grid\GridRoster.lua:190> (tail call): ?: CallbackHandler-1.0-6:147: in function <...non\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147> <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-6:92: in function `Fire' AceEvent-3.0-3 (Bagnon):120: in function <...ace\AddOns\Bagnon\libs\AceEvent-3.0\AceEvent-3.0.lua:119>
Thanks for this. I will not be able to look at it until Saturday as I am just leaving for the airport. I will post again on this as soon as I get the chance.
The old version had not been updated when you posted, deadca7. I was waiting on the libraries that this module uses to be updated to 4.0. It should work fine now.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
GridStatusDungeonRole + GridIndicatorSideIcons show Blizzard role check.
Rather than pushing out a quick improvement, I'm going to take a couple of days and produce a solution that gives the user some control over what info is used (blizztanks, rolecheck info, talent info) and how to prioritize it, and I am going to completely re-write how roles are determined and who gets inspected when. I'll try to remember to post here when I get an alpha out, but in any case, check the wowace page in two or three days. I should have something worth testing by then.
Thanks much for the feedback.
...\GridConfigurableLayouts\GridConfigurableLayouts.lua:1151: in function <...\GridConfigurableLayouts\GridConfigurableLayouts.lua:1146>:
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0-6:92: in function `SendMessage'
Grid-1.40000.1370\GridRoster.lua:243: in function <Grid\GridRoster.lua:190>
(tail call): ?:
CallbackHandler-1.0-6:147: in function <...non\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0-6:92: in function `Fire'
AceEvent-3.0-3 (Bagnon):120: in function <...ace\AddOns\Bagnon\libs\AceEvent-3.0\AceEvent-3.0.lua:119>
---