I would guess that the problem is related to this change:
r59445 | ckknight | 2008-01-26 09:44:25 -0500 (Sat, 26 Jan 2008) | 1 line
Changed paths:
M /trunk/PitBull/PitBull.lua
PitBull - standard right-click will no longer bring up the config menu
Try reverting to the version immediately prior to r59445 and see if this fixes your problem. Ellipsis linked the file list page in his post above.
UPDATE: Well, this gets stranger by the hour. The version I reverted to that I was having no problems with (56911), is now doing the exact same thing. ie, the entire WTF and Interface folders were reverted to the older version and it's doing it as well. This rules out Pitbull I suspect. And in fact I did some research and found 2 threads on the wow forums with people having the same issue:
I am completely at a loss. Reverting to known good backups of WTF and Interface folders that worked fine previously. Maybe it was the 2.3.3 patch and something in that.....but these above posts were made before 2.3.3.....so I dont know.......
I wish the Pitbull thread was easier to find information.
I did look and there is some talk of my issue but i cannot resolve it.
I currently use Pitbull for my priest.
During raids I would like to see the Main Tank window, MT target and MT targets target
I was not able to get it working via Pitbull so I loaded oRa2.
I read this could assist Pitbull in obtaining MT info.
I created a group, assigned MT and my bars did not show.
Is there a good way to get MT windows to work in Pitbull ?
I am having this exact same issue. I logged a JIRA on it (http://jira.wowace.com/browse/PB-159) but it doesn't appear to have been researched by the assignee. Although PB-77 describes a similar if not the same issue and it was resolved by updating the listener to something oRa2 specific.
Really wish this would get resolved as I prefer Pitbull over X-Perl. I would prefer not to have to run a hybrid configuration of the two simply to have my MT group displayed.
I am having this exact same issue. I logged a JIRA on it (http://jira.wowace.com/browse/PB-159) but it doesn't appear to have been researched by the assignee. Although PB-77 describes a similar if not the same issue and it was resolved by updating the listener to something oRa2 specific.
I have skipped over this issue when going through the Jira tickets for a few reasons - one, it's quite possibly user error (raid leader is not setting the MTs, or is using the wrong system - Blizz or oRA/CTRA); two, the linked screenshots in that ticket no longer exist, so I wasn't able to see exactly what the issue was. Can you provide screenshots or a better explanation of exactly what's happening?
I have skipped over this issue when going through the Jira tickets for a few reasons - one, it's quite possibly user error (raid leader is not setting the MTs, or is using the wrong system - Blizz or oRA/CTRA); two, the linked screenshots in that ticket no longer exist, so I wasn't able to see exactly what the issue was. Can you provide screenshots or a better explanation of exactly what's happening?
Here is a link to my original posts in the forums.
There are several messages in sequence that attempt to explain the issue.
Unfortunately, I didn't receive any troubleshooting feedback and the screenshots there, of course, are retired with the site that went down at the beginning of the year. It was after awaiting feedback that I decided to log it as a bug. As I stated in the JIRA, I will re-up the screenshots and provide valid links on my new server.
When you say "or is using the wrong system - Blizz or oRA/CTRA", are you stating that these are the "wrong systems"? It was my understanding that those three were compatible with PitBull.
My assumptions are that the Raid Leader is indeed setting the MT "properly" since the MT bar in X-Perl is loading with no apparent issues. I have also confirmed that he is using CTRA. The version of which, I'm not sure as of this posting but I can get that info and supplement the JIRA along with the updated screenshots.
Hello all,
Few quick questions, I'm hoping you guys can help with.
First off very happy with Pitbull, great frames.
1) Can I make the casting bar text smaller? Can't seem to find the option under Texts or the Cast Bar options.
2) Is it possible to split buffs & debuffs on top of a frame? Atm I have both my buffs/debuffs on top of the target frame, but they overlap. For instance targeting myself, with an aura on & forberance, I only see the aura. I'd like to make it so that buffs are to the left, and debuffs to the right on top of the frame.
3) I'm using borders around buff/debuffs, is it possible to make smaller movements of the buffs/debuffs. As the buff icon itself is perfectly lined up with the frame, but the borders make it hang over the frame.
today I tried to replace the "border.tga" (inside the "PitBull/Aura" folder) with a better looking alternative. But nothing really changed. Reloading, restarting WoW, deleting the cache files and so on didn't help there's still the old "boring" border art.
I actually removed the border.tga from the Pitbull/Aura folder to test if wow starts complaining, but again... nothing happend - no errors, simply nothing.
today I tried to replace the "border.tga" (inside the "PitBull/Aura" folder) with a better looking alternative. But nothing really changed. Reloading, restarting WoW, deleting the cache files and so on didn't help there's still the old "boring" border art.
Missing textures don't generate errors. It's possible the texture isn't actually used for anything; look inside the Aura.lua file to figure out which texture is used.
Guys, there is no thread search option and reading all 45 pages would be too long so Im posting my question here. Sorry If It had been asked before.
I was using agunitframes with OmniCC and Im a warlock. As you can guess, I need that timers on my dots on target frame. They were working perfect with ag_unitframes but in Pitbull they are bugged. I tried enabling/disabling Aura options, set OmniCC scale to %0 but still some of them shows, some of them doesnt.
Is there a solution to this ? I really loved PitBull but I also need those timers, I dont wanna change the style I play the game.
There is a "search thread" option... switch to the "SMF Default Theme". ;)
As for DoT timers on the target frame, I'm not sure what exactly is wrong, since "they are bugged" is not descriptive at all, but in general you have many options:
1. Make sure that "cooldown spiral" is enabled for auras in PitBull. OmniCC does not work for (de)buff icons -- (de)buff times are not cooldowns. :P
2. Use Quartz to provide timers for your debuffs on your target.
3. Use a general buff mod that can be configured to show your target's debuffs.
4. Use a warlock DoT timer mod.
If #1 doesn't solve your problem and you don't want to use another addon, give more details about how exactly PitBull's display of your DoTs is "bugged".
There is a "search thread" option... switch to the "SMF Default Theme". ;)
Thank you for that, didn't know it :)
As for DoT timers on the target frame, I'm not sure what exactly is wrong, since "they are bugged" is not descriptive at all, but in general you have many options:
1. Make sure that "cooldown spiral" is enabled for auras in PitBull. OmniCC does not work for (de)buff icons -- (de)buff times are not cooldowns. :P
OmniCC does show a cooldown on DoTs on Target frames even they are not cooldows but they way it shows has eyecandy so I like em thats why I wanna use em. But If I can manage to increase the size for Pitbull's DoT timers without touching all font sizes of unitframes that would be ok also.
2. Use Quartz to provide timers for your debuffs on your target.
Already have Quartz installed and running well but as I told before, I wanna see them on my target debuffs, not like a countdown bar.
3. Use a general buff mod that can be configured to show your target's debuffs.
4. Use a warlock DoT timer mod.
Have one "DotDotDot" but that has no difference from Quartz. Its also disabled.
If #1 doesn't solve your problem and you don't want to use another addon, give more details about how exactly PitBull's display of your DoTs is "bugged".
All Working :
Immolate Now not working.
Small numbers are PitBull's original numbers. The big numbers belong to OmniCC.
Hope I explained my problem better this time.
There are several messages in sequence that attempt to explain the issue.
Unfortunately, I didn't receive any troubleshooting feedback and the screenshots there, of course, are retired with the site that went down at the beginning of the year. It was after awaiting feedback that I decided to log it as a bug. As I stated in the JIRA, I will re-up the screenshots and provide valid links on my new server.
When you say "or is using the wrong system - Blizz or oRA/CTRA", are you stating that these are the "wrong systems"? It was my understanding that those three were compatible with PitBull.
My assumptions are that the Raid Leader is indeed setting the MT "properly" since the MT bar in X-Perl is loading with no apparent issues. I have also confirmed that he is using CTRA. The version of which, I'm not sure as of this posting but I can get that info and supplement the JIRA along with the updated screenshots.
I also use Xperl on my lock because I need the following.
1) Main Tank windows
2) MA targets
Xperl provides both while I play on my lock.
I cant get either to work in PB.
I tested MT windows in PB two seperate ways.
I created a group and assigned MT via oRA2 myself so I know it was done correctly.
I tried to get it working in a 25man raid setting where all other players could see MT windows but PB wasnt getting the info.
Raid leader was using CTRA (i think)
I'm sure it is probably some setting I need to change or some plugin i'm missing but I have no clue what that may be.
Missing textures don't generate errors. It's possible the texture isn't actually used for anything; look inside the Aura.lua file to figure out which texture is used.
Hm, ok. Didn't know that missing textures don't generate errors.
I did a quick google search on the topic and other people are replacing the same file with success. Also, there's a line like.. eh..
I have also replaced the aura border with success (which reminds me - I need to do that again, since PitBull was updated the other day). Make sure you've completely exited the game and restarted for the new texture to be loaded. Also, remember that you'll have to do it each and every time PitBull is updated, as it will be overwritten with the original file.
I have also replaced the aura border with success (which reminds me - I need to do that again, since PitBull was updated the other day). Make sure you've completely exited the game and restarted for the new texture to be loaded. Also, remember that you'll have to do it each and every time PitBull is updated, as it will be overwritten with the original file.
Well, that's what I did.
- exit wow
- replace border.tga
- restart wow
I tried several texture files without success. Some from people who told me that it worked for them.
Then I acutally changed the filename in the .lua. Still, nothing changed.
Is it possible that it has to do with some settings I missed? Currently I disabled the global aura settings (cooldown spiral, zoom textures)
??? You should be able to target yourself. Are you clicking on your unit frame? You can also press F1. Do you have any other mods that deal with clicks (like Clique) or the unit frames? etc.
After updating Pitbull a week ago i get this problem with buffs/debuffs floating in the powerbar.
Do you use Alt Aura?
If so, simply adjust the offsets of the respective buffs & debuffs as to place them where you'd like.
If not, you can always try using Alt Aura, disable the regular buff and debuff icons for Pitbull, and do the same thing with their (Alt Aura's) offsets.
I just auto-updated PitBull and I'm now getting errors (and it's not loading).
[2008/01/30 18:29:40-808-x1]: PitBull-2.0r59760\PitBull.lua:240: Library "LibDogTag-2.0" not found.
LibRock-1.0-40347 (LibRock-1.0):1667: in function `Rock'
PitBull-2.0r59760\PitBull.lua:240: in main chunk
---
[2008/01/30 18:29:40-808-x1]: PitBull-2.0r59760\PitBull_MetaLayout.lua:234: Library "LibDogTag-2.0" not found.
LibRock-1.0-40347 (LibRock-1.0):1667: in function `Rock'
PitBull-2.0r59760\PitBull_MetaLayout.lua:234: in main chunk
---
[2008/01/30 18:29:40-808-x1]: PitBull-2.0r59760\Layouts\ABF.lua:10: attempt to call method 'RegisterLayout' (a nil value)
---
It was fine yesterday night, and the library LibDogTag-2.0 is present in the folder. I'm running on a Mac with Leopard.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
UPDATE: Well, this gets stranger by the hour. The version I reverted to that I was having no problems with (56911), is now doing the exact same thing. ie, the entire WTF and Interface folders were reverted to the older version and it's doing it as well. This rules out Pitbull I suspect. And in fact I did some research and found 2 threads on the wow forums with people having the same issue:
http://forums.worldofwarcraft.com/thread.html;jsessionid=BC588154919364E98B165F1518DD95D5?topicId=3466366833&postId=34658749112&sid=1
and
http://forums.worldofwarcraft.com/thread.html;jsessionid=F5E7A369AA061CBE3F201AE4690F2A5C?topicId=3466368361&sid=1
I am completely at a loss. Reverting to known good backups of WTF and Interface folders that worked fine previously. Maybe it was the 2.3.3 patch and something in that.....but these above posts were made before 2.3.3.....so I dont know.......
I am having this exact same issue. I logged a JIRA on it (http://jira.wowace.com/browse/PB-159) but it doesn't appear to have been researched by the assignee. Although PB-77 describes a similar if not the same issue and it was resolved by updating the listener to something oRa2 specific.
Really wish this would get resolved as I prefer Pitbull over X-Perl. I would prefer not to have to run a hybrid configuration of the two simply to have my MT group displayed.
I have skipped over this issue when going through the Jira tickets for a few reasons - one, it's quite possibly user error (raid leader is not setting the MTs, or is using the wrong system - Blizz or oRA/CTRA); two, the linked screenshots in that ticket no longer exist, so I wasn't able to see exactly what the issue was. Can you provide screenshots or a better explanation of exactly what's happening?
Here is a link to my original posts in the forums.
http://www.wowace.com/forums/index.php?topic=8435.msg156901#msg156901
There are several messages in sequence that attempt to explain the issue.
Unfortunately, I didn't receive any troubleshooting feedback and the screenshots there, of course, are retired with the site that went down at the beginning of the year. It was after awaiting feedback that I decided to log it as a bug. As I stated in the JIRA, I will re-up the screenshots and provide valid links on my new server.
When you say "or is using the wrong system - Blizz or oRA/CTRA", are you stating that these are the "wrong systems"? It was my understanding that those three were compatible with PitBull.
My assumptions are that the Raid Leader is indeed setting the MT "properly" since the MT bar in X-Perl is loading with no apparent issues. I have also confirmed that he is using CTRA. The version of which, I'm not sure as of this posting but I can get that info and supplement the JIRA along with the updated screenshots.
*bump*
today I tried to replace the "border.tga" (inside the "PitBull/Aura" folder) with a better looking alternative. But nothing really changed. Reloading, restarting WoW, deleting the cache files and so on didn't help there's still the old "boring" border art.
I actually removed the border.tga from the Pitbull/Aura folder to test if wow starts complaining, but again... nothing happend - no errors, simply nothing.
I'm really confused. Any ideas?
Thanks in advance.
Missing textures don't generate errors. It's possible the texture isn't actually used for anything; look inside the Aura.lua file to figure out which texture is used.
I was using agunitframes with OmniCC and Im a warlock. As you can guess, I need that timers on my dots on target frame. They were working perfect with ag_unitframes but in Pitbull they are bugged. I tried enabling/disabling Aura options, set OmniCC scale to %0 but still some of them shows, some of them doesnt.
Is there a solution to this ? I really loved PitBull but I also need those timers, I dont wanna change the style I play the game.
As for DoT timers on the target frame, I'm not sure what exactly is wrong, since "they are bugged" is not descriptive at all, but in general you have many options:
1. Make sure that "cooldown spiral" is enabled for auras in PitBull. OmniCC does not work for (de)buff icons -- (de)buff times are not cooldowns. :P
2. Use Quartz to provide timers for your debuffs on your target.
3. Use a general buff mod that can be configured to show your target's debuffs.
4. Use a warlock DoT timer mod.
If #1 doesn't solve your problem and you don't want to use another addon, give more details about how exactly PitBull's display of your DoTs is "bugged".
Thank you for that, didn't know it :)
OmniCC does show a cooldown on DoTs on Target frames even they are not cooldows but they way it shows has eyecandy so I like em thats why I wanna use em. But If I can manage to increase the size for Pitbull's DoT timers without touching all font sizes of unitframes that would be ok also.
Already have Quartz installed and running well but as I told before, I wanna see them on my target debuffs, not like a countdown bar.
3. Use a general buff mod that can be configured to show your target's debuffs.
Have one "DotDotDot" but that has no difference from Quartz. Its also disabled.
All Working :
Immolate Now not working.
Small numbers are PitBull's original numbers. The big numbers belong to OmniCC.
Hope I explained my problem better this time.
I also use Xperl on my lock because I need the following.
1) Main Tank windows
2) MA targets
Xperl provides both while I play on my lock.
I cant get either to work in PB.
I tested MT windows in PB two seperate ways.
I created a group and assigned MT via oRA2 myself so I know it was done correctly.
I tried to get it working in a 25man raid setting where all other players could see MT windows but PB wasnt getting the info.
Raid leader was using CTRA (i think)
I'm sure it is probably some setting I need to change or some plugin i'm missing but I have no clue what that may be.
Hm, ok. Didn't know that missing textures don't generate errors.
I did a quick google search on the topic and other people are replacing the same file with success. Also, there's a line like.. eh..
"border_path = "\\border" in the lua
So I think border.tga should be the right file
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWell, that's what I did.
- exit wow
- replace border.tga
- restart wow
I tried several texture files without success. Some from people who told me that it worked for them.
Then I acutally changed the filename in the .lua. Still, nothing changed.
Is it possible that it has to do with some settings I missed? Currently I disabled the global aura settings (cooldown spiral, zoom textures)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI use blizzard SCT and damage text.
Here it is working like suppost to.
The issue:
and how it looks in configuration mode:
Anyone that could help me solve this issue?
Do you use Alt Aura?
If so, simply adjust the offsets of the respective buffs & debuffs as to place them where you'd like.
If not, you can always try using Alt Aura, disable the regular buff and debuff icons for Pitbull, and do the same thing with their (Alt Aura's) offsets.
It was fine yesterday night, and the library LibDogTag-2.0 is present in the folder. I'm running on a Mac with Leopard.