Grind Bot Randomly Going AFK - Log Included
- Thread starter Mydruid
- Start date
CodenameG
New Member
- Joined
- Jan 15, 2010
- Messages
- 38,364
- Reaction score
- 231
in wow, while in game click go into your Game Menu and Key Bindings in that menu, click the Reset to Default then press ok.
ive seen cases before while the anti-afk quits working an this has worked before, give it a shot.
ive seen cases before while the anti-afk quits working an this has worked before, give it a shot.
Sorry I think I didn't explain properly. When I say afk I mean it just stops doing anything. It just sits there as if it had gone afk. No movements, no actions, nothing at all. You can see it in the log if you scroll down I have marked it out.
Edit: Here is the log from just before and after the event.
Edit: Here is the log from just before and after the event.
Code:
[07:57:24.931 D] Activity: Loading Tile/s
[07:57:24.931 D] Loading HawaiiMainLand_30_31
[07:57:25.025 D] Loading HawaiiMainLand_30_32
[07:57:25.116 D] Loading HawaiiMainLand_31_32
[07:57:25.182 D] Loading HawaiiMainLand_31_31
[07:57:25.252 D] Updating repair cost for current equipped items. New value: [14g81s96c]
[07:57:25.262 D] Activity: Moving to hotspot
[07:57:33.969 D] Changed POI to:Type: Harvest
[07:57:34.274 N] Moving to Type: Harvest
[07:57:40.189 D] InteractDebug:273390720
[07:57:40.261 D] Interact Done:273390720
[07:57:40.337 D] [Lua.Events] Attached to event LOOT_OPENED with handler
[07:57:44.122 N] Looting Ghost Iron Deposit Guid:0xF513319F000BA24E
[07:57:44.122 V] Blacklisting F513319F000BA24E for 00:15:00 [Type: Node]
[07:57:44.351 D] Cleared POI - Reason Waiting for loot flag
[07:57:44.351 D] Cleared POI
[07:57:46.087 D] [CGSpellBook::CastSpell] Override ID: 470, KnownIndex: -1
nothing for 1 minute, then i manually moved into combat
[07:58:53.049 V] Blacklisting F513319F000B4DD8 for 3.00:00:00 [Type: All]
[07:58:54.241 D] Dismount for attacker.
[07:58:54.242 D] Stop and dismount... Reason: Combat
Last edited:
I suspect it is a mesh issue. After watching the log with diagnostic on I noticed this after it stopped moving.
I suspect this is the case for all. This was with a fresh install and fresh mesh downloads.
Code:
Could not generate full path from {917.3956, -1897.169, 54.83297} to {902.2857, -1910.153, 57.827} (time used: 0 milliseconds)I suspect this is the case for all. This was with a fresh install and fresh mesh downloads.
Tony
"The Bee"
- Joined
- Jan 15, 2010
- Messages
- 128,830
- Reaction score
- 571
Ah my apologies this was not in that log. I had assumed because I did not set the log to diagnostic it didn't record?
Anyway after testing with others bots it turns out the problem wasn't exactly the same. In that particular instance once I removed hotspots where the path couldn't be generated it worked fine.
In the other instance, my original post, where the bot just stops moving and nothing happens I set a new mesh folder so it would download new mesh. Now I don't know if my old mesh was the problem or not but since then the problem seems to have gone. I suspect it might also be some plugins that could be causing issues. I will do some more testing.
Anyway after testing with others bots it turns out the problem wasn't exactly the same. In that particular instance once I removed hotspots where the path couldn't be generated it worked fine.
In the other instance, my original post, where the bot just stops moving and nothing happens I set a new mesh folder so it would download new mesh. Now I don't know if my old mesh was the problem or not but since then the problem seems to have gone. I suspect it might also be some plugins that could be causing issues. I will do some more testing.