my Frost Mage (498iLvl) in LFR doint 39-43k dps on boss - is it normal???? i think i must do at least 100k... but not only 40.... what i must do????
Thanks for the debug log and frame of reference. It's not clear what the issue is from the log other than the fact that it is moving towards the Sap mob but not getting significantly closer. Wozoki93 had posted log for Night Elf Rogue Levels 10+ and said it occurred beginning at Level 1 using Kicks profiles. I watched leveling a Night Elf Rogue from 1 - 12 with the same profiles and did not see an issue. Only difference was that I had only AutoEquip2 and Refreshment plugins installed and active, whereas he had a few others. You have quite a few others. My recommendation is to remove all plugins (not just disable -- since some cause logic to run even when disabled) that are not essential and retry. I'll see what I can do regarding additional debug output for moving towards a Sap target which seems to be the common link. Thanks for the post and good luck with your Rogue, Bobby53
tumbum, It is the responsibility of the profile author to disable the Combat Routine when in a quest vehicle, so you will want to post in their thread. If it is a quest that has a custom quest behavior which completes the entire objective then it should be modified to disable/enable the appropriate behaviors. If it is one that uses multiple behaviors or statements in a profile then the profile author can use the EnableBehavior tag. See CJ's post on Pull Distance and You for documentation on the EnableBehavior/DisableBehavior questing profile elements [click here]. For profiles no longer maintained, you can change Singular to disable itself when in a Quest vehicle as described in the message: It is not recommended you do this since some profiles require the Combat Routine to be active while in a quest vehicle, so setting the above option will break the use of Singular for those quests even though it fixes it for others. The distinction of which quests require the Combat Routine and which quests it should be disabled is the responsibility of the quest profile author and one of the elements coded into the quest profile or the quest behaviors it uses. The option above will be removed in an upcoming release and Singular (as all combat routines should) will depend upon the quest profile to enable/disable as appropriate and not have logic to detect quest vehicles. -Bobby53
You will want to Post as described in Reporting Bugs [CLICK HERE] for assistance. There are too many factors that lead to lowering your DPS. For example, are you running with HonorBuddy's Log Level set to Diagnostic? If so it provides terrific info which I will need to look into your issue. However, you should be running with Log Level set to Normal if you are concerned about DPS as a high volume of log activity will cause low DPS. Additionally, if you are running DungeonBuddy to automate you will be trading DPS for convenience. Simply not enough info for me to say what is causing the issue for you without the correct type of log file attached and description as referenced in the post I linked. Just to clarify: 1. You need to set Log Level to Diagnostic for the log you submit so I can see all the necessary details of your configuration and setup. 2. You need to set Log Level to Normal any time you are measuring DPS as its a meaningless value when you have Verbose or Diagnostic output turned on. -Bobby53
Just a little Quest to Sigular + Questbot, is it possible to "deactivate" Singular for some Quests and just let Singular do White Autohits and not the full Combat Routine?
You can Disable combat and add a macro in the profile with /cast auto attack. You'll have to know where the target will be though as the CC wouldt auto face or walk up to the target. Anyways. I really don't see in what sort of scenario this would be useful. Edit: It would be like this Code: <DisableBehavior Name="Combat" /> <!-- Disable the combat. CC will not interfere --> <MoveTo xx.yy.zz > <!-- Move to whereever the target will be --> <CustomBehavior File="RunMacro" Macro="/cast auto attack" NumOfTimes="1" WaitTime="40000"/> <!-- Wait time as long as you think you need to kill the target. 400000 = 40 seconds --> <EnableBehavior Name="Combat" /> <!-- Enable the CC again --> Sorry for going off topic, Bobby.
For Quests where you need to use an Item at a % of Life of the Mob. When using Singular in full mode with Pets, Dots, full Combat Routines the Mob will always die before it use the Item on him. So the only thing i see is to deactivate the Combat Routine and just do White Hits till the %. But Facing must work. Ok lets stop here, will ask later in the Devs Forum.
No worries. What quest objective would this be useful for The Combat Behavior doesn't have to be disabled prior to combat, it can be done in the middle of combat (this may require a custom quest behavior however -- there was one in the past that used an item at a certain health % but I am NOT familiar with the current catalog of custom behaviors available.) So in the case described it could be allowed to proceed until reaching a quest mob specific health % and then disabled. I would imagine that will come out in Dev Forum discussions. Good luck with the solution. -Bobby53
No need to apologize, but if you would like me to research this issue you'll need to follow the steps in the Reporting Bugs post I provided in bolded red to you in my previous reply. Good luck with your Rogue, Bobby53
I am ok with rouges, I can wait to open all boxes for some weeks. You do not need to research if you don't wanna do that. I just say that isn't working.
Is there a way to IGNORE attackers with Singular? My toons die in The Barrens because they are LvL 85 and those nasty Kor'kron Orcs are LvL 90 and really evil. Toon flies to e.g. Bael Modan digsite - gots ranged attacked from those orcs - lands and fights... and dies
standza, Thanks for the post, but it doesn't work that way. Rogue Pick Lock is working well for me, so if there is an issue it appears to be specific to you and your configuration. So, if you would like me to research why it doesn't seem to work for you then follow the steps in the Reporting Bugs post I have politely referenced three replies now so I have the information needed to do that research. By omitting the details I have requested, you are letting me know the issue is not important to you and does not require any research. Good luck with your Rogue, Bobby53
Keldorn, No there isn't. The Combat Routine (in this case Singular) is component or tool used by the BotBase (sounds like Archaeology) to kill things when the BotBase thinks it should. The decision to attack one type of target and ignore another would be handled by it. In the case of Questing, the quest profile would contain that information. ArchBuddy doesn't support profiles however and the Bot Config user settings don't appear to allow specification of that either. My suggestion is to post in the HonorBuddy Support thread so the issue can be looked at relative to AB. Thanks for the post and good luck with your toon, Bobby53 Edit: btw... you can configure AB to ignore specific dig sites. Check the AB settings and have it skip that one if going there is problematic.
Thanks. I know i can BL but when the toon flies over the Barrens he got killed. This depends on where he is and where the new digsite is.
Understood, but as I mentioned this is not a Singular issue. For assistance with this, you will want to post in the HonorBuddy Support forum providing a log and indicating specifically what the problem is. -Bobby53
standza, My friend, this is a text book example of why a log file should always be attached. Although the original post indicated using Singular v3.0.0.3173 the attached log indicates you are using: Pick Lock is broken in that earlier version. Download the latest from this thread (3.0.0.3173) and you should not have a problem. Thanks for the log file and good luck with your Rogue, -Bobby53
