23051602, Well, have to say I am a bit surprised to receive a log file that doesn't represent what I had carefully explained in my response to your earlier post. The switch from DungeonBuddy to RaidBot while in combat seems to have created an issue. In general, Bots should be switched while you are not in combat. As for max DPS while using DungeonBuddy, that won't happen. DungeonBuddy is an amazing piece of work that has intelligence to implement a raid fight strategy based upon tank position, moving out of fire, etc. That movement is focused upon moving out of the stuff on the floor, staying in range of something, etc. and not DPS/HPS, so in situations where it could strafe and still attack the target it instead turns and runs. This is not a condemnation of DungeonBuddy, quite the contrary... it's an amazing piece of work. Your expectations while using it should be that you can complete a raid encounter without manual intervention, not that you'll max out DPS. For higher DPS, you'll want to use a manual assist bot so you can do things like pop Spiritwalker's Grace prior to moving and strafe instead of turning away, etc. In the same way the movement of DungeonBuddy can impact an Elemental, so can the movement and positioning by the user with a manual assist bot. As for sluggish casting, that should be expected given the following:
Code:
[07:10:41.020 D] LogLevel: Diagnostic
As mentioned in my prior response, you will want to disable debug output and set Log Level to Normal when assessing performance as verbose log file output degrades performance (aka sluggish casting.) Only after determining that you believe that there is an issue with the spell priority would you want to enable debug output, and at that point it isn't to assess performance with debug enabled but to provide the detail needed to understand why a spell was or was not cast.
For now while you are trying to improve the results you achieve while raiding, follow the steps I provided carefully and use a training dummy. That will provide a stationary fight and reduce the number of variables impacting your results.
Thanks for the post and good luck with your Elemental, Bobby53
Edit: btw... in reviewing your log file there is a bug in that release that occurs when casting Earthquake. The spell was cast but the log message after it caused an exception that generates some log file noise. Fixed in the next release. Thanks for passing along.