What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Issues with Questing

S

Scrubbish

New Member
Joined
Feb 26, 2012
Messages
167
Reaction score
1
OK so I have been using Kick's 1-90 profile pack all day or attempting to. I started out this morning running my new druid on my laptop, after about 2-3 hours it stopped attacking, even when being attacked, it would just stand there and heal until i took over and started attacking, then it would sometimes finish combat and move on to the next hot spot and just stand there again. I deleted the cache in HB and WoW, rebooted the machine, no change. I switched it over to running on my desktop for a bit, it worked for 2-3 hours, then the same problem started occurring. I repeated the process of deleting caches, and same result.Log Attached. Thanks in Advance!
View attachment 1060 2013-01-03 19.43.txt
View attachment 3284 2013-01-03 19.13.txt
 
have you set your talent points and made sure your new spells are learned?
 
Yes and Yes on the talent points, and as for lazy raider being enabled I have no idea. I set the bot base to questing and loaded kicks 12-58 profile. The toon that this is from has never even used Lazy Raider.
 
Scrubbish said:
Yes and Yes on the talent points, and as for lazy raider being enabled I have no idea. I set the bot base to questing and loaded kicks 12-58 profile. The toon that this is from has never even used Lazy Raider.
Click to expand...

Hi, Scrubbish,

Please try another Druid Combat Routine and let's eliminate that as the source of the problem... choose from CLU, Singular, or SuperBad only, please.

cheers,
chinajade
 
Actually the problem started when I was using Singular. I installed FPSware hoping to fix it.

I'm not sure but i think it has something to do with LazyRaider. I started having this problem after i installed LazyRaider to dungeon grind on RAF. I left my old HB install where it was and made a second one the same drive, but did not install LazryRaider. 0 instances of this happening with the new install.
 
Last edited:
Scrubbish said:
Actually the problem started when I was using Singular. I installed FPSware hoping to fix it.

I'm not sure but i think it has something to do with LazyRaider. I started having this problem after i installed LazyRaider to dungeon grind on RAF. I left my old HB install where it was and made a second one the same drive, but did not install LazryRaider. 0 instances of this happening with the new install.
Click to expand...

Hi, Scrubbish,

Most excellent--glad you found and fixed the problem.

cheers,
chinajade
 
Well the post was less about fixing what I had going on, and more about passing on information of a problem to the powers that be in order to improve the program :)
 
Scrubbish said:
Well the post was less about fixing what I had going on, and more about passing on information of a problem to the powers that be in order to improve the program :)
Click to expand...

Hi, Scrubbish,

That was not clear in your first post.

LazyRaider is a third-party product. If you would like the issue addressed, please report it to the LazyRaider thread. You might want to give the thread a read, to make certain the issue isn't already known, or has a work-around.

cheers,
chinajade
 
Well I didn't come up with the work around when i first posted the thread. What is odd though is as Tony pointed out, even though the bot base is Questing, LazyRaider is enabling anyway.
 
You must log in or register to reply here.
Back
Top