Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
I posted the SetTheLeader plugin [link--click here] I had been using which will allow you to select the Tank. It will work with the RAF bot and should work with the Combat/Heal Bot shortly.
dshiizznitt, My apologies for the issue you are having. I don't have enough information to be able to respond to your issue. A bug with Bloodlust/Heroism in RAF/Instances was reported late yesterday and a fix is being tested for release later today, however I have no way of knowing if its the same issue you are experiencing without a complete debug log file. You will want to visit Post #2 in this thread. Frequently Asked Questions-FAQ [link--click here] has details on the information needed when posting an issue. There is a template there you can copy and paste if needed. Once the requested information is available, I will look into this further for you and if the problem is the same or different and provide a fix in next release if needed. Thanks for the post, Bobby53
Just to clarify, all the Mr. AutoFight plugin does is disable Bot movement, so it would prevent the RAF/Combat Assist or the Combat/Heal Bots from moving the character. ShamWOW will recognize if you have Mr. AutoFight enabled and disable its movement, but if you have any issues with that you can Disable CC Movement in the CC Configuration window. Of course, this means you will need to move the character throughout the raid. That is required for now until support for Raid scripts is provided similar to how InstanceBuddy provides Instance/Dungeon scripts.
Check the prior posts reporting the issue for the workaround prior to getting the release with containing the fix. Thanks for the follow up, Bobby53
Release I am about to post is just a bug fix build to address the Bloodlust / Heroism issue reported.
That is an HonorBuddy bug. CustomClasses (CC's) like ShamWOW in general deal with how to fight and movement while fighting. All other movement, looting, gathering, /use of Quest items, etc. is handled by HonorBuddy or specifically coded Plug-ins. You'll want to post about this one in the HonorBuddy thread.
One of the responses [link--click here] to another user reporting on double heals. The double heal occurs but only within specific situations as discussed in the linked post. Healing Surge uses more mana, but it also has a much faster cast time and heals for more which makes it a good choice when you can't anticipate the amount of incoming damage. The key criteria is whether you kept your group alive and having sufficient mana available throughout the encounter. Nobody at the end of a run is going to comment on how much mana you used, just whether you kept the group alive (despite their best efforts to die) and if you went OOM and had to wait for you to drink every fight. If you (or any member) is going OOM while healing please send the complete debug log file so I can do a detailed analysis of the heal selection and mana consumption. I could easily add in more Healing Waves because people want to see them, but to add them just for the sake of having them would be a mistake given all the data received so far on the healing performance of the current spell selection. So currently, Healing Wave is reserved for when nobody is in combat or there isn't sufficient mana for a HS, but I will gladly change that when the data is received that indicates a need for a change since it should also indicate what change is needed. I will provide a mechanism in an upcoming release to allow the user to adjust their preference with the trade off of slower healing vs. double heals.
Could you help identify what point in the log file corresponds with this behavior? I looked but I don't see anything indicating CC movement occurred outside of the instance so it is possible it was InstanceBuddy but I'd like to be sure rather than just deflecting the issue.
Was this inside the instance or while you were waiting?
I said that drinking frequently would be an issue (see the highlighted part of my prior response above) so I agree. However I haven't received a log file indicating anyone had to do that yet due to the spell selection, including the one attached to your post. I looked at the first SM Run in your log file. You would have only had to stop to drink once for the entire run (which is reasonable), but the tank always started with the next pull immediately so InstanceBuddy would interrupt drinking. You had a total of 3 drink attempts all which were interrupted at 50.31% (started at 37.73%), 40.77% (started at 38.02%), and 52.82% (started at 48.12%) respectively. Since your Resting Mana % was configured at 49% there is a good chance you would need to attempt to drink each fight.
Again, please read the post where I responded to this issue with another poster [LINK--CLICK HERE]. If you feel the explanation isn't clear, ask for clarification.
The best way is to .ZIP them before attaching. Log files have a lot of repeated text and compress well. The forums don't accept .RAR files so you'll need to use the .ZIP format.
Again, the mana issue I am seeing in the first run is related to not being allowed to replenish above 50%. Also note, your Shaman never went OOM despite being prevented from drinking. Also, since drinking was interrupted to keep up with the group, my assumption is that this didn't represent a group where anyone was "yelling" at you about the healing.
Change History
[B]11/17/10 Revision 4.2.08[/B]
- Fix: fixed problem with Bloodlust/Heroism being cast for trash in Dungeons/Raids when option saying to use on Bosses was set. Now correctly casts only for Bosses.ugghh... As described in post and change history for 4.2.08, the fix was for those running Dungeons and Raids. No issue prior to your submission indicated a problem while grinding. Thanks for the log file and to the point post. I'll get you an update shortly.