I've tried this before myself, but I don't like the large amount of space it puts in between the left and right sections, so I just put it all on the left, since it's usually the longest line in my CowTip anyway.
Anyone knows the line (left and right) so i can see who my target is targeting?
like, <Charname> is targeting <archimonde>
or, <Charname> is targetin <You>
Pls help.
Yeah I know. The thing is that there is no event triggered (as far as I know) when a skill level is updated, so I'm only refreshing it if you show the addon's interface. If I ever find a way to work around this, I'll fix it.
Thank you for writing this extremely useful addon. I used to have to keep track of most of the info it provides outside of WoW in spreadsheets, so Altoholic has saved me a ton of time.
I was wondering if you could add the level progress to the interface somehow? Like, instead of level 5, it could say 5.3, for example. The information already provided is very useful, but this would really help in knowing just how close an alt is to a given level (useful for crafting/purchasing items in advance, for instance).
I noticed that MobInfo2 cannot add its *runs* text to the tooltip with CowTip, so I wrote a little file you can add to your "LibDogTag-Unit-3.0\Categories" folder (along with a line in "LibDogTag-Unit-3.0\lib.xml") to enable using DogTags to display MobInfo2 data! Anyway, for those who want a pretty tooltip with *runs* text and the ability to completely customize the layout of that MobInfo2 data, this should work for you. Here's a few screenshots of it in action:
yes. both conditions are true. lol, all i wanted to suggest was that that message me made optional in conQuest... >.<
I just wanted to make sure you knew how it worked currently, so you could disable if you wanted to. I'll consider this for the advanced options interface for conQuest (I intend to have a simple and advanced view, to address both types of users, with simple being the default). Thanks.
no no, this is a different message. i have it set to MSBT and that part works fine "1/10 so and so found" but the exact message is "Found Sunblade Summoner for Crush the dawnblade, adding to quest tracker"
thats the message that shows up in frame one regardless of what i have the output set to
Ok, so you'll see that message when looting a quest item if the following conditions are true.
Condition #1: In the menu under "Quest", the option called "When looting quest item" under "Auto Show" is enabled.
Condition #2: The quest is not currently being watched in the minion. It is hidden from view.
Assuming those conditions are both true, the quest is added to the list of watched quests and it should then become visible. Along with this change, it is announced to the chat window that that quest is being added to the tracker as a watched quest.
So, you can either turn off that option or just realize that this is only going to happen if the quest isn't visible at the time. It shouldn't happen for every quest update, unless you are constantly rehiding the quest after it is made visible.
Sorry for not being more specific. This is the errors I get when checking bugsack right after entering wow.
[2008/04/30 19:33:44-1223-x1]: nQuestLog-1.0 r%d.71012\nQuestLogFormat.lua:34: Cannot find a library instance of "LibTourist-3.0".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
nQuestLog-1.0 r%d.71012\nQuestLogFormat.lua:34: in main chunk
---
[2008/04/30 19:33:44-1223-x1]: nQuestLog-1.0 r%d.71032\modules\Coloring\Coloring.lua:37: Cannot find a library instance of "LibTourist-3.0".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
nQuestLog-1.0 r%d.71032\modules\Coloring\Coloring.lua:37: in main chunk
---
[2008/04/30 19:33:44-1223-x1]: nQuestLog-1.0 r%d.71802\modules\Comments\Comments.lua:36: Cannot find a library instance of "LibAbacus-3.0".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
nQuestLog-1.0 r%d.71802\modules\Comments\Comments.lua:36: in main chunk
---
[2008/04/30 19:33:45-1223-x1]: nQuestLog-1.0 r%d.71802\modules\DetailsFrame\DetailsFrame.lua:36: Cannot find a library instance of "LibAbacus-3.0".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
nQuestLog-1.0 r%d.71802\modules\DetailsFrame\DetailsFrame.lua:36: in main chunk
---
Well, it's seems pretty obvious from the errors what the problem is here. You are using disembedded libraries as stated, yet you haven't enabled automatic dependency download in WAU or haven't manually downloaded the necessary libraries if you are running disembedded and not using WAU to keep track of dependencies. The lack of an instance of both the LibTourist-3.0 and LibAbacus-3.0 libraries is causing these errors, and that is likely the cause of the rest of the errors after those. You need to have each of those libraries in your Addons folder if you are running disembedded like most experienced users. If they are there, please make sure you have them enabled in your list of addons before logging in. Assuming both of those are true and you still have problems, please test with nQuestLog and libraries ONLY and see if that is still the case. Thanks.
would it be possible to add a Maximum Height to the minion options, or if there is already one there can you tell me how to enable it please.
Also is it possible to make the background and the border completely transparent, again if the option is there and i've somehow missed it, i apologise.
As for max height for the minion, that option is not available and I do not intend to add any more features to nQuestLog, but I'll consider that option for conQuest as I'm working on development toward that addon. You can make the background and border transparent by setting their alpha to 0 when setting the color for each of them in the Coloring module of nQuestLog.
[2008/04/27 11:57:15-2286-x2]: nQuestLog-1.0 r%d.71032\modules\Comments\Comments.lua:449: attempt to perform arithmetic on local 'level' (a nil value)
This should be fixed now. It would be interesting to know exactly what quest caused this, if you happen to know. Anyway, I added a nil check where the error was happening, so it shouldn't happen again. Thanks.
I got rid of Babble-Class-2.2, so only Babble-Zone-2.2 remains, since Tourist-2.0 uses it. When I get a chance, I'll get Tourist updated to LibTourist-3.0 and update to LibBabble-Zone-3.0.
FYI. I've now upgraded all libraries that I intend to upgrade (Abacus, Babble, Crayon, Sink, Tourist). I *might* upgrade Quixote-1.0 to Quixote-2.0 at some point (would require a LOT of code changes and testing), but I definitely won't be converting nQuestLog to Ace3.
Little request...
Would love the Close option or a little red X at the top to close the details frame. Many quests, you have to scroll down the window, and on a few occasions I have clicked on Abandon by accident. Of course I declined in the prompt, but Id find the close much more useful and non accidental on the top of the frame.
I can see that others may not want it on the top, so maybe make it an option to display on top or bottom?
Thanks for all the hard work. This is one quest mod that has make my entire WoW experience more enjoyable.
I could have sworn I changed the details frame several months ago so that you can click on the quest title and it will close the frame. So that should do it for you, rather than have an ugly X button there. :) I just built a new computer and am about to reinstall WoW, so I can't check and see if what I stated is true, but if it isn't, I'll go ahead and add that feature. Since the details frame itself is a Tablet-2.0 panel, I believe it would be very difficult to add any actual buttons.
Could someone update this addon to use LibBabble-3.0 instead of Babble-2.2, please?
I got rid of Babble-Class-2.2, so only Babble-Zone-2.2 remains, since Tourist-2.0 uses it. When I get a chance, I'll get Tourist updated to LibTourist-3.0 and update to LibBabble-Zone-3.0.
0
Left
Right
[Target:Name ? 'is targeting ' [(IsUnit('player', Target) ? 'You':Angle ! Target:NameRealm:Angle)]]I've tried this before myself, but I don't like the large amount of space it puts in between the left and right sections, so I just put it all on the left, since it's usually the longest line in my CowTip anyway.
0
I use the following:
[Outline][((IsEnemy & ~IsPet) ? DifficultyColor ! ClassColor) (NameRealm ' ' Status:Bracket:StatusColor ' ' (AFK | DND):Angle)] [Target:Name ? '>> ' [((Target:IsEnemy & Target:~IsPet) ? DifficultyColor ! ClassColor(unit=Target)) (IsUnit('player', Target) ? '<<You>>' ! Target:NameRealm)]]For what you want, this should work at a minimum without all the fancy formatting:
[NameRealm:Angle] [Target:Name ? ' is targeting ' [(IsUnit('player', Target) ? 'You':Angle ! Target:NameRealm:Angle)]]0
How about the SKILL_LINES_CHANGED event?
http://www.wowprogramming.com/docs/events/SKILL_LINES_CHANGED
http://www.wowace.com/forums/index.php?topic=9818.0
Armory uses this event in order to keep track of skill updates (check ArmorySkillFrame.lua).
0
I was wondering if you could add the level progress to the interface somehow? Like, instead of level 5, it could say 5.3, for example. The information already provided is very useful, but this would really help in knowing just how close an alt is to a given level (useful for crafting/purchasing items in advance, for instance).
0
Ok, I just e-mailed a request to ckknight. :)
0
http://i197.photobucket.com/albums/aa247/1337rx8/WoW%20UI/RegularCowTip.png
http://i197.photobucket.com/albums/aa247/1337rx8/WoW%20UI/AltCowTip.png
0
I just wanted to make sure you knew how it worked currently, so you could disable if you wanted to. I'll consider this for the advanced options interface for conQuest (I intend to have a simple and advanced view, to address both types of users, with simple being the default). Thanks.
0
Ok, so you'll see that message when looting a quest item if the following conditions are true.
Condition #1: In the menu under "Quest", the option called "When looting quest item" under "Auto Show" is enabled.
Condition #2: The quest is not currently being watched in the minion. It is hidden from view.
Assuming those conditions are both true, the quest is added to the list of watched quests and it should then become visible. Along with this change, it is announced to the chat window that that quest is being added to the tracker as a watched quest.
So, you can either turn off that option or just realize that this is only going to happen if the quest isn't visible at the time. It shouldn't happen for every quest update, unless you are constantly rehiding the quest after it is made visible.
0
Well, it's seems pretty obvious from the errors what the problem is here. You are using disembedded libraries as stated, yet you haven't enabled automatic dependency download in WAU or haven't manually downloaded the necessary libraries if you are running disembedded and not using WAU to keep track of dependencies. The lack of an instance of both the LibTourist-3.0 and LibAbacus-3.0 libraries is causing these errors, and that is likely the cause of the rest of the errors after those. You need to have each of those libraries in your Addons folder if you are running disembedded like most experienced users. If they are there, please make sure you have them enabled in your list of addons before logging in. Assuming both of those are true and you still have problems, please test with nQuestLog and libraries ONLY and see if that is still the case. Thanks.
0
As for max height for the minion, that option is not available and I do not intend to add any more features to nQuestLog, but I'll consider that option for conQuest as I'm working on development toward that addon. You can make the background and border transparent by setting their alpha to 0 when setting the color for each of them in the Coloring module of nQuestLog.
0
This should be fixed now. It would be interesting to know exactly what quest caused this, if you happen to know. Anyway, I added a nil check where the error was happening, so it shouldn't happen again. Thanks.
0
Fixed! Sorry about that. I should have tested nQuestLog by itself with embedded libs before making those changes.
0
FYI. I've now upgraded all libraries that I intend to upgrade (Abacus, Babble, Crayon, Sink, Tourist). I *might* upgrade Quixote-1.0 to Quixote-2.0 at some point (would require a LOT of code changes and testing), but I definitely won't be converting nQuestLog to Ace3.
0
I could have sworn I changed the details frame several months ago so that you can click on the quest title and it will close the frame. So that should do it for you, rather than have an ugly X button there. :) I just built a new computer and am about to reinstall WoW, so I can't check and see if what I stated is true, but if it isn't, I'll go ahead and add that feature. Since the details frame itself is a Tablet-2.0 panel, I believe it would be very difficult to add any actual buttons.
0
I got rid of Babble-Class-2.2, so only Babble-Zone-2.2 remains, since Tourist-2.0 uses it. When I get a chance, I'll get Tourist updated to LibTourist-3.0 and update to LibBabble-Zone-3.0.