This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Live
PTR
10.2.7
PTR
10.2.6
Beta
Wowhead AddOns (Client/Looter) Issue? Report here!
Post Reply
Return to board index
Post by
cjsharkie
I am having problems with my toys tab for my profile. It is only showing some of them and not all. I have updated my profile a couple times and uploaded my data as well. Is there something that I am missing?
Post by
Tumadre
After 8.3 dropped, I could no longer turn in quests. I had to make the lengthy trek of checking off addons 1 at a time. It only fixed after i turned off wowhead looter... thanks for that
Post by
charmead
Wow Classic, starting today after running wowhead client, I'm getting the following error when I loot anything. Something I killed or herbs.
1x +Wowhead_Looter\Wowhead_Looter.lua:2384: attempt to call upvalue 'IsPartyLFG' (a nil value)
+Wowhead_Looter\Wowhead_Looter.lua:2384: in function `?'
+Wowhead_Looter\Wowhead_Looter.lua:3776: in function <+Wowhead_Looter\Wowhead_Looter.lua:3774>
Locals:
self = wlFrame {
0 = <userdata>
}
_ = 0.885786
_ = 0.206072
mshome = 63
msworld = 64
now = 1579711058868
eventId = 2
fromFishing = false
guid = "Killing^Creature-0-4392-0-17-1125-00002878E4"
(*temporary) = <function> defined =:-1
(*temporary) = "WL_LOOT_COOLDOWN"
(*temporary) = "Killing^Creature-0-4392-0-17-1125-00002878E4"
(*temporary) = nil
(*temporary) = "attempt to call upvalue 'IsPartyLFG' (a nil value)"
wlId = "Suneagle^Westfall"
wlN = 4
GetNetStats = <function> defined =:-1
WL_PING_MAX = 300
wipe = <function> defined =:-1
wlLootedCurrenciesBlacklist = <table> {
}
IsFishingLoot = <function> defined =:-1
pairs = <function> defined =:-1
wlLootCooldown = <table> {
}
wlTracker = <table> {
spell = <table> {
}
rep = <table> {
}
quest = <table> {
}
}
wlSpells = <table> {
MindControl = <table> {
}
PickPocketing = <table> {
}
Skinning = <table> {
}
Mining = <table> {
}
Fishing = <table> {
}
HerbGathering = <table> {
}
Opening = <table> {
}
Disenchanting = <table> {
}
}
UnitName = <function> defined =:-1
UnitIsDead = <function> defined =:-1
UnitIsFriend = <function> defined =:-1
UnitIsPlayer = <function> defined =:-1
UnitPlayerControlled = <function> defined =:-1
wlTrackerClearedTime = 0
UnitGUID = <function> defined =:-1
SendAddonMessage = <function> defined =:-1
IsPartyLFG = nil
UnitFactionGroup = <function> defined =:-1
GetNumLootItems = <function> defined =:-1
GetLootSlotLink = <function> defined =:-1
GetLootSlotInfo = <function> defined =:-1
WL_CURRENCIES = <table> {
}
tinsert = <function> defined =:-1(##RESPBREAK##)258##DELIM##Sas148##DELIM##This will be fixed this week, make sure you're running the Client to get the latest updates when they're available. Thank you!
Post by
WHTJunior
After 8.3 dropped, I could no longer turn in quests. I had to make the lengthy trek of checking off addons 1 at a time. It only fixed after i turned off wowhead looter... thanks for that
This, combined with the "End of file" error in the uploader, means that I will be leaving the client off until they are both fixed.
Post by
Sas148
After 8.3 dropped, I could no longer turn in quests. I had to make the lengthy trek of checking off addons 1 at a time. It only fixed after i turned off wowhead looter... thanks for that
This, combined with the "End of file" error in the uploader, means that I will be leaving the client off until they are both fixed.
Do either of you have any error logs you can provide for us to look into it? All of us use the client/looter when we play and haven't encountered this quest turn in issue on 8.3.
Have both you of you made sure you've loaded the Wowhead Client, prior to launching the game, and received the latest updates to the client and looter?
Post by
tga123
After 8.3 receive errors at start.
1)
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:5578: hooksecurefunc(): PlaceAuctionBid is not a function
Count: 1
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:5578: hooksecurefunc(): PlaceAuctionBid is not a function
"]: ?
"]: in function `hooksecurefunc'
:5578: in function `wlHook'
:635: in function `?'
:4621: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4619>
2)
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:2613: attempt to index field 'spell' (a nil value)
Count: 27
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:2613: attempt to index field 'spell' (a nil value)
"]: ?
:2613: in function `?'
:4621: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4619>
Post by
PigeonD
After 8.3 receive errors at start.
1)
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:5578: hooksecurefunc(): PlaceAuctionBid is not a function
Count: 1
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:5578: hooksecurefunc(): PlaceAuctionBid is not a function
"]: ?
"]: in function `hooksecurefunc'
:5578: in function `wlHook'
:635: in function `?'
:4621: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4619>
This should be already fixed in the latest version of the addon. Please update the addon and see if you still have the error. Thanks!(##RESPBREAK##)
Post by
PigeonD
After 8.3 dropped, I could no longer turn in quests. I had to make the lengthy trek of checking off addons 1 at a time. It only fixed after i turned off wowhead looter... thanks for that
We've just pushed an update to the addon, could you try and see if that fixes the problem? Thanks!
Post by
WHTJunior
After 8.3 dropped, I could no longer turn in quests. I had to make the lengthy trek of checking off addons 1 at a time. It only fixed after i turned off wowhead looter... thanks for that
This, combined with the "End of file" error in the uploader, means that I will be leaving the client off until they are both fixed.
Do either of you have any error logs you can provide for us to look into it? All of us use the client/looter when we play and haven't encountered this quest turn in issue on 8.3.
Have both you of you made sure you've loaded the Wowhead Client, prior to launching the game, and received the latest updates to the client and looter?
I'll try to remember to re-enable the in-game looter, and try the client again when I get home. From memory, there is no error. It just prevents some quests from completing when clicking the Complete button. I know for sure that it happened on my Vulpera intro quest for both Vulpera that I created, where you go talk to the emissary guy, but would only complete once I disabled the looter. There were others, too, but that was the main one that I noticed.(##RESPBREAK##)258##DELIM##Sas148##DELIM##We were eventually able to replicate it on a different computer and patched it. Just make sure you have the latest update and let us know if you encounter it still. Thanks!
Post by
WHTJunior
After 8.3 dropped, I could no longer turn in quests. I had to make the lengthy trek of checking off addons 1 at a time. It only fixed after i turned off wowhead looter... thanks for that
This, combined with the "End of file" error in the uploader, means that I will be leaving the client off until they are both fixed.
Do either of you have any error logs you can provide for us to look into it? All of us use the client/looter when we play and haven't encountered this quest turn in issue on 8.3.
Have both you of you made sure you've loaded the Wowhead Client, prior to launching the game, and received the latest updates to the client and looter?
I'll try to remember to re-enable the in-game looter, and try the client again when I get home. From memory, there is no error. It just prevents some quests from completing when clicking the Complete button. I know for sure that it happened on my Vulpera intro quest for both Vulpera that I created, where you go talk to the emissary guy, but would only complete once I disabled the looter. There were others, too, but that was the main one that I noticed.
We were eventually able to replicate it on a different computer and patched it. Just make sure you have the latest update and let us know if you encounter it still. Thanks!
Looks like my desktop Wowhead Client and in-game Wowhead Looter are working with no unusual behaviors. Thanks!
Post by
Sponk
Anyone else experiencing delays when loading a character after applying patch 8.3?
Logging on to the games is ok, but when loading a character, the game freezes for 20 to 30 seconds after the progress bar reaches 100%.
I have tried deleting addons one by one, and the Wowhead looter seems to cause the problem - even when installed as the only addon.
Deleting all *wowhead_looter* files from the Addons/WTF folders and reinstalling Wowhead Looter does not help.
Post by
RockstarSuicide
Was randomly reading the archaeology guide and notice that a ton of items I know I completed haven't been imported to the site to show for any character. I've noticed at times mounts and pets may not be correct.
Is this something wrong on my end? I already update my characters data from Battle.net and use the WowHead client as an FYI for troubleshooting
Post by
Ramatar
I just thought I would let you know that Bitdefender Antivirus, after it was updated this week, rates Wowhead Client as a danger and auto-delete it from your system. It will not allow it to be added as an exclusion to the antivirus scans.
Post by
bjhinkel
WoWHead Looter Error on WoW Retail Only
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:5578: hooksecurefunc(): PlaceAuctionBid is not a function
Time: Thu Mar 5 13:46:08 2020
Count: 1
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:5578: hooksecurefunc(): PlaceAuctionBid is not a function
"]: in function `hooksecurefunc'
:5578: in function `wlHook'
:635: in function `?'
:4621: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4619>
Locals:
Post by
sinusoidplus
I saw a post on the retail forum dating back to 2009, stating that the wowhead uploader would randomly disappear from Windows.
This is still a thing. Windows Smartscreen prevents running the program by default, and after a day or two - it's gone from its residing folder.
Perhaps it would be an idea to fix your credentials - maybe even have a talk with MS about it, as I know the company I work for have similar issues with Windows default AV blocking runtime.
I would love to help update the database everyday, but it is getting harder to do so.
Best
/Beef
Post by
Dusklight
Been having some issues with the Wowhead Looter client when uploading data. It was working fine a month ago, but now when I hit Upload it gives me the error:
The Wowhead Client installs and maintains an addon called the Wowhead Looter, which collects data as you play the game. It also has stopped working.
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
Uninstalled the Client and deleted the Looter folders from the addon folders. Reinstalled it from the website, and still not working. Running Windows 7.
EDIT 1/22/2021 Okay so after like 6 months of not working, I uninstalled the client, reinstalled it, still wasn't working. Went to tools, cleared the file path for all the versions I had enabled (retail/classic/classic PTR), then had the client re-detect them, and I was able to upload again! I think something was wrong with my classic PTR file path so it kept giving me that error.
Post by
Allusya
Bag Scanner Tool not working correctly!
Meldung der Webseite: Wir konnten deine Taschenscan-Daten nicht lesen. Bitte folge den Anweisungen und versuche es erneut.
Export String is not complete
Please fix it
Thank you
Update
Thank you for fixing it! Now it works fine.
Post by
AllBuzzman
Need to update the Wowhead Client for WoW Classic.
## Interface: 11304
Should be 1130
5
Every time I edit the toc to fix, the client reverts the update.
Post by
Eglenn
The problem occurs with almost every addon publisher that they often forgets to update the .toc file. ;-)
Post by
cnorthfield2000
Client is unable to accept the PTR path as it produces an error that its invalid.
My PTR is located at: G:/World of Warcraft/_ptr_
This is the same drive where Classic & Live are located and no issue.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.