Authors CurseForge

trying to import the nurfed layout, I am getting this:

Pitbull: Error importing layout:,[string "return Player Frame..."]:'<eof> expected near 'Frame'

this is very frustrating.

I am not a developer so my understanding of lua is practically nil. I have used the import facility, pasted the code for the player frame, clicked import.

I have also read the comment made regarding some dogtag problem, but since I am completely a noob I have no idea whatsoever what need modifying. If a new standard of dogtag is there, isnt it already supported by the latest version that I have downloaded. If this is the case there cannot be old incompatible dogtag strings there to cause problems.

If a knowledgeable person could put a step by step scenario on how to fix this, I would really appreciate it.

I have this problem, with bartender not letting me reapply a buff on my warrior is that buff is already present.

Any pointer please?

Prat blocked from using MultiBarBottomLeftButton1:Show()
Count: 36

Call Stack:
[C]: in function `Show'
Interface\FrameXML\ActionButton.lua:266: in function `ActionButton_ShowGrid'
Interface\FrameXML\ActionButton.lua:343: in function `ActionButton_OnEvent'
[string "*:OnEvent"]:1: in function <[string "*:OnEvent"]:1>
[C]: in function `EquipItemByName'
Interface\FrameXML\ChatFrame.lua:864: in function `?'
Interface\FrameXML\ChatFrame.lua:2990: in function <Interface\FrameXML\ChatFrame.lua:2957>
[C]: ?
[C]: in function `ChatEdit_ParseText'
Interface\FrameXML\ChatFrame.lua:2724: in function `ChatEdit_SendText'

Anyone has an idea on this?

Actually is there a way to ensure that the targetting bypass the cheap hunter pet exploit.

I have posted on this here and you said that is could be reported. I did and the GM stated that this was ok and not against the rules. So here we are against top team that use proximo too but with a difference, since if they have used the hunter pet naming exploit we cannot target their healer while their proximo works fine.

It would be nice if there was a way to use unique IDs in the targetting of proximo and have an option to show pets too.

This is for me currently a big show stopper until something is done (on blizzard or the mod community) to sort this out.

Quote from Shadowed »

/targetexact is still guessing, you cannot assume it's the exact mob you want still as there could be multiple of them with the same name, or in this case a pet with the same name as a player.

well it is seen as an exploit since the intention of the player is clear.

more on this here: http://forums.wow-europe.com/thread.html?topicId=2405613107&sid=1
and a blue post response backed up here; http://www.wowblues.com/us/petnaming-exploit-legal-3686704359.html

In any case I have reported 4 hunters so far and they have had the pet change enforced.

I will certainly be reporting every single hunter using this limitation of the UI to gain an advantage.

Meanwhile I can only hope that some new implementation is done on blizzard side to renders this crap useless.

PS; How sad this is that players forget all about sportsmanship and fair play and resort to these tactics to win. Are they the kind condoning the use of drugs and steroids in athletics and American football? So sad that people find it somehow justifiable to cheat in a game.

Quote from ugh »

There is no way to work around this with the UI, and I'll eat my metaphorical hat if anyone finds actual evidence of Blizzard saying this is an exploit.

PS: Look up the meaning of AWOL.

Edit: I just read the comments and somebody mentioned that it was messing with focus macros. If that is the case, I can see why Blizzard would take action. But it still strikes me as a "oh we need to fix our UI code" thing over a "oh we need to create a new policy" thing.

Sorry mate but in my part of the world awol means something has gone pear shaped (Absent Without Official Leave) and against conventional rule. I hope you see the imagery used.

I don't wish this thread to deviate into some lexicographical battle and would rather people put their brain power together to see if we can do something.

Quote from Grayhoof »

See here: http://www.wowinsider.com/2008/01/01/blizzard-cracks-down-on-arena-pet-naming-exploit/

And here: http://forums.worldofwarcraft.com/thread.html?topicId=3686704359&postId=36884333751&sid=1#14

wow link is deleted so no way to verify it.

The wowinsider one I knew about.

Quote from Grayhoof »

Report them is really the only option. Blizzard has said this is an exploit.

Proximo should still work for all the other members and for their health, you just may or may not be able to use clicks effectively on the frames depending on if the person with the name or his pet are closer to you.

I have looked everywhere and cannot find a blue post on the matter.

A certain pet exploit renders both these mods unuseable. Basically if a hunter name his pet the same as another player in his team
both mods stop working pitbull display the target unit of the pet or the other player.

Assist stops working
focus stops working
impossible to target with proximo
target of target stops working
target of anyone in your group stops working

Any way to go around this exploit and avoid having it break the UI?

Here is my take on this.

I like aguf because it seems smaller and It has really nice, ready to be used layouts. The problem is that it is lacking a built in, ready to use support for party targets. I do however like the Aura (buff debuff section) since it seems really crisp and has a timer for my dots which I can't seem to be able to activate in pitbull.

Pitbull: does lots and lots of things. It seems to cover everything but does not have built in layouts for those that do not want to get their hand dirty. The aura section seem less lisible compared to Aguf. My main concern is one of memory usage compared to Aguf.

Can anyone tell me how pitbull compares to aguf in terms of memory usage?
Is there any plan to implement readily available layouts like aguf?
Do you also feel that the aura section of pitbull is less crisp graphically than aguf's?

Lichdawg

Starting this thread where ideas can meet some gifted guys to implement them.

This is my idea for an implementation of a layout for Pitbull.

Minimalist Transparent Layout:

This layout is for the following frames:
player
player pet
target
target'target.

The player and target frame are both transparent. They do not show any bars. The only things showing are text in bold:
1-PlayerHealth percentage class color
2-PlayerMana percentage in blue

Same goes for the other frames above.
Each of the above frames have portraits not attached physically to the values 1 and 2 and the portraits can be moved independantly to their corresponding values 1 and 2.

I have tried with all the raid unitframes you mention. So far the only one stable is perl. All the others cause a lockup when joining a BG.

Anyone could help me get my pet bar buttons to not be draggable. All my bars are locked, all the buttons are locked, BUT the pet bar buttons refuse to stop being dragged by accident.

Anyone knows how to force the pet bar buttons to stay put?

Quote from Seerah »

@fred: Those bars you listed at the end of your list are the Blizzard defaults. You can set it up differently if you wish.

@psyquest:
1. unless this isn't applying to the pet bar for some reason, just lock the buttons on your bars (I think you can just click the Bartender icon to lock them)
2. get Omni Cooldown Count from wowinterface.com

Omnicc did the trick. but my pet bar buttons refuse to be locked in place. all buttons cannot bemoved accidentally, but the pet bar button which can be moved even when the rest of the bar buttons are locked.

Anyone has an idea on how to lock the pet bar buttons and stop them from accidentally being moved?

thanks for your help.

I have to issues I would love some help with:

-> How do I make my pet bar buttons to stick and not be able to be moved accidentally?
-> Is there a way to show the global cooldown on all buttons (much like blizzard animation) when I cast a spell?

Many thanks for your input.