Looting Problem

someone else who has had problems with the loot when you quest. it runs fine for a while but then you can not loot is already the body's loot

 

What? You need to word it more precisely and add some more detail.

 

Hey guys.. I have no idea, if the problem, dicksson is talking about, is the same as mine but here we go:
After a while using the questmode, the cursor, which usually turns gold if you move over a dead mob to show you, the mob is lootable, stays grey. also if I try manually to loot the mob nothing happens. No errors at all in wow but I have to log out completely and relog in to be able to loot the mobs.
The log just shows the following:

Code:

[21:18:48:433] interact: 0x11B8C0E0
[21:18:48:433] interact done: 0x11B8C0E0
[21:18:51:523] Cleared POI - Reason Waiting for loot flag
[21:18:51:523] Cleared POI
[21:18:51:997] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:18:52:278] interact: 0x11B8C0E0
[21:18:52:292] interact done: 0x11B8C0E0
[21:18:55:382] Cleared POI - Reason Waiting for loot flag
[21:18:55:382] Cleared POI
[21:18:55:854] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:18:55:972] Cleared POI - Reason Already looted
[21:18:55:972] Cleared POI
[21:18:56:88] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:18:56:205] Cleared POI - Reason Already looted
[21:18:56:205] Cleared POI
[21:18:56:321] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:18:56:437] Cleared POI - Reason Already looted
[21:18:56:437] Cleared POI
[21:18:56:553] [PoD] CheckPet timer has ended. Allow calling CheckPet now
[21:18:56:553] [PoD] Resetting checkpet timer - allow calls in at least 10 seconds.
[21:18:56:555] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:18:56:672] Cleared POI - Reason Already looted
[21:18:56:672] Cleared POI
[21:18:56:789] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:18:56:906] Cleared POI - Reason Already looted
[21:18:56:906] Cleared POI
[21:18:57:23] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:18:57:256] interact: 0x11B8C0E0
[21:18:57:270] interact done: 0x11B8C0E0
[21:19:00:393] Cleared POI - Reason Waiting for loot flag
[21:19:00:393] Cleared POI
[21:19:00:898] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:19:01:14] Cleared POI - Reason Already looted
[21:19:01:14] Cleared POI
[21:19:01:132] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:19:01:248] Cleared POI - Reason Already looted
[21:19:01:248] Cleared POI
[21:19:01:366] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:19:01:482] Cleared POI - Reason Already looted
[21:19:01:482] Cleared POI
[21:19:01:601] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:19:01:717] Cleared POI - Reason Already looted
[21:19:01:717] Cleared POI
[21:19:01:838] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:19:01:967] Cleared POI - Reason Already looted
[21:19:01:968] Cleared POI
[21:19:02:85] Changed POI to: Type: Loot, Name: Schreckenswirker
[21:19:02:201] Blacklisting lootable to avoid useless POI spam, tried looting twice but we still can't loot!
[21:19:02:201] Cleared POI - Reason Tried to loot more than 2 times
[21:19:02:201] Cleared POI
[21:19:02:320] Updating repair cost for current equipped items. New value: [0g36s15c]
[21:19:02:321] Changed POI to: Type: Train, Name: Darba the Crone
[21:19:02:499] Mounting: Schreckensross
[21:19:05:200] Moving to Type: Train, Name: Darba the Crone
[21:19:05:656] Successfully generated path from {2407.287, -5192.753, 73.37794} to {-4599.313, -1107.486, 504.9388} in 456 milliseconds
[21:19:05:792] [PoD] Player mounted fired
[21:19:05:887] [PoD] FelPuppy: Detected pet bar update. Reloading pet skills...
[21:19:05:887] [PoD] Successfully cast Schreckensross
[21:19:06:149] [PoD] Failed to cast Schreckensross
[21:19:07:742] Start/Stop button pressed.
[21:19:07:744] Stopping the bot!
[21:19:07:745] Stop called!

You see, that the log says he will not loot because the mob is already looted. THAT?s NOT TRUE So I have no idea, what is causing that behavior and while searching the forum it seems that nobody else has that problem... weird

I?ll try to get rid of it by disabling all addons and report back

 

same for me, with all profiles.
sometimes in a looting quest, the loots become unlootable but not only for bot, for me too! The cursor become grey and u can't click the mob for looting.
I try to post last log where i had this problem. I stopped the bot after this

 

[20:50:49:332] EnabledPlugins:
[20:50:49:332] Anti-Drown
[20:50:49:332] Refreshment Detection
[20:50:49:332] EquipMe
[20:50:49:332] Tidy Bags 3 Reloaded
[20:50:49:332] Mr.ItemRemover
[20:50:49:332] Talented
[20:50:49:332] Bug Submitter

maybe it's an issue with plugins, dunno

 

So we need only to wait someone that will check this problem for us


edit:

anyway it's some problem with the looting... sometimes it opens the loot window but don't loot anything :S

 

it's really unplayable guys...
i'm on the quest "Gathering some Grub(s)" from 1 hour :S
everytime i reload all, the bot loot 2-3 meats and he become bugged

 

is it stuck in the "looting" position? if so, it's a wow bug

if not, you'll have to wait for tony and the bot devs

 

is autoloot enabled (in game)?

 

nono it's not a problem of position.
the curson (that normally become a "yellow bag" when u stay on the lootable mob) become grey and u can't click the lootable corpse. u can't also if u stop the bot and try it with your hands :S


P.S.
sorry for my english

ofc m8
it worked until new hb

 

wow bug since vanilla. move away from corpse and wait for it to fix itself.

 

I had this problem, dont know what fixed it, but i removed some addons from wow as well as i cleared all WTF cashe ETC.

/reload ui is as well a quick fix that worked for me when i could not loot.

 

how can i delete the cache?

 

Inside your wow install folder tehre's 1 called cache. Delete

 

ok guys... I did everything one advised.... deleted cache, turned off ALL addons in wow etc pp... But Kick was right... I turned off Antidrown, Openthatstuff , Nobelgardener, Equipme and Bookcollector and it?s working since a while now.. so I guess it?s the antidrown or equipme... I?ll try to re enable one after another and we?ll see...

Edit: re-enabled all Plugins but deactivated "AcceptLogQuest", "BasicUseObject" and "UseGameObject2" from the kick-SVN seems to be one of them... Will let it run some more time and report back

Edit2: Seems to work! You have to remove them from the Quest Behaviors. But if you don?t know how to remove them, Pablito, you probably didn?t install them!?? If that?s true, I have no idea.. For me it works now!

 

hmmm idk how to deactivate these

edit: so it's a problem of the profiles?

 

I would still like to know the followup from this story.

If it's indeed the questbehaviours that is causing the lootbug (in my plugin part there's also a few peeps with issues).
If this is related to the altered questbehaviours, then I don't need to dig into this.
If not then I go on with my own investigation (if you can even call it since I still didn't manage to reproduce this).

So if Pablito and Milleniox could confirm this is solved by NOT using the questbehaviours from kick, I would be much obliged.

 

I don't use the custom questbehaviors anymore and since that time I never had that issue once again!!