Considering that that plugin is designed to tell you who and when to heal, I sincerely hope that it, or anything like it, is never part of the core of any version of Grid.
Agreed, it would be really disrupting, specially if you tend to oliberate those punny mages that keep spaming fireball while they're being hit hard by the shadow images on Eredar Twins... Speaking of Eredar, will Grid2 implement some short of conditional statuses? A clear example of that would be a status that changed color when Kalecgos' curse has less than 10 seconds remaining.
Considering that that plugin is designed to tell you who and when to heal, I sincerely hope that it, or anything like it, is never part of the core of any version of Grid.
For 5 mans and 10 mans I can agree. If your set to be a raid healer in a 25 man it can very helpful. Every healer in my guild uses Grid with Clique and GridSHPriority. I know some who will never use unless they are in a 25 man. Some might say its considered cheap, some say it helps you understand when and how to heal in a raid situation. Honestly the second of the two works for us.
It doesn't matter whether it's useful or not. It does matter whether it's something I want to see included or not. I do not want to see it included.
Grid (and Grid2, by extension) should give you the best information possible in the least intrusive way so that you can decide who to heal and for how much. Grid should not make that decision for you.
I'm not saying that another addon may not add this kind of functionality to Grid2. I don't care about that. I do not want the default Grid2 to enforce some kind of choice to healers.
Well I found out some bad news. The code that was used for Libs pre 3.0 is no longer implemented in WoW, so meaning mods like LibThreat2.0 and MobHealth no longer work in WoW in it's current state. Also means many Grid addons will not work either like GSHPrority or any other healing estimator addon.
For 5 mans and 10 mans I can agree. If your set to be a raid healer in a 25 man it can very helpful. Every healer in my guild uses Grid with Clique and GridSHPriority. I know some who will never use unless they are in a 25 man. Some might say its considered cheap, some say it helps you understand when and how to heal in a raid situation. Honestly the second of the two works for us.
Eh, if Grid is set up properly, you should never have a problem figuring out who to heal without something placing a big "HEAL THIS GUY NOW" sign on someone for you.
Well I found out some bad news. The code that was used for Libs pre 3.0 is no longer implemented in WoW, so meaning mods like LibThreat2.0 and MobHealth no longer work in WoW in it's current state. Also means many Grid addons will not work either like GSHPrority or any other healing estimator addon.
Those are both good news, because their demise means less code everyone has to run.
MobHealth is no longer needed, and can simply be removed from anything that used it, as WoW now gives you the actual health values for everything.
LibThreat-2.0 is no longer needed, and addons that used it should be updated to use the new threat API functions Blizzard has added to the game.
[2008/10/21 17:17:05-784-x1]: Grid2Options\core.lua:34: attempt to index local 'element' (a nil value)
Grid2Options\GridIndicators.lua:99: in function `AddBarIndicatorOptions'
Grid2Options\GridIndicators.lua:162: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 6 $\GridCore.lua:144: in function `LoadOptions'
Grid2-$Rev: 6 $\GridCore.lua:152: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3212: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2911: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2932: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
---
2008/10/21 17:17:05-784-x1]: AceLocale-3.0: Grid2Options: Missing entry for 'Default pet Color':
Grid2Options\GridStatuses.lua:89: in function `MakeClassColorStatusOptions'
Grid2Options\GridStatuses.lua:131: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 6 $\GridCore.lua:144: in function `LoadOptions'
Grid2-$Rev: 6 $\GridCore.lua:152: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3212: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2911: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2932: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
---
[2008/10/21 17:17:05-784-x1]: Grid2Options\core.lua:108: attempt to call global 'InterfaceOptionsFrame_OpenToFrame' (a nil value)
Grid2-$Rev: 6 $\GridCore.lua:154: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3212: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2911: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2932: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
[2008/10/27 13:19:01-823-x1]: Grid2-$Rev: 15 $\GridIndicator.lua:97: assertion failed!
Grid2-$Rev: 15 $\GridIndicator.lua:97: in function `RegisterIndicator'
Grid2-$Rev: 15 $\modules\IndicatorBar.lua:126: in function `CreateBarIndicator'
Grid2-$Rev: 15 $\modules\IndicatorBar.lua:131: in main chunk
---
when trying to call options:
[2008/10/27 13:21:32-823-x1]: Grid2Options\core.lua:34: attempt to index local 'element' (a nil value)
Grid2Options\GridIndicators.lua:143: in function `AddBarColorIndicatorOptions'
Grid2Options\GridIndicators.lua:163: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 15 $\GridCore.lua:142: in function `LoadOptions'
Grid2-$Rev: 15 $\GridCore.lua:150: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3212: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2911: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2932: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
---
PS: do you actualy want this bugs posted since its alpha and "This code is HIGHLY experimental, and should not be used." ? maybe you prefere tickets? i compleatly understand if you dont want to be buged with them at all, posting them just in hope i can remove 1 more ace2 addon till wotlk release ;)
PS: do you actualy want this bugs posted since its alpha and "This code is HIGHLY experimental, and should not be used." ? maybe you prefere tickets? i compleatly understand if you dont want to be buged with them at all, posting them just in hope i can remove 1 more ace2 addon till wotlk release ;)
As long as this thread does not become a long list of the same bug reported over and over, it doesn't hurt. Development on Grid2 is scarse, although I've been working a bit on Grid2Alert, and I have started to think about Grid2StatusRaidDebuff (mainly about naming it something else :-) )
[2008/10/28 11:54:01-832-x1]: Grid2Alert\core.lua:155: attempt to index global 'GridAlert' (a nil value)
---
[2008/10/28 11:54:01-832-x1]: LibSink-2.0\LibSink-2.0.lua:693: Storage must be a table
LibSink-2.0\LibSink-2.0.lua:693: in function `SetSinkStorage'
Grid2Alert\core.lua:131: in function <Interface\AddOns\Grid2Alert\core.lua:126>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:340: in function `InitializeAddon'
AceAddon-3.0\AceAddon-3.0.lua:428: in function <...Ons\ag_UnitFrames\libs\AceAddon-3.0\AceAddon-3.0.lua:421>
but ye i personly like kinda "all in one important plugins" idea, everyone can just turn off what they dont need... im sure every raider that is using grid is also using *raiddebuff and if you are buffing class *missingbuffs (or well at least they should -.-, would be much less of "can i get pof please?")
edit: there is still a lot of problems with options and Grid2Alert even in r21, but you probably know about them, for ex. defaults supposed to be part of Grid2Layout and fetched with self., if you change to Grid2Alert, then they get saved and all but there is no way to access them from Grid2Options, since there would need to be added there also + libsink should be fixed in .pkgmeta
but ye i personly like kinda "all in one important plugins" idea, everyone can just turn off what they dont need... im sure every raider that is using grid is also using *raiddebuff and if you are buffing class *missingbuffs (or well at least they should -.-, would be much less of "can i get pof please?")
I strongly disagree. The whole point of a modular design like Grid's is that users aren't forced to run the code for 500 features when they only want to use 12 of them. Even if you "turn off" the features you don't need, if those features are all in the same plugin as the features you do use, you're still running the code to support them.
For example, you obviously think that every class who can cast buffs should use MissingBuffs. However, I do not use this plugin on my druid, my boyfriend does not use this plugin on his priest, and I'm sure there are many other players who are able to play their class correctly in groups without the aid of this plugin. If you like it, great, use it, but bear in mind that not everyone shares your opinions or your likes and dislikes.
Same goes for RaidDebuff; it is in no way necessary for raiding with Grid at any level. In fact, on my resto shaman in a Sunwell raiding guild, it got to the point where I realized I was turning off most of the debuffs, and since the plugin was so plagued by bugs at that point, I just got rid of it, and have had no problems since then manually adding the 1 or 2 debuffs per boss that I actually care to see.
If you want 500 features, install more plugins. Installing plugins is not in any way difficult, and in most cases running 10 plugins that each do 1 thing instead of running 1 plugin that does 10 things does not adversely affect performance.
Well at the end of the day it doesnt matter if its as standalone plugin or part of main addon, but back in the days when i was raidleader i always tryed to "force" people to use it because i got less excuses ;) its not about knowing how to play class, im sure everyone gets rebuffed once/hour but people die and those people sometimes doesnt get rebuffed unless they whine or have big icon on grid that he needs buff :) even when i played feral druid a bit last few months i was buffing people just because this annoying big icon in the middle of his frame that he is missing buff and since i didnt have imp motw this shouldnt be my "job" at all... I just feel that *missingbuffs should be *must* pluging for each buffing class at least and raidleader, but this is only my personal oppinion. People in most cases needs to be pushed in certain direction, because they wont do shit on their own.
About *raiddebuff is a bit different since it works like big filter and needs to be updated all the time so maybe its not that usefull, since most of time people should only care for debuffs they can cure and this filter i think it exists already in default grid/grid2.
It's a matter of personnal preference, really. I am a raid leader, and I am very conscious about buffing, not only for the class I play, but all raid buffs in general. For that, GridStatusMissingBuff is not sufficient. I use XRaidStatus for the purpose of checking who is missing a buff. It works great. I don't need GridStatusMissingBuff.
As I said in the commit, the long term plan is not to have Grid2Alert with Grid2. Right now, I want it in there so that there is a single place where the test code is. I'll also add Grid2StatusRaidDebuff once I figure out how I'm going to do it.
Also, soon to be added is separate layout configuration for Heroïc / Normal raids, which will be handy in wotlk.
I have one request. I have been a fan of Grid since you first made it and have been using i since then.
Can we please control the amount columns (if grid is horizontal) or rows (if grid is vertical)?
I ask this because I have recently been using grid in groups, as I find that I am MUCH more efficient healer with grid on all the time. This issue comes up because I like to keep pets in view also. my UI does not allow for grid to extend beyond a certain with. You do this with the raid setup it would just be nice if it was working for dynamic/group situations.
Grid is an original idea from Maia, that came into being with the work of both Maia and Pastamancer. I came very late in the development of Grid. Lots of design decisions is still present in Grid2, although most of the code has been rewritten.
You can make Grid show only the number of column you want by editing the attributes of a particular layout. This has to be done in the lua source code (either with Grid or Grid2), at least until someone writes a layout editor (which would be a fun project).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Agreed, it would be really disrupting, specially if you tend to oliberate those punny mages that keep spaming fireball while they're being hit hard by the shadow images on Eredar Twins... Speaking of Eredar, will Grid2 implement some short of conditional statuses? A clear example of that would be a status that changed color when Kalecgos' curse has less than 10 seconds remaining.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI agree
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumGrid (and Grid2, by extension) should give you the best information possible in the least intrusive way so that you can decide who to heal and for how much. Grid should not make that decision for you.
I'm not saying that another addon may not add this kind of functionality to Grid2. I don't care about that. I do not want the default Grid2 to enforce some kind of choice to healers.
Atleast I got to let you guys know.
Eh, if Grid is set up properly, you should never have a problem figuring out who to heal without something placing a big "HEAL THIS GUY NOW" sign on someone for you.
Those are both good news, because their demise means less code everyone has to run.
MobHealth is no longer needed, and can simply be removed from anything that used it, as WoW now gives you the actual health values for everything.
LibThreat-2.0 is no longer needed, and addons that used it should be updated to use the new threat API functions Blizzard has added to the game.
[2008/10/21 17:17:05-784-x1]: Grid2Options\core.lua:34: attempt to index local 'element' (a nil value)
Grid2Options\GridIndicators.lua:99: in function `AddBarIndicatorOptions'
Grid2Options\GridIndicators.lua:162: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 6 $\GridCore.lua:144: in function `LoadOptions'
Grid2-$Rev: 6 $\GridCore.lua:152: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3212: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2911: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2932: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
---
2008/10/21 17:17:05-784-x1]: AceLocale-3.0: Grid2Options: Missing entry for 'Default pet Color':
Grid2Options\GridStatuses.lua:89: in function `MakeClassColorStatusOptions'
Grid2Options\GridStatuses.lua:131: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 6 $\GridCore.lua:144: in function `LoadOptions'
Grid2-$Rev: 6 $\GridCore.lua:152: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3212: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2911: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2932: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
---
[2008/10/21 17:17:05-784-x1]: Grid2Options\core.lua:108: attempt to call global 'InterfaceOptionsFrame_OpenToFrame' (a nil value)
Grid2-$Rev: 6 $\GridCore.lua:154: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3212: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2911: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2932: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
---
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumwhat he is talking about is this
this is wotlk client, but its same on retail...
I too have those white horizontal bars.
Me 3 ... and I didn't seem to get any health bars.
[2008/10/27 13:19:01-823-x1]: Grid2-$Rev: 15 $\GridIndicator.lua:97: assertion failed!
Grid2-$Rev: 15 $\GridIndicator.lua:97: in function `RegisterIndicator'
Grid2-$Rev: 15 $\modules\IndicatorBar.lua:126: in function `CreateBarIndicator'
Grid2-$Rev: 15 $\modules\IndicatorBar.lua:131: in main chunk
---
when trying to call options:
[2008/10/27 13:21:32-823-x1]: Grid2Options\core.lua:34: attempt to index local 'element' (a nil value)
Grid2Options\GridIndicators.lua:143: in function `AddBarColorIndicatorOptions'
Grid2Options\GridIndicators.lua:163: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 15 $\GridCore.lua:142: in function `LoadOptions'
Grid2-$Rev: 15 $\GridCore.lua:150: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3212: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2911: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2932: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
---
PS: do you actualy want this bugs posted since its alpha and "This code is HIGHLY experimental, and should not be used." ? maybe you prefere tickets? i compleatly understand if you dont want to be buged with them at all, posting them just in hope i can remove 1 more ace2 addon till wotlk release ;)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAs long as this thread does not become a long list of the same bug reported over and over, it doesn't hurt. Development on Grid2 is scarse, although I've been working a bit on Grid2Alert, and I have started to think about Grid2StatusRaidDebuff (mainly about naming it something else :-) )
Why rename it? The current name makes it very obvious what the plugin does.
[2008/10/28 11:54:01-832-x1]: Grid2Alert\core.lua:155: attempt to index global 'GridAlert' (a nil value)
---
[2008/10/28 11:54:01-832-x1]: LibSink-2.0\LibSink-2.0.lua:693: Storage must be a table
LibSink-2.0\LibSink-2.0.lua:693: in function `SetSinkStorage'
Grid2Alert\core.lua:131: in function <Interface\AddOns\Grid2Alert\core.lua:126>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:340: in function `InitializeAddon'
AceAddon-3.0\AceAddon-3.0.lua:428: in function <...Ons\ag_UnitFrames\libs\AceAddon-3.0\AceAddon-3.0.lua:421>
but ye i personly like kinda "all in one important plugins" idea, everyone can just turn off what they dont need... im sure every raider that is using grid is also using *raiddebuff and if you are buffing class *missingbuffs (or well at least they should -.-, would be much less of "can i get pof please?")
edit: there is still a lot of problems with options and Grid2Alert even in r21, but you probably know about them, for ex. defaults supposed to be part of Grid2Layout and fetched with self., if you change to Grid2Alert, then they get saved and all but there is no way to access them from Grid2Options, since there would need to be added there also + libsink should be fixed in .pkgmeta
I strongly disagree. The whole point of a modular design like Grid's is that users aren't forced to run the code for 500 features when they only want to use 12 of them. Even if you "turn off" the features you don't need, if those features are all in the same plugin as the features you do use, you're still running the code to support them.
For example, you obviously think that every class who can cast buffs should use MissingBuffs. However, I do not use this plugin on my druid, my boyfriend does not use this plugin on his priest, and I'm sure there are many other players who are able to play their class correctly in groups without the aid of this plugin. If you like it, great, use it, but bear in mind that not everyone shares your opinions or your likes and dislikes.
Same goes for RaidDebuff; it is in no way necessary for raiding with Grid at any level. In fact, on my resto shaman in a Sunwell raiding guild, it got to the point where I realized I was turning off most of the debuffs, and since the plugin was so plagued by bugs at that point, I just got rid of it, and have had no problems since then manually adding the 1 or 2 debuffs per boss that I actually care to see.
If you want 500 features, install more plugins. Installing plugins is not in any way difficult, and in most cases running 10 plugins that each do 1 thing instead of running 1 plugin that does 10 things does not adversely affect performance.
About *raiddebuff is a bit different since it works like big filter and needs to be updated all the time so maybe its not that usefull, since most of time people should only care for debuffs they can cure and this filter i think it exists already in default grid/grid2.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAs I said in the commit, the long term plan is not to have Grid2Alert with Grid2. Right now, I want it in there so that there is a single place where the test code is. I'll also add Grid2StatusRaidDebuff once I figure out how I'm going to do it.
Also, soon to be added is separate layout configuration for Heroïc / Normal raids, which will be handy in wotlk.
Can we please control the amount columns (if grid is horizontal) or rows (if grid is vertical)?
I ask this because I have recently been using grid in groups, as I find that I am MUCH more efficient healer with grid on all the time. This issue comes up because I like to keep pets in view also. my UI does not allow for grid to extend beyond a certain with. You do this with the raid setup it would just be nice if it was working for dynamic/group situations.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumGrid is an original idea from Maia, that came into being with the work of both Maia and Pastamancer. I came very late in the development of Grid. Lots of design decisions is still present in Grid2, although most of the code has been rewritten.
You can make Grid show only the number of column you want by editing the attributes of a particular layout. This has to be done in the lua source code (either with Grid or Grid2), at least until someone writes a layout editor (which would be a fun project).