Hey bobby, In /Helpers/Spell.cs, line 1982 (in function ContextCastOnGround), this line: Code: if (cog.spell == null || cog.loc == WoWPoint.Empty || !requirements(cog.context)) should probably have a NULL check on requirements, such as: Code: if (cog.spell == null || cog.loc == WoWPoint.Empty || (requirements != null && !requirements(cog.context))) otherwise it throws exceptions like crazy and causes issues in a few routines. The place I ran into it was with a Mistweaver monk while he was attempting to place his jade statue - it was passing in NULL for requirements (I assume that was intended to say "no requirements") and erroring out constantly, causing it to stop healing entirely and inflate the log files to several hundred MB very quickly.
Is there any way to keep Singular from dismounting from the Telaari Talbuk?? or is this apart of the botbase?
*new* Singular v4.0.0.3991 available for download! Refinement on Shadow Priests improving their survival and kill rate in WoD. Also final revision of support for Garrison Abilities to avoid using those which are not attacks. If its worth posting about, its worth following the steps in Post #4 - Reporting Bugs in Singular. More to come..... -Bobby53
Hey can you make an option to turn off slice and dice, assassination rogues get it as a passive now and singular keeps trying to use it. Improved Slice and Dice - Spell - World of Warcraft
Thanks for taking the time to write such a thorough post! I have incorporated a number of fixes based upon this. Please see the latest release (from this thread.) It will likely require some additional refinement based upon additional member feedback, but there should be a noticeable improvement in survivability. Thanks again for the post and good luck with your Priest, Bobby53
Synful, Thanks for the log. Please see the latest release which defaults to 0% for Shadow casting Prayer of Mending. If you upgrade an existing installation, you will need to click Class Config ==> Class Specific and change the Prayer of Mending Health % on the Priest tab. Thanks for the post and good luck with your Priest, Bobby53
class" elementa/resoration shaman: it would be nice if your included something so that we could turn off totem recall. Takes me out off ghost wolf form no matter what im doing. thank you
Thank YOU! The change is a huge improvement and immediately noticed. The death rate was much lower, almost eliminated; got from 96-98 in just a few hours. It even pulled a rare mob on top of another add and I was like shiiiit, but it actually focused the rare down while keeping dots on the weak target, killing them both! Looked impressive. I'll keep watching on its way to 100 to see if there's anything else I can give feedback on. Another setting unrelated to the CC that I think was messing me up was "Kill between hotspots" in settings & config menu of HB. I turned this off when it was having issues, trying to avoid as many fights as possible. But when off, the shadowpriest seems to run up on top of the target for combat, and trying to reposition itself in melee of the target. I think it's trying to get to the hotspot (the target) and perpetually repositioning as the mob backs up a yard, usually a quick death. I was about to log this, but tried flipping the setting back on first. It now seems to approach the hotspot areas more cautiously, killing its way through crowds 1 at a time. It also kills mobs nearby that are not aggro and unrelated to the quests, though. But if anyone else is thinking they might save some time by not killing between hotspots, wrong. At least for questing, that setting seems to be necessary for ranged survival.
Its there so you dont die basically. If you turn it off, it will only run to the next hotspot, pulling anything while mounted and ignoring combat. If this distance is short enough with enough mob density, you'll instantly kill yourself and waste time. It also pads XP between quests. Unless overgearing (read not lvling) you want it on. Also the reason why its on by default and auto enabled by most questing profiles even if you disable it.
The hunter routine is realy messed up. The bot does not use the major cooldowns. Do I have to wait for an update or what do I have to do?
Affliction warlock will sometimes banish an add, then not unbanish it and try to cast drain soul over and over. Looks very bad.
*new* Singular v4.0.0.4014 available for download! I will only be responding to posts that following the steps given in Reporting Singular Bugs (click here). A fix a number of members have been waiting for with Warriors stuck on Defensive Stance. Also a number of fixes for Shadow Priests. Just a reminder, if it is worth posting about it is worth following the steps in Post #4 - Reporting Bugs in Singular. I have been focusing on the code and less on the forums recently, so my apologies if the lack of a timely response to your Singular post was a concern. I will be responding to all Singular thread posts in the next day. Thanks for your patience, -Bobby53
I wish that was the only problem , the rotation complety sux , dont even uses plague strike and self healing ...im very geared and i die alot.
Just a reminder, a lot to do still. As mentioned several times, I'm not replying to posts the are.... - Questions about behavior but log files or no LOGMARKS (click here for info) - Bug reports with no log files - Emotional posts Also, make sure if reporting a bug about something that did not occur (spell not cast, char not moving, etc.) you will need to have LOGMARKS (click here for info) at the point where it did not occur. By definition, if something did not occur there won't be log entries describing it. The LOGMARK will help me see what Singular decided to do instead and allow me to research / recreate the issue as needed to get it resolved for you. Thanks for your posts and good luck with your Singular characters, -Bobby53
Beowulfe, Thanks for the post. The Vital Mists only implementation of Surging Mist is a problem. Will get that resolved in next release. The ActionAlwaysSucceed referenced doesn't block multiple Surging Mists while in Combat as CreateMistweaverWaitForCast() is present in the Combat behaviors, but Healing is handled in the Heal behavior which is a higher priority and called prior to that (unless the BotBase in question is not honoring the correct usage of behaviors.) That success entry simply keeps the Combat behaviors from casting attacks or other spells which would interrupt the Soothing Mist in progress. I'll look at the rest of the info you posted but replying back on that point quickly while I had a moment, -Bobby53
colabah, Thanks for the post with log file. This issue should be fixed in Singular v4.0.0.4014 which is available for download from Post #1 of this thread. Thanks and good luck with your Warrior, Bobby53
