Problem in 60-63 Blood Furnace.
Booster attempts to target a rogue on the way back to RAFs but 90% of the time the MOB isn't there and the bot just stands and waits. (Maybe this needs a check for mob xxx timer so that it can move on?)
<!-- Targetandmoveto a rogue on the way out to keep the rafs safe -->
<CustomBehavior File="TargetAndMoveToMob"
MobId="17491"
MoveWithinMaxRangeOfMob="1"
WaitForNpcs="false"
TargetOnlyIfHealthPercentAbove="5"
X="162.3682" Y="-91.31461" Z="9.602009" />
Thanks as always <3 Running 90 Blood DK with 2 x RAF squishies and it's incredible.
I have an issue. I believe I have set this up wrong from the reading I was doing but after 20 pages of reading I cannot find my answer.
I have a main account - from that account I used the RaF button to two new emails and started ( and bought ) new accounts. I then got those two accounts to level 10 and started the booster running them through deadmines. I get about 10XP per mob, the entire instance only got me a portion of a level at a level 10's point of view. I don't believe I have it setup right from the accounts perspective.
Any advice on how I should start and actually receive the benefits of RaF to power level?
Account A = Booster, non RAFed, B + C = 2 RAF accounts. A boost B + C
Will work on this some more today, I will try to get ally Northrend and Pandaria done. Then horde over the next few days.
So happy to hear you are working on the hordeversion.
You have entered too many instances recently....thats a pitty even a reset wont help.so no big gold making out of this one.
Most likely, you are the cause of the instance lock. The profile has built in timers. It will not leave the instance until 12 minutes and 30 seconds has elapsed. meaning you stopped and started the bot while it was in the instance. It then exited and reset the instance faster than 12 minutes resulting in your instance lock after a few runs. Before making judgements in the future, perhaps you should investigate more and actually know what you are talking about.
Most likely, you are the cause of the instance lock. The profile has built in timers. It will not leave the instance until 12 minutes and 30 seconds has elapsed. meaning you stopped and started the bot while it was in the instance. It then exited and reset the instance faster than 12 minutes resulting in your instance lock after a few runs. Before making judgements in the future, perhaps you should investigate more and actually know what you are talking about.
Don't be so offended,he was just giving input,maybe you can have a look to the profile because 2 ppl having the same problem.
Before going in offensive mode in the future,maybe say i have a look to the profile.
JS.