Thanks Beowulfe. Thats an internal implementation method for CastOnGround variations and the intention was for the delegate passed to be non-null, with any null handling handled by the caller. Looks like I introduced a bug at line 1992 in v4.0.0.4064 where a null is being passed. Thanks for posting and look for a quick update with fix late tonight. In the meantime you could change line 1992 from: ContextCastOnGround(null, waitForSpell) to: ContextCastOnGround(req => true, waitForSpell) Thanks for the post, -Bobby53
help how to make shadow priest use mind sear in aoe situation hes just single targeting everything like 20+ mobs
awesome update, bobby! first big one we have had in a while for singular when i go to level my next toon, i will use singular as my routine, and submit bug reports if i find any, with logs/logmarks. lets get this baby fully polished!
HELLO. Fgame did not attach the log Pleas fix Edit: Bobby -- Does Singular handle AoE rotations, or is it strictly single target? I went through all the settings in the Class Config section and saw nothing pertaining to AoE counts. If it does handle AoE, I'm venturing a guess that the AoE count is hard coded to something like 3+ units? Again, I ask this because while leveling a feral (cat) druid, the routine seems to really only use a single target rotation, even when there are multiple mobs. I also noticed that someone reported that shadow priests don't use their AoE spell (Mind Sear). I don't remember clearly, but for some reason I seem to recall a post you may have made pertaining to problems with AoE that may be sorted at a later date. If I'm wrong about this, please forgive my ignorance. I wasn't completely certain. Here's a log anyway. If you find any spells or skill in the log that pertain to AoE, please feel free to point them out to me. My apologies for missing them.
Hi Zeldrak, Great to see you here my friend! Yes, Singular handles AoE spell priorities. However, Singular does not expose a generalized AoE count. Since the response to a multiple mob situation varies with each specification, so does the AoE count. In the few situations where it does provide an AoE setting, the setting is not a general AoE count but a count controlling the application of a specific ability for that spec/class. In general, there isn't a need to wildly vary the AoE count. If Singular doesn't detect what you believe to be an AoE situation as described by Noxxic, please post a log and I will look into it and either fix the issue or advise why it responded in the manner it did. If there is an AoE situation you believe warrants a response that differs from that described by Noxxic, please link the reference website describing what should be done in that scenario and I am happy to add a user selectable variation of the default behavior. Ultimately, there are currently waaaayyyyyy too many settings in Singular since the premise is it should just work. At one point in Singular development, I felt that the best response to an AoE situation in Normal Context (Solo) was to stay Single target and burn down a mob as quick as possible, then move to the next. The idea behind that is that with each kill you decrease the incoming damage. If you respond with AoE abilities, your overall damage likely increases, but the life expectancy of every mob also increases lengthening the fight and the amount of damage you take, thus decreasing your survival rate. If you do die, better to have killed 1 to 2 mobs in the process and clearing some areas to ressurect than dying to an AoE pack that you can only get down to an average of 25% before dying which leaves them all to reset to a 100% health and be waiting for upon rezzing. There isn't one right answer. AoEing a pack makes sense if you are able to survive. Burning down mobs is justifiable whether your toon lives or dies. Ultimately you can't tell which was the correct approach until the fight is over. I'll give user control of AoE counts some additional thought. However, Singular doesn't try to be all things to all people - its mantra is that it should just work. As for your specific example, there were a number of Thrash and Swipe casts in your log file, as well as some multi-target applications of Rake. Thanks for the post and good luck with your Druid, -Bobby53
In helpers\item.cs line 221/248, there's support for crystal of insanity. Tried update it to work with 'Oralius' Whispering Crystal', itemid 118922. buffs 'Whispers of Insanity', SpellId 176151. but its never that easy, is it lol.
Need to add in rogue routines WoD box True Steel Lockbox - Item - World of Warcraft Manualy add { 116920, 0 } // True Steel Lockbox
Hi! Can you please give me a tip: is there a way to tune Singular, so that my frost mage would kill low-level mobs using only Ice Lance instead of Frost arrow? Or just use Ice Lance only? Maybe I missed some settings?
What Class+Spec are you?: Warrior All Specs What 'context' is the bot in? (Instance, BG, Normal): Normal What level are you?: 100 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? Every day What happened (be specific)? Even without taunt being enabled the bot still seems to use taunt and change into defensive and refuses to change back to battle stance. Glad stance not even an option. Did you attach a complete debug log? (choose one: YES or YES) No. Irrelevent
warrior pulls w/ taunt even w/ it off. warrior changes to defensive stat with no way to disable this. If put into glad stance manually and it changes ot defensive, it never changes back to glad which is severely detrimmental to farming etc. Was hoping one of these things would be fixed in the new version, woe is me! The CC is superior to all others when it comes to intricate logistical tasks but technically... ewwww! anyhow, thank you for your time and effort... i might QQ but dont let that diminish how great it is that you work on this regardless.
What Class+Spec are you?: Death Knight(Frost) 2h What 'context' is the bot in? (Instance, BG, Normal): Normal What level are you?: 67 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? What happened (be specific)? Uses only "Death Strike", but never uses "Obliterate" even if Deathmachine is on Did you attach a complete debug log? (choose one: YES or YES) Yes
Hey bobby, does the routine support cloudburst totem for restoration shaman(level 100 talent) didn't see it use it so far, i'll try to post a log of a dungeon run soon. Also some tips to elemental shaman dps: Cast earthshock only after you have 17+ stacks of lightning shield(currently casts at 5) Cast earthquake only after casting chain lightning to get enhanced chain lightning bonus(currently seems to cast earthquake without Enhanced CL stacks) Cast earthquake on 2+ targets(currently seems to be set to 3/6 targets?) Cast earthquake despite mana situation on aoe(code indicates to only cast with clearcasting or 60+ mana if i understand correctly)
tomten2, Have added in next release. I don't have one presently to test so post a log if you don't see a "/use item: Oralius' Whispering Crystal" message. -Bobby53
My Fury warrior keeps using taunt while leveling and changing to defensive stance, and then he doesnt change back, and it makes him lose aloooot of time
Hello. Destruction warlock is capping embers. See ~5 seconds before and after logmark 1 and 2. It should override and force chaos bolt cast at => 30 embers, even on pulls. Its less problematic at max level but while leveling it'll constantly cap as every new mob forces the pull rotation and once it reaches chaos bolt the mob is often dead already :-/ View attachment 6876 2014-12-16 01.58.copy.zip Edit. Realized while watching the bot play, this is an old error i've reported before... At full embers he starts with imo, then he goes for conflag (you waste ember generation and force inc casts for backdraft stacks) once chaos bolt passes req, mob is dead and the loop is on.
Singular is casting 'Banish' on mobs for some reason (can't find a setting for it.) and keeps attacking the banished target until banish runs out. Instant bot spotter if someone sees it. Wasn't fast enough with logmarks but searched the log and created 2 of my own to give you some reference to go on. View attachment 7904 2014-12-16 03.57 - Copy.txt Shorter log with proper logmark, leaving both logs as its a critical issue. View attachment 7904 2014-12-16 03.57 - Copy.txt Even shorter log dedicated to the issue, logmark from application and a couple trough it and lastly until banish ended. View attachment 7804 2014-12-16 04.25 - Copy.txt This issue makes destro less then desirable for anything AFK. Not sure why it should use banish at all while leveling. even questionable in group play/max level as its more likely to cause issues then benefits. If used I think it should only be triggered as a defensive measure based on player hp % rather than mob count. Also should be able to cancel it. My 2 cents at least.
