Authors CurseForge

I hope a feature request is acceptable here: I would love to see a tag to show how many charges of a buff (like Lifebloom) are on a unit. Thanks!

... you can already do that with the current version of DogTag. [NumAura(Lifebloom)]

Excellent, thanks!

I've been searching this page

http://www.wowace.com/wiki/DogTag-2.0/Tags

for tags to use. Apparently it doesn't contain all of them. Where should I be looking instead?

I'm not sure if this should be part of DogTag itself, some helper addon or Pitbull.

Problem: When I use Pitbull I use the same DogTag string for all the special targets frame (partytarget, focustargetm, targettarget, ...) but it is hassle to change it, because I have to go through all the frame configurations and copy-paste it many times.

The idea: Can we create our custom DogTags in some DogTag editor and use it in the game instead of the full string? When the change is made to the custom DogTag all the DogTags using it would automatically update as well...

Example: Define: [CustomColoredName] = [IsPlayer & IsFriend ? Name:ClassColor ! Name:HostileColor] and then we can use [CustomColoredName] in all the DogTag enabled addons (CowTip, Pitbull, ...) like one of the predefined DogTags.

Quote from zarevak »

Example: Define: [CustomColoredName] = [IsPlayer & IsFriend ? Name:ClassColor ! Name:HostileColor] and then we can use [CustomColoredName] in all the DogTag enabled addons (CowTip, Pitbull, ...) like one of the predefined DogTags.

Sounds useful. I think. Not sure. :)

I'd love the ability to define custom tags. I use the same name coloring tag for all unit frames in PitBull -- players by class, mobs by hostility, and pets by creature type that usually maps to owner class (i.e. beasts get the hunter color, demons get the warlock color) -- and it would be nice to define that as [ColoredName] and then just use that instead of the full sequence on all the unit frames. I imagine it would be even more helpful for people using more than one DogTag addon.

Also, a tag that generated a color based on a pet's owner's class would be nice.

errr spend all day on PTR trying to find out how to convert some of the tags I have on live :(

For the easy one, no problems, but for some others no way :( and a big headache, so little question : will Dogtag2 continue or not ?

What also can we use now to replace [Name:TruncEllipsis(22):ClassColor] [DruidForm:Trunc(1):Color(dda0dd):Angle] [IsPlayer ? Guild:TruncEllipsis(10):Angle]",

I post here the one I tried to convert :

[~IsPet ? Level:Hide(??):DifficultyColor ! Level][~IsPlayerOrPet ? Classification:Contains(Rare) ? Text(R):Gray][~IsPlayerOrPet ? Classification:Contains(Elite) ? Text(E):Yellow][~IsPlayerOrPet ? [Classification = Text(Boss)] ? Text(Boss):Red][IsPlayer ? SmartClass:ClassColor] [~IsPlayerOrPet ? CreatureType:Hide(Unknown)] [IsPet ? Guild] [IsPlayerOrPet ? [ [Faction = Text(Alliance)] ? [PvP ? Text(A):Blue ! Text(A):Green] ! [ [Faction = Text(Horde)] ? [PvP ? [PvP#player ? Text(H):Red ! Text(H):Yellow] ! Text(H):Green] ] ] ]

I use it on my frame target and it was really good for me, so ohh please could you help me on that one ?

Beside that two error popped on PTR while trying to adapt the new dogtag to Pitbull for 2.4 - Changelog-PitBull-r65512.txt
I was trying to get the above tag working and also the Cast bar and Cast time tag working as using the ones included with Pitbull dont work at least on ptr.
It does not work actually as on live.
if i target myself, nothing appear on the castbar of my Player frame.
Though on the TOT frame, I can see the name of the spell and a gazillon of numbers for the duration.
on PTR version for 2.4 Changelog-PitBull-r65512.txt
on PTR Changelog-PitBull-r65339.txt

[2008/03/24 01:35:01-954-x6]: PitBull-r65427\PitBull_MetaLayout.lua:2159: attempt to call method 'OpenHelp' (a nil value)

[2008/03/24 01:42:14-954-x2]: LibDogTag-3.0\LibDogTag-3.0.lua:296: assertion failed!

 ---

Thank you

-

About the cast and castime dogtags in the new version, any idea why they are not working on player frame cast bar, Target frame cast bar and working on the TOT (at least semi working as the time casting is really strange).
Actually as the version 65339 works perfectly on PTR, I just adapt all the changes you are doing, BUT the dogtags -I keep old version-, until this will work totally.
Even using the integrated ones dont work.

[Alpha((CastStopDuration or 0) + 1) CastStopMessage or (CastName " " CastTarget:Paren)]

[if not CastStopDuration then Concatenate("+", CastDelay:Round(1):Hide(0)):Red " " (CastEndDuration >= 0):Format("%.1f")]

Just curious...why were new symbols invented to mean logical operands?

There are syntax symbols out there already, and not that I know squat about LUA (so please don't be offended), but there are logical operands in symbolic forms:

&& AND
|| OR
! NOT
~ NEGATE
...
etc, etc

Is it necessary to reinvent the wheel? I'd rather have a manual that explains the symbols, but would still be nice to know that these symbols follow a somewhat standard notation...

I know you are working hard for us and as progammer of this adddon you have the right to do what you want, but .... why on patch day insist to put on a new system, that is not fully working and will give you a lot more work.

The Tag change could have been done later, when the patch rush would have been a little behind, and give us plenty of time to learn and test out you change.

		{
			["message"] = "PitBull-r65512\\PitBull_MetaLayout.lua:2596: attempt to call method 'OpenHelp' (a nil value)\n\n ---",
			["type"] = "error",
			["time"] = "2008/03/25 17:02:25",
			["session"] = 1027,
			["counter"] = 1,
		}, -- [181]

and Cast time and Cast Dodtags are not working.

The ShortClassification tag does not seem to be working in LDT-3.0. Is this intended, or was it changed to some other notation? I did a quick search and didn't find anything.

If you just want to give a response along the lines of "Not all tags are implemented, list of LDT-3.0 tags coming soon", that's fine too. =)

Quote from ckknight »

Because DogTag-2.0 doesn't work right on 2.4 and I don't want to support multiple systems at one time. I didn't have adequate time to work on LDT-3.0 before WoW 2.4 came out, I plan to get things like the ingame documentation working properly as soon as possible.

Also: I don't have faith in people to "learn and test out", since that didn't happen at all it seems when I had it up and running for PTR testers.

Well I dont know what is not working with the DogTag-2.0, but actually this is working perfectly. I had no error while testing them on PTR, and I have actually no error either on live. And even if this is not as perfect as you wish, actually the DogTag-3.0 is popping so much errors that I went back to my working version.

Also its not the help implementation that will answer question like why cast and cast timer are not working or Player cast bar, and Target cast bar ? and why a gazillon of numbers are on the TOT cast bar now ?

Dog Tags were much easier and more functional before. Now, they're needlessly muddled. The problem I'm having right now is in regards to three separate general topics:
1) Color(xxxxxx) does not appear to be working as a tag.
2) I cannot modify the unit designation of a tag with #unitname
3) I cannot seem to find a way to nest "if, then" statements

More specifically, if I could figure out how to get this sequence working, I'd be able to figure out everything I need to know in the new patch, excluding how to modify a tag to a specific unit:

[IsMana ? [~IsMaxMP ? CurMP:Color(9BDDFF)] ][IsRage ? [CurMP:HideZero:Color(DC143C)] ][IsEnergy ? [~IsMaxMP ? CurMP:Color(DFFF00)] ][IsFocus ? [~IsMaxMP ? CurMP:Color(DFFF00)] ]

or (as far as I've worked it so far):

[if IsMana then [if not IsMaxMP then CurMP:Color(9BDDFF)] ][if IsRage then [CurMP:Hide(0):Color(DC143C)] ][if IsEnergy then [if not IsMaxMP then CurMP:Color(DFFF00)] ][if IsFocus then [if not IsMaxMP then CurMP:Color(DFFF00)] ]

The idea is to display the power type with proper colors and in the proper condition. Worked perfectly fine pre-patch.

You obviously didn't read any of this thread. As previously mentioned, all three of the things you're asking about have changed in the new version of DogTag.

1. Color tags now require quotes around their arguments, e.g. Color("DFFF00")
2. Units are now specified with named aruments, e.g. Name(unit="target")
3. Nesting can be done using [], (), or {} as desired.

Thank you.

Issues I'm having at the moment with 2.4:

The status tag is breaking in raid. While in a raid group if *anybody* is offline it shows myself as offline too... [Edit: Ok this one isn't as consistent as I first thought, its just frequently triggering myself as offline if someone else goes offline it seems. Its currently not indicating me as offline however, despite other raid members being offline. Will try to narrow it down.]

In CowTip using HostileColor breaks while mousing over dead units, or units tapped by someone other than myself.

Are there equivalents for ShortClass and AFKTime?

WTB tag list, pst

Quote from krage »

Issues I'm having at the moment with 2.4:

The status tag is breaking in raid. While in a raid group if *anybody* is offline it shows myself as offline too... [Edit: Ok this one isn't as consistent as I first thought, its just frequently triggering myself as offline if someone else goes offline it seems. Its currently not indicating me as offline however, despite other raid members being offline. Will try to narrow it down.]

In CowTip using HostileColor breaks while mousing over dead units, or units tapped by someone other than myself.

Are there equivalents for ShortClass and AFKTime?

WTB tag list, pst