(49MB)

Updated: 12-25-22 01:22 PM

Add Favorite

Install Help

Pictures

File Info

Compatibility:	Dragonflight (10.0.2) Shadowlands patch (9.0.2) Visions of N'Zoth (8.3.0)
Updated:	12-25-22 01:22 PM
Created:	unknown
Downloads:	5,594,143
Favorites:	7,690
MD5:

LightHeaded

Version: v100002-1.0.0-2022-12-15

by: Cladhaire [More]

Classic not updated at the moment, only retail.

LightHeaded is a very simple addon that displays quest information and comments from http://www.wowhead.com in game, eliminating the need to Alt-Tab when you get stuck on quest. This addon was inspired by qcomments and wowhead_quests, which both serve a similar purpose. Data is only loaded when you first request it, so you can be sure you're not using more memory than you need to.

I HIGHLY suggest using this addon with TomTom, another one of my addons (http://www.wowinterface.com/download...32-TomTom.html ). This allows you to simply click any coordinate in LightHeaded to add it to your map as a waypoint.

The following slash commands are valid:

/lh attach - Attaches the frame to the quest log
/lh detach - Detaches the frame, allows you to resize and move it
/lh sound - Toggles the open/close sound
/lh page - Toggles showing all comments on one page, or with multiple pages
/lh bgalpha <0.0-1.0> - Changes the alpha of the LH window background textures, so you can see the world.
/lh debug - Enables or disabled debug messages when loading quest databases
/lh config - Opens the LightHeaded configuration window
/lh autodetails - Toggle automatic opening of the Lightheaded window when clicking a quest in the objective tracker

LightHeaded now includes the English descriptions and introductory text for most of the quests in the game. This is disabled by default, but can be enabled for those players that are not playing in their native locale.

LightHeaded supports sending coordinates to TomTom, MapNotes, Cartographer2 and Cartographer3.

IMPORTANT: Addon authors that wish to use this API and data should
include the wowhead logo in the frame that displays this information.
They are kind enough to let me continue parsing their database, and we
owe them at least that much. Thank you.

Thanks for using my addons!

Updated 2022-12-15 for retail.

Beta Files (7)

File Name	Version	Hits	Size	Author	Date
beta_LightHeaded-v30401-1.1.0-2022-12-15.zip	v30401-1.1.0-2022-12-15	0	32MB	Cladhaire	02-04-23 03:41 AM
beta_LightHeaded-v11302-1.0.0-2020-05-01.zip	v11302-1.0.0-2020-05-01	591	10MB	Cladhaire	05-05-20 11:47 AM
beta_LightHeaded-v11302-1.1.0.zip	v11302-1.1.0	1,322	10MB	Cladhaire	10-04-19 11:26 AM
beta_LightHeaded-v11302-1.0.0.zip	v11302-1.0.0	1,464	10MB	Cladhaire	09-05-19 12:16 AM
beta_LightHeaded-v70100-1.1.0-2016-12-29.zip	v70100-1.1.0-2016-12-29	299	30MB	Cladhaire	01-12-17 02:27 PM
beta_LightHeaded-v70000-1.0.0-beta.zip	v70000-1.0.0-beta	307	27MB	Cladhaire	09-05-16 07:11 AM
beta_LightHeaded-v60000-0.1.0.zip	v60000-0.1.0	1,012	22MB	Cladhaire	10-20-14 02:50 PM

Comment Options

Page 124 of 255

124

11-18-08, 07:06 AM

lewal

A Kobold Labourer

Forum posts: 0

File comments: 153

Uploads: 0

Originally posted by Cladhaire
The message is just there to inform you that using those two addons together can severely impact the performance on your machine. There is absolutely nothing I can do to fix this issue, it's Armory that is doing improper things. If you don't experience the problem.. then you can leave them both running. However, it does indicate a real problem.

ok so you know what it is doing have you ever left a post to the author of that addon,, i left him the same post as yours,, this never poped up before wierd.....im just wondering if he is aware that there is a problem

11-18-08, 07:03 AM

Cladhaire

Salad!

Forum posts: 1935

File comments: 4940

Uploads: 19

Originally posted by lewal
your mod just pop up a funny window saying it was having a conflict with another mod called armory that i run and to contact the author of that mod??

seems to me it is your mod that picked up the issue but im letting both of you know

The message is just there to inform you that using those two addons together can severely impact the performance on your machine. There is absolutely nothing I can do to fix this issue, it's Armory that is doing improper things. If you don't experience the problem.. then you can leave them both running. However, it does indicate a real problem.

__________________
"There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..."

11-18-08, 07:00 AM
lewal A Kobold Labourer Forum posts: 0 File comments: 153 Uploads: 0	your mod just pop up a funny window saying it was having a conflict with another mod called armory that i run and to contact the author of that mod?? seems to me it is your mod that picked up the issue but im letting both of you know

11-18-08, 03:08 AM

Cladhaire

Salad!

Forum posts: 1935

File comments: 4940

Uploads: 19

Originally posted by pär
Just wanted to say thanks. I run a 2nd monitor for this kind of stuff, but LightHeaded still helps. A lot.

Glad to hear that you find it useful!

11-17-08, 11:59 PM
pär A Murloc Raider Forum posts: 6 File comments: 87 Uploads: 0	Just wanted to say thanks. I run a 2nd monitor for this kind of stuff, but LightHeaded still helps. A lot.

11-17-08, 11:40 PM

Cladhaire

Salad!

Forum posts: 1935

File comments: 4940

Uploads: 19

Originally posted by Allara
New version actually seems to trigger the warning more frequently now. It doesn't seem to like QuestGuru, but all I'm doing is opening the quest log when the warning strikes. Pretty sure QuestGuru just uses Quixote. And I don't have anything collapsed in the log. Hmm. Wonder if we could have an option to turn the warning off...? Ah, heuristics.

Edit: No, it doesn't seem to use Quixote.

Edit2: Now you're warning about my add-on, QuestAgent. I am certainly not doing any timed log reads other than once at the end of a throttled read. I abandoned a quest and LH warned me. QuestAgent doesn't even do any tricks with collapsed headers, I fail to see what the problem is here. You are aware that a lot of times WoW will send 5-10 QUEST_LOG_UPDATE events all at once when just one thing changes, right? There's nothing I can do about that, but I throttle myself so I only respond to one per 3 seconds at maximum.

I will have to look at it. The warning will only happen once per session at the moment. If you can give me specific steps for how you are reproducing this, I would appreciate it.

Originally posted by miakeru
I know that this has probably already been suggested, but there's so many pages of comments and there's no good search tool, so I'll just post it again. Forgive me if it's already been mentioned, a lot.

Is there some way to maybe get LightHeaded to do some sort of auto-update where it fetches quest-related information when you load it up in your quest log? This would prevent you from having to do batch updates every so often so that we can get the latest comments, coords, whatever, that are appearing in Wowhead. I'm not sure about the number of API calls that this would create and whether it's actually feasible with what Wowhead is letting you do, but I figured I'd ask.

What you are asking for is not possible via the WoW API. An addon cannot communicate in any way with data sources that aren't loaded prior to the game being launched.

If that's not possible, have you thought about setting up some web space with a web hosting company to use that as a sort of caching location where you could set up a script to auto-execute (crontab, anyone?) and download the information that you push out to the addon whenever you update the comments? You could then maybe develop some sort of front-end to LightHeaded that we can run on our computers hourly (or less) to have it fetch the updated comments and other information from your web space and then to our computers.

I'm not interested in doing this. The parsing process is EXTREMELY expensive and really can't be done in a better way than its already being done. I update the database in batch and push out updates in a timely manner. By tagging the addon as a favorite you can be notified that there has been an update, with a direct link to the file to be downloaded.[quote]

Hosting that data externally might not be something Wowhead likes but it would potentially solve the API calls issue and would hopefully be something that you could work in to a release.

I'm very happy with this addon so far and appreciate all of the work that you've done for it. You've done a fantastic job and it's one of my favorites, by far! Keep up the good work and thanks again!

It's more than that, unfortunately. The problem is a bit more complex than it might appear on the surface and the arrangement I have currently is probably the best you would see without a database site creating an addon of their own and providing incremental updates for it.

Hope that makes sense.

11-17-08, 09:19 PM
miakeru A Kobold Labourer Forum posts: 0 File comments: 1 Uploads: 0	Auto-update? I know that this has probably already been suggested, but there's so many pages of comments and there's no good search tool, so I'll just post it again. Forgive me if it's already been mentioned, a lot. Is there some way to maybe get LightHeaded to do some sort of auto-update where it fetches quest-related information when you load it up in your quest log? This would prevent you from having to do batch updates every so often so that we can get the latest comments, coords, whatever, that are appearing in Wowhead. I'm not sure about the number of API calls that this would create and whether it's actually feasible with what Wowhead is letting you do, but I figured I'd ask. If that's not possible, have you thought about setting up some web space with a web hosting company to use that as a sort of caching location where you could set up a script to auto-execute (crontab, anyone?) and download the information that you push out to the addon whenever you update the comments? You could then maybe develop some sort of front-end to LightHeaded that we can run on our computers hourly (or less) to have it fetch the updated comments and other information from your web space and then to our computers. Hosting that data externally might not be something Wowhead likes but it would potentially solve the API calls issue and would hopefully be something that you could work in to a release. I'm very happy with this addon so far and appreciate all of the work that you've done for it. You've done a fantastic job and it's one of my favorites, by far! Keep up the good work and thanks again!

11-17-08, 06:54 PM
Allara A Kobold Labourer Forum posts: 1 File comments: 123 Uploads: 1	New version actually seems to trigger the warning more frequently now. It doesn't seem to like QuestGuru, but all I'm doing is opening the quest log when the warning strikes. Pretty sure QuestGuru just uses Quixote. And I don't have anything collapsed in the log. Hmm. Wonder if we could have an option to turn the warning off...? Ah, heuristics. Edit: No, it doesn't seem to use Quixote. Edit2: Now you're warning about my add-on, QuestAgent. I am certainly not doing any timed log reads other than once at the end of a throttled read. I abandoned a quest and LH warned me. QuestAgent doesn't even do any tricks with collapsed headers, I fail to see what the problem is here. You are aware that a lot of times WoW will send 5-10 QUEST_LOG_UPDATE events all at once when just one thing changes, right? There's nothing I can do about that, but I throttle myself so I only respond to one per 3 seconds at maximum. Last edited by Allara : 11-17-08 at 07:02 PM.

11-17-08, 03:40 PM
Cladhaire Salad! Forum posts: 1935 File comments: 4940 Uploads: 19	The "issue" is the same one that cause people's pages to flip back to the first page, meaning they never get to read anything. I've "solved" that for those users, but the underlying problem is essentially the following: Some addons (Armory being the notable culprit at the moment) repeatedly scan the quest log on a timed basis (instead of responding to events like they are supposed to). The reason they do it this way is because the user can collapse the quest headers, and the only way to get at those via the API is to EXPAND the headers, get the data you want, and then re-collapse them quickly. This causes QUEST_LOG_UPDATE to fire, which means these addons can't rely on that event. I consider this a fundamental flaw in their addons, but have to do something so things are still useful to my users. I can't think of a viable heuristic for determining whether an update should be ignored or not.. since we can never know if there is going to be another call after the one we're currently processing. Either way, the new version is posted with new quest data, comments, npc locations and hopefully a bit less intrusive warning. Please let me know if you have any feedback or suggestions. __________________ "There's only one thing that I know how to do well and I've often been told that you only can do what you know how to do well, and that's be you-- be what you're like-- be like yourself. And so I'm having a wonderful time, but I'd rather be whistling in the dark..."

11-17-08, 03:09 PM
Allara A Kobold Labourer Forum posts: 1 File comments: 123 Uploads: 1	Clad, you've probably thought of this: If the performance issues are resulting from LH re-selecting the quest every time the API is called, and some add-on is calling the API on a rapid timer, have you tried adding a throttle to LH so it just won't select a quest faster than a certain amount (say, once per 1-2 seconds)? If your selection function gets called within the throttle, just schedule a select for after the throttle expires, so the user might perceive a slight delay if they click several quests really fast, but it could alleviate some of the processing. Or perhaps I'm misunderstanding the issue.

11-17-08, 02:35 PM
Zidomo A Cliff Giant Forum posts: 76 File comments: 1046 Uploads: 0	Yes, the fact it seems to throw the error even when no other quest mods/mods are active explains what I have been experiencing. As well, out of all other quest mods tried with this, it only reported the name of one. Every other time the report came up, the mod name was not shown in the popup box ("LightHeaded has detected an addon conflict. The following addons may have a severe impact on the performance of your client in combination with LightHeaded; it is suggest that you disable these addons or contact the authors for a fix: \|cffff1111%s\|r") The only time the name of the "conflicting" mod appeared in the text was with bEQL (latest r184). Also tried the following mods/mod combos alone with Lightheaded. None of them appeared in the conflict message; after the colon, it was blank: --QuestGuru (v0.9.5) --DoubleWide (v0.7-30000) + BetterQuest --DoubleWide + SmoothQuest None of them had "performance issues" on the client here. Either when used with r259 of Lightheaded now or with earlier versions of it with the message not present (in previous weeks). (WoW 3.0.3 (WotLK installed), USEng client/server).

11-17-08, 01:09 PM

Cladhaire

Salad!

Forum posts: 1935

File comments: 4940

Uploads: 19

Originally posted by Balsta
ok this is kinda funny. I did some research trying to find the conflicting mods. Monkeyquest and its libs are defiantly one conflict. I dropped that mod out the errors went away but i was still getting the addon conflict dialog from LH. So I started removing mods trying to find the conflict. Any guess as to what I found?

LH was causing the dialog to pop on its very own. lol I was getting the pop up with no other mods turned on at all. So there must be a flaw in the detection. Now to reproduce this I did have to open LH click a few quests then close the log. I would then reopen the log click a quest and bingo pop up.

Hope this helps. Let me know if I can do anything else.

There is a flaw in the detection and I'm hoping to improve it. You can reproduce it right now by opening the quest log 10 times without having QUEST_LOG_UPDATE fire. I hope to have an "improved" version posted relatively soon, but I'm still working out some of the kinks with it. The criteria to actually trigger it will be pretty high.. so it won't provide much use to those people who are actually experiencing the performance issues that it's meant to detect.

It's a tough problem either way you look at it.

11-17-08, 01:06 PM
Balsta Guest Join Date: Not Yet Forum posts: 0 File comments: 0 Uploads: 0	ok this is kinda funny. I did some research trying to find the conflicting mods. Monkeyquest and its libs are defiantly one conflict. I dropped that mod out the errors went away but i was still getting the addon conflict dialog from LH. So I started removing mods trying to find the conflict. Any guess as to what I found? LH was causing the dialog to pop on its very own. lol I was getting the pop up with no other mods turned on at all. So there must be a flaw in the detection. Now to reproduce this I did have to open LH click a few quests then close the log. I would then reopen the log click a quest and bingo pop up. Hope this helps. Let me know if I can do anything else.

11-17-08, 12:07 PM

Balsta

Guest

Join Date: Not Yet

Forum posts: 0

File comments: 0

Uploads: 0

Originally posted by Cladhaire
I do not understand why this is happening. There is clearly some conflict with another addon that I'd like you to try and figure out for me. Would you please do some more troubleshooting using the procedure I've outlined in the forums post?

KK will see what I can find

11-16-08, 05:46 PM

Cladhaire

Salad!

Forum posts: 1935

File comments: 4940

Uploads: 19

Originally posted by Aesir
In my defense, the top entries for the changelog (typically, the most recent comments) are now using some method of ordering that I'm not familiar with.

Thanks for the quick response.

[/b]

Aye, not sure how I screwed em up, sorry about that!

Page 124 of 255

124

Some folks have asked for how they can donate money, and for many years I've enjoyed hearing about how my addons have helped other people enjoy World of Warcraft. If you would like to donate, I'd ask you to make a donation to the Colorectal Cancer Alliance, a worthy organisation that helped my sister immensely from her diagnosis through her final years. If you or a family member suspect you might have something not right in your butt, please have a doctor check it out. Colorectal cancer is one of the most preventable cancers in the world.

Report this File

Category Jump: