cmills, The versions of LazyRaider available for download does not initiate combat. If that occurs, it is due to the CC (CustomClass/CombatClass) you are, an enabled HonorBuddy Plug-in, or your WOW client targeting in response to a unit attacking you. As Laria mentioned, you can configure LazyRaider to recognize a Pause key sequence. This will allow you to Start the bot, but then press the Pause key which will prevent it from automatically doing anything until you press it a second time. Note the Pause key must be pressed while WOW is the active Window. If you have any further questions, be sure to attach a complete debug log file with your post. Thanks and good luck with your LazyRaiding, Bobby53
I'd assume you would know about the risks of getting banned using Honorbuddy seeing you've been registered here for more than a year... Just have some common sense and you wont get banned.
I have read through this, and installed, and went to RaidFinder to test it. But I'm having some issues. I'm using a Druid Healer with HazzElite CC, and I've disabled movement. Chose the Tank on LazyRaider. But this is not that lazy isn't it? Or am I missing something? And the targeting of the players that need to be healed can be done by LazyRaider?
furyz0r, Thanks for the post. You mentioned having some issues, but I only see where you question if the use of the term Lazy is appropriate so I'll address that for now. The case given is one of playing a Healing class with this Bot in Raid Finder. I suppose its a value judgement, but I would say LazyRaider allows you to be very lazy in this casec. Here is how I view the relative laziness made possible by this Bot: 1. Movement. Since movement was disabled in the CC, you are responsible for moving the character while in combat. You can leave movement enabled in HazzElite CC, but if it doesn't have support for specific raid encounters or moving out of AoE you are betting off leaving it disabled and moving yourself. 2. Positioning. This is really just where you are moving too (or stopping at), so although it appears as an extra word in the statement I doesn't imply additional work. It merely underscores that if the strategy for a raid encounter is to stack on the guy with a orange circle above his head then you have to move to that spot. 3. Targeting. Targeting of players that need to be healed is handled by the CC (in this case you mentioned HazzElite) so for your setup implies no additional work. In my opinion being able to complete a raid encounter while only having to move the character periodically allows you to be extremely Lazy, but each persons perception could differ. If you decide to continue with LazyRaider, you should use it for some Heroics first before attempting in a Raid so you are comfortable with how the CC handles you moving while it tries to cast. Your overall raiding experience while using this bot will primarily be controlled by the CC you use, as what LazyRaider does best is get out of the way so you can control movement and the CC can control everything else. Thanks for the post and good luck with your LazyRaiding, Bobby53
When adjusting the performance setting in the bot's Interface, I still can not get it to tick at the same speed that RaidBot does. Does the MaxDps button config the bot based on your current performance?
mount/dismount loop. He starts mounting hes flying mount in a loop when out of range in a BG. This happens on the last two new releases of Lazyraider.
He starts mounting hes flying mount in a loop when out of range in a BG. This happens on the last two new releases of Lazyraider. Attached Files Attached Files File Type: txt 08.07.2012_11_27 5064 Log.txt (554.5 KB, 5 views) I have same problem, please fix this.
When i try using it i lagg really bad. Cab barely move my toon so it can keep up with target. Ive tried different ccs but i still lagg. Id really like to be able to use this with anymlagg. Is there a specific way to set my settings or anything?
Kazs1390, For use with systems that lag badly, click Bot Config and clear the check box for Frame Lock. The lag is due either to the design of the CC you are using and/or the computer system you are running on. Thanks for the post and good luck with your LazyRaiding, Bobby53
trichomer, Thanks for the post. Not much time presently, but will look into this next opportunity. Bobby53
tawing79, Thanks for the post, but rather than copy/pasting trichomers post and log file attachment it would be better if you attached one from your botting session. As it stands there isn't anything I can use in your post that trichomer didn't already provide. Good luck with your LazyRaiding, Bobby53
Hi Bobby, just wanted to know if there is anyway for me to get lazyRaider to tick as fast as Raid Bot.I've changed the settings to 30fps and 60fps and neither helped.With LazyRaider since there is a small delay between casts. Using LazyRaider i can get around 20k on my warlock for example but with Raid bot i can do 30kdps but i do get lower fps with Raid Bot.
hi! I'm an noob an just tested lazyraider for the first time. The plugin is easy to handle and really great with the right cc! But i have one question: is there an svn checkout for this addon available? Sry if that was already asked but this thread is really long^^ greez Veo
Body im using lazyraider with shamwow on my resto shaman to follow and heal my ret pally on arena, i dunno why but sometimes the shammy keeps mounting UP over and over and over... and i diselected use mount on honorbuddy... what should i do ? tks
Hey guys! I just started using Honorbuddy and all so I'm still getting used to all the settings. I've enabled LazyRaider and set the configurations there together with HazzDruid Elit4.0.4 (Using the Restoration profile). I disabled movement and enabled "Heal Out of Combat" and "Enable Combat" within HazzDruid, while ticking on "Auto Target" and "Run Without a Tank (no leader)", but whenever I tried testing it out in a random battleground and random heroic but, I was forced to heal manually. Is there something I'm missing or not doing right? I know I wasn't setting LazyRaider on pause.