Interface\AddOns\PitBull\libs\LibDogTag-2.0\LibDogTag-2.0.lua:428:unexpected symbol near '['
its completely disabling the pitbull raid frames. I've tried downloading the newest dogtag2.0 from the SVN but this hasn't fixed the error either.
You can go into the lua and add L to the front of the 5 lines or so starting at line 428, they are missing. That is what I did until a fix is up on WAU.
You can go into the lua and add L to the front of the 5 lines or so starting at line 428, they are missing. That is what I did until a fix is up on WAU.
Yep that's what I did to fix it. I also removed the commas at the end of each line in that area, since no other lines around them had it.
Huh? What you said didn't make any logical sense, since that'd be like asking why use Elk's Buffbar or anything else. Not trying to sound bad, but you do know what Buffalo's function is? hehe. Buffalo doesn't have any commands to hide buff/debuff frames. So, it isn't a really "double-negative."
It's an issue and somebody else posted the same problem, so like most people I simply asked if anybody had any suggestions how to fix this besides double clicking the option in the Pitbull menu each time I log in.
Example:
Actually, yes- I do know what Buffalo is. Though I possibly could have phrased that a bit better or you could have phrased better what you wanted to accomplish.
Before ck added buffs to the list of blizz frames to disable, people used Buffalo to hide them and only use the buff display provided by PitBull. (Yes, you can use it to hide your buffs.)
Buffalo is essentially default blizz icon style buffs, but scalable and movable. If you only want to use the buff display from PitBull, then you don't need Buffalo. If you want to see buffs through Buffalo, then stop trying to mess with the buff frame in PitBull and conflicting with Buffalo.
edit: in short, don't hide the buff frame in PitBull.
Yup. The only fix is actually going into the config window in Pitbull and double clicking the 'Hide Default Buff framewhateveritscalled' and that isn't how PitBull or Buffalo has traditionally worked for...well, ever. To clarify, that fixes it until I log out and back in, then it shows up yet again until I go back into the config menu again to doubleclick it.
Small issue in comparison to others people have found, but when going to the Focus module---> Text, if I check the "Hidden" option for Position, it'll hide the text fine. But unchecking it does not unhide the text.
I have a problem with the Range check function.
I'm currently leveling a priest and plan on being a healer with him, but only when he hits 70. Until then he's gonna be melting faces. My problem is that I know Pitbull pr. default uses "Flash Heal" to check for OOR. I practically only solo grind my way up, so I need to change this to Mind Blast/SW: Pain. Additionally I don't know the code I have to use in my RangeCheck.lua file. I found this line
if class == "PRIEST" then
distanceCheckFunction = function(unit) return IsSpellInRange(BS["Flash Heal"], unit) == 1 or not UnitIsFriend("player", unit) end
What do I have to add to make Pitbull use Rangecheck on Enemy Targets as well?
The most optimal solution would be to check with Mind Blast/SW: Pain when I targeted an enemy and when I targeted a friendly target it checked with Flash heal (I suggest changing the default to Lesser Heal btw, since you only get Flash Heal at lvl 20 so until then it bugs - at least it did for me).
did you try reloading your UI after copying a layout from one uf to another, Kinesia?
No I didn't. Since the other options are updated automatically when copying a layout I didn't really consider that some other options might require a reload...
I've updated the sizes all manually now anyway, so I've no way to really check.
Regarding casting bars:
As you can see on the picture below in the group frames (top middle of the image), the paladin is casting a spell (big "Flash of.."). The casting bar is basically 1-2 px in height. Previously (before the Rock migration), the spell name text scaled with the size of the casting bar. However this is no longer the case and I have not been able to find an option to adjust this. Anyone have an idea if its possible to make the text smaller again?
I have a problem with the Range check function.
I'm currently leveling a priest and plan on being a healer with him, but only when he hits 70. Until then he's gonna be melting faces. My problem is that I know Pitbull pr. default uses "Flash Heal" to check for OOR. I practically only solo grind my way up, so I need to change this to Mind Blast/SW: Pain. Additionally I don't know the code I have to use in my RangeCheck.lua file. I found this line
if class == "PRIEST" then
distanceCheckFunction = function(unit) return IsSpellInRange(BS["Flash Heal"], unit) == 1 or not UnitIsFriend("player", unit) end
What do I have to add to make Pitbull use Rangecheck on Enemy Targets as well?
The most optimal solution would be to check with Mind Blast/SW: Pain when I targeted an enemy and when I targeted a friendly target it checked with Flash heal (I suggest changing the default to Lesser Heal btw, since you only get Flash Heal at lvl 20 so until then it bugs - at least it did for me).
Thank you in advance.
Im no LUA coder but changing the settings for priest class to what is below would do it?
if class == "PRIEST" then
distanceCheckFunction = function(unit) return IsSpellInRange(BS["Flash Heal"], unit) == 1 or IsSpellInRange(BS["Mind Blast"], unit) == 1 end
I downloaded PItBull through WAU las night and some of my configurations where lost. So I opened the new nice config window and when I choosed pitbull from the drop down menu the whole thing started to respond VERY slow. I wanted to uncheck the "relation lines" (I guess I don't know the exact name) and after I clicked on the check box it took over 5 seconds to respond... and it takes the same amount of time to change from module or closing the config window.
Any ideas on what can be slowing down the configuration window?
When I install the latest pitbull (currently r53016.10) I get alot of errors in continuous loops and my custom frames don't work. When I revert back to r51570, everything is fine again.
Firstly I recently installed Pitbull and I like if very much, thanks for such a good addon.
I have a very small question on the Pitbull health bar.
I have a custom backdrop color of plain black, set for All Units health bars, and I also have enabled the aggro indicator, to switch the bar to red when aggroed. However when it switches to red, the backdrop reverts to the default, not the black backdrop.
I have searched all the options and I cannot find how to customize this aggroed health bar backdrop, is there such an option?
Firstly I recently installed Pitbull and I like if very much, thanks for such a good addon.
I have a very small question on the Pitbull health bar.
I have a custom backdrop color of plain black, set for All Units health bars, and I also have enabled the aggro indicator, to switch the bar to red when aggroed. However when it switches to red, the backdrop reverts to the default, not the black backdrop.
I have searched all the options and I cannot find how to customize this aggroed health bar backdrop, is there such an option?
I had the same problem and I don't think there's an answer in the options and settings of Pitbull.
Editing Banzai.lua to get rid of this problem is easy though...
Find:
local banzai
local backgroundColors = {0, 0, 0, 1}
local function updateBGColor(color)
for i, v in ipairs(color) do
backgroundColors[i] = (v + 0.2) / 3
end
backgroundColors[4] = 1
end
function PitBull_Banzai:OnInitialize()
self.db = PitBull:GetDatabaseNamespace("Banzai")
PitBull:SetDatabaseNamespaceDefaults("Banzai", "profile", {
color = {1.0, 0, 0, 1.0},
groups = {
target = {
ignore = true,
},
targettarget = {
ignore = true,
},
targettargettarget = {
ignore = true,
},
["*"] = {},
}
})
updateBGColor(self.db.profile.color)
end
and make it like this:
local banzai
local backgroundColors = {0, 0, 0, 1}
---local function updateBGColor(color)
--- for i, v in ipairs(color) do
--- backgroundColors[i] = (v + 0.2) / 3
--- end
--- backgroundColors[4] = 1
---end
function PitBull_Banzai:OnInitialize()
self.db = PitBull:GetDatabaseNamespace("Banzai")
PitBull:SetDatabaseNamespaceDefaults("Banzai", "profile", {
color = {1.0, 0, 0, 1.0},
groups = {
target = {
ignore = true,
},
targettarget = {
ignore = true,
},
targettargettarget = {
ignore = true,
},
["*"] = {},
}
})
--- updateBGColor(self.db.profile.color)
end
The three -'s in front of the lines will make them ignored. Deleting the lines should work just as well :)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Interface\AddOns\PitBull\libs\LibDogTag-2.0\LibDogTag-2.0.lua:428:unexpected symbol near '['
its completely disabling the pitbull raid frames. I've tried downloading the newest dogtag2.0 from the SVN but this hasn't fixed the error either.
You can go into the lua and add L to the front of the 5 lines or so starting at line 428, they are missing. That is what I did until a fix is up on WAU.
Yep that's what I did to fix it. I also removed the commas at the end of each line in that area, since no other lines around them had it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumActually, yes- I do know what Buffalo is. Though I possibly could have phrased that a bit better or you could have phrased better what you wanted to accomplish.
Before ck added buffs to the list of blizz frames to disable, people used Buffalo to hide them and only use the buff display provided by PitBull. (Yes, you can use it to hide your buffs.)
Buffalo is essentially default blizz icon style buffs, but scalable and movable. If you only want to use the buff display from PitBull, then you don't need Buffalo. If you want to see buffs through Buffalo, then stop trying to mess with the buff frame in PitBull and conflicting with Buffalo.
edit: in short, don't hide the buff frame in PitBull.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNotepad++
Even with the box unchecked, the problem still persists though.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhrmmmmmm
Yup. The only fix is actually going into the config window in Pitbull and double clicking the 'Hide Default Buff framewhateveritscalled' and that isn't how PitBull or Buffalo has traditionally worked for...well, ever. To clarify, that fixes it until I log out and back in, then it shows up yet again until I go back into the config menu again to doubleclick it.
I personally use SCiTe LUA to hack things up with. :)
I have a problem with the Range check function.
I'm currently leveling a priest and plan on being a healer with him, but only when he hits 70. Until then he's gonna be melting faces. My problem is that I know Pitbull pr. default uses "Flash Heal" to check for OOR. I practically only solo grind my way up, so I need to change this to Mind Blast/SW: Pain. Additionally I don't know the code I have to use in my RangeCheck.lua file. I found this line
if class == "PRIEST" then distanceCheckFunction = function(unit) return IsSpellInRange(BS["Flash Heal"], unit) == 1 or not UnitIsFriend("player", unit) endWhat do I have to add to make Pitbull use Rangecheck on Enemy Targets as well?
The most optimal solution would be to check with Mind Blast/SW: Pain when I targeted an enemy and when I targeted a friendly target it checked with Flash heal (I suggest changing the default to Lesser Heal btw, since you only get Flash Heal at lvl 20 so until then it bugs - at least it did for me).
Thank you in advance.
No I didn't. Since the other options are updated automatically when copying a layout I didn't really consider that some other options might require a reload...
I've updated the sizes all manually now anyway, so I've no way to really check.
As you can see on the picture below in the group frames (top middle of the image), the paladin is casting a spell (big "Flash of.."). The casting bar is basically 1-2 px in height. Previously (before the Rock migration), the spell name text scaled with the size of the casting bar. However this is no longer the case and I have not been able to find an option to adjust this. Anyone have an idea if its possible to make the text smaller again?
Big: http://farm3.static.flickr.com/2406/1714023689_beaad313f4_o.jpg
Im no LUA coder but changing the settings for priest class to what is below would do it?
I dont have a priest so i havent checked it :)
Any ideas on what can be slowing down the configuration window?
When I install the latest pitbull (currently r53016.10) I get alot of errors in continuous loops and my custom frames don't work. When I revert back to r51570, everything is fine again.
Here are the errors:
http://www.simnet.is/krja/myndir/WoWScrnShot_102507_141757.jpg
http://www.simnet.is/krja/myndir/WoWScrnShot_102507_141820.jpg
http://www.simnet.is/krja/myndir/WoWScrnShot_102507_141825.jpg
Thanks in advance.
I have a very small question on the Pitbull health bar.
I have a custom backdrop color of plain black, set for All Units health bars, and I also have enabled the aggro indicator, to switch the bar to red when aggroed. However when it switches to red, the backdrop reverts to the default, not the black backdrop.
I have searched all the options and I cannot find how to customize this aggroed health bar backdrop, is there such an option?
-
View User Profile
-
View Posts
-
Send Message
Curse Premium@Arcanefoam: not sure why it would be slowing you down so much... Did you get any errors at all? Was a virus scanner running in the background?
I had the same problem and I don't think there's an answer in the options and settings of Pitbull.
Editing Banzai.lua to get rid of this problem is easy though...
Find:
local banzai local backgroundColors = {0, 0, 0, 1} local function updateBGColor(color) for i, v in ipairs(color) do backgroundColors[i] = (v + 0.2) / 3 end backgroundColors[4] = 1 end function PitBull_Banzai:OnInitialize() self.db = PitBull:GetDatabaseNamespace("Banzai") PitBull:SetDatabaseNamespaceDefaults("Banzai", "profile", { color = {1.0, 0, 0, 1.0}, groups = { target = { ignore = true, }, targettarget = { ignore = true, }, targettargettarget = { ignore = true, }, ["*"] = {}, } }) updateBGColor(self.db.profile.color) endand make it like this:
local banzai local backgroundColors = {0, 0, 0, 1} ---local function updateBGColor(color) --- for i, v in ipairs(color) do --- backgroundColors[i] = (v + 0.2) / 3 --- end --- backgroundColors[4] = 1 ---end function PitBull_Banzai:OnInitialize() self.db = PitBull:GetDatabaseNamespace("Banzai") PitBull:SetDatabaseNamespaceDefaults("Banzai", "profile", { color = {1.0, 0, 0, 1.0}, groups = { target = { ignore = true, }, targettarget = { ignore = true, }, targettargettarget = { ignore = true, }, ["*"] = {}, } }) --- updateBGColor(self.db.profile.color) endThe three -'s in front of the lines will make them ignored. Deleting the lines should work just as well :)