HB ARCHIVES: Singular--DO NOT DELETE

[godpan]

Are u kidding me? Why u add auto-Vanish in Rogue rotation, it's just stupidly evading bosses... I even can't cancel it, this button is not present in settings!
And occasional use Cloak of Shadows at any moment of the battle, not just when the character takes on a higher damage already becomes annoying.
Please take a Rogue little more of your time, because now this rotation is just ridiculous.

 

[Ikyata]

Balance Druid in particular just moonfires everything within range despite what your "pull more" options are

 

[ectocooler]

What Class+Spec are you?: Unholy Death Knight
What 'context' is the bot in? (Instance, BG, Normal): Normal
What level are you?: 108
Have you made any modifications to Singular?: no
Are you using the Test Build of Singular?: no
What time (HH:MM:SS) or LogMark did your issue occur? Logmark 1 and 2
What happened (be specific)?

Singular spams the following:

[19:21:39.048 N] [Singular] *Death Coil on Meet.51DB @ 62.6% at 0.0 yds
[19:21:39.959 N] (Singular) [WoWRedError] 50
[19:21:39.907 N] [Singular] *Death Coil on Meet.51DB @ 62.6% at 0.0 yds
[19:21:40.543 D] Stopped moving.
[19:21:40.740 N] [Singular] *Death Coil on Meet.51DB @ 62.6% at 1.7 yds
[19:21:40.796 N] (Singular) [WoWRedError] 50
[19:21:42.931 N] (Singular) [WoWRedError] 50


View attachment 7544 2016-09-10 11.27.txt

 

[elpargo]

This, so much this.
Would increase KPH by 100s if HB would use the correct skills.

You can add spells to the rotation easily, but i dont know how to apply "logic" to them. Simply add: Spell.Cast("Fel Eruption", on => (WoWUnit)on),
Under // High Priority Single+AoE
In Singular\ClassSpecific\DemonHunter\Vengeance.cs or Havoc.cs

You can add any spell, switch "Fel Eruption" for the name of the spell you want, works with Artifact spells too.

 

[Phenotype]

Balance Druid in particular just moonfires everything within range despite what your "pull more" options are

Having the same issue, the druid just stands there and spams moonfire like a retarded owl.

And it breaks my heart that development of the bot went downhill since the addition of the store.

Now all base packages get second rate treatment, in order to push users to buy the routines...

Very sad, I really love this product, but there has been a lot of bad management over the years in regards to this.

If they made a 20 euro a month sub with ALL routines and ALL plugins available, I think it would be even more successful.

 

[EchoTiger]

Balance Druid in particular just moonfires everything within range despite what your "pull more" options are

Having the same issue, the druid just stands there and spams moonfire like a retarded owl.

And it breaks my heart that development of the bot went downhill since the addition of the store.

Now all base packages get second rate treatment, in order to push users to buy the routines...

Very sad, I really love this product, but there has been a lot of bad management over the years in regards to this.

If they made a 20 euro a month sub with ALL routines and ALL plugins available, I think it would be even more successful.

Singular's original developer, Bobby, went MIA over a year ago - and since then Singular hasn't had a dedicated developer.
I've only recently taken over Singular - and have been addressing all reported issues, but with Legion launch the questing profiles have had me swamped.

The neglection of Singular is purely because of these two factors - and has nothing to do with the store.

The Moonfire spam issue has been fixed already - and will be live in the next Honorbuddy update.
There will also be the addition of Artifact Weapon usage, Demon Hunter rotation rework, and several bug fixes.

There's also a massive Rogue rework pending.

 

[Phenotype]

Singular's original developer, Bobby, went MIA over a year ago - and since then Singular hasn't had a dedicated developer.
I've only recently taken over Singular - and have been addressing all reported issues, but with Legion launch the questing profiles have had me swamped.

The neglection of Singular is purely because of these two factors - and has nothing to do with the store.

The Moonfire spam issue has been fixed already - and will be live in the next Honorbuddy update.
There will also be the addition of Artifact Weapon usage, Demon Hunter rotation rework, and several bug fixes.

There's also a massive Rogue rework pending.

Thanks for your work.

But what I mean is that Bossland sold the bot at the time, with that singular as a base product, it was part of the functioning suite. All those questing, gathering, PVP BG, etc, it was dependant on Singular.

So Singular is actually one of the most important parts of the bot, and the fact that someone had to volunteer to take care of it, has shown a huge disrespect to early supporters of the bot, because it now feels that Singular is just a very bad bandage until you get a proper combat routine... paid from the shop.

You know what I mean?

I am in no way belittling your work, not at all, I am just surprised and sad that the buddy team just deliberately "forgot" their main botbase which is the combat logic, dare I say that all the rest depends on it.

And now we are left with a subpar product that is not fit for purpose, which is a shame.

I hear a lot of people I speak to, said they switched to the competition (because like me, they only use combat routines at all) and it also makes me ponder if I too should make the move. By necessity, not by because I dislike this product.

Bah, sorry for the honesty here, but I am upset and sad at all this because the only thing I use the bot for, is not working... and the only reason I even use combat routines is not because I raid or PVP, I dont ever do those things, but just regular questing and going about in the world... and I cannot do it at the moment because I have arthritis and a hand condition that makes the game unplayable without a combat routine.

I need some hugs right now ;'(

 

[EchoTiger]

Thanks for your work.

But what I mean is that Bossland sold the bot at the time, with that singular as a base product, it was part of the functioning suite. All those questing, gathering, PVP BG, etc, it was dependant on Singular.

So Singular is actually one of the most important parts of the bot, and the fact that someone had to volunteer to take care of it, has shown a huge disrespect to early supporters of the bot, because it now feels that Singular is just a very bad bandage until you get a proper combat routine... paid from the shop.

You know what I mean?

I am in no way belittling your work, not at all, I am just surprised and sad that the buddy team just deliberately "forgot" their main botbase which is the combat logic, dare I say that all the rest depends on it.

And now we are left with a subpar product that is not fit for purpose, which is a shame.

I hear a lot of people I speak to, said they switched to the competition (because like me, they only use combat routines at all) and it also makes me ponder if I too should make the move. By necessity, not by because I dislike this product.

Bah, sorry for the honesty here, but I am upset and sad at all this because the only thing I use the bot for, is not working... and the only reason I even use combat routines is not because I raid or PVP, I dont ever do those things, but just regular questing and going about in the world... and I cannot do it at the moment because I have arthritis and a hand condition that makes the game unplayable without a combat routine.

I need some hugs right now ;'(

Sorry that absolutely all 36 specializations aren't meeting your expectations a week after HB3's launch.
If I were perfect, then the routine would be as well - but I'm not. It's going to take time for me to iron out absolutely every issue and make it perfect.

But let this be known: - I didn't "volunteer." Singular is now my project entirely.
And this "bandage" you're speaking of is the result of an expansion being released alongside of HB3's API changes.

After Bobby went MIA, the year leading up to me taking over was us trying to get in contact with him.
Once we realized he wouldn't respond, this was around when the banwaves started happening - which absolutely killed our funding.

All the "good" developers we had left started leaving because WoW was practically dead to them at this point, and no one had interest in working on Singular.
Nor did we have the funds to bribe them to.

So that's when I took over.

 

[Phenotype]

Sorry that absolutely all 36 specializations aren't meeting your expectations a week after HB3's launch.
If I were perfect, then the routine would be as well - but I'm not. It's going to take time for me to iron out absolutely every issue and make it perfect.

But let this be known: - I didn't "volunteer." Singular is now my project entirely.
And this "bandage" you're speaking of is the result of an expansion being released alongside of HB3's API changes.

After Bobby went MIA, the year leading up to me taking over was us trying to get in contact with him.
Once we realized he wouldn't respond, this was around when the banwaves started happening - which absolutely killed our funding.

All the "good" developers we had left started leaving because WoW was practically dead to them at this point, and no one had interest in working on Singular.
Nor did we have the funds to bribe them to.

So that's when I took over.

So Bossland hired you to be in charge of Singular?
Does that mean it will eventually be looked after and taken care of?

If so, that is reassuring.

I know Singular would not have worked straight out of Legion launch, that was not what I mean. I meant in general, since the implementation of paid routines, the Singular combat routine has been neglected, so it wasn't your fault.
I admire you because you are basically cleaning the others mess, and that is commendable.

Hopefully we will have a working product soon and all will be on track again.

 

[EchoTiger]

So Bossland hired you to be in charge of Singular?
Does that mean it will eventually be looked after and taken care of?

If so, that is reassuring.

I know Singular would not have worked straight out of Legion launch, that was not what I mean. I meant in general, since the implementation of paid routines, the Singular combat routine has been neglected, so it wasn't your fault.
I admire you because you are basically cleaning the others mess, and that is commendable.

Hopefully we will have a working product soon and all will be on track again.

Yep, it's entirely up to me to get it back in shape now.

With this change, I've completely reworked this thread to make it more professional-looking and clean as you can already see on the front page.
The new "Issue Tracker" (which needs to be updated) has been included so users can fully understand what's happening in the background in terms of what bugs have been noted, and what bugs have been addressed.

As issues come in, I debug them - if they are confirmed problematic, they're put up on the tracker.
If the issue is fixed, a new Singular is zipped up to be included into the test build download link.

Currently both the Issue Tracker and the Test Build link are outdated due to the massive amount of Legion bugs I've been clawing through.
Things are starting to slow down a bit now - which I'll be able to dedicate more development time into Singular.

In the upcoming days Singular should be back on track with regular updates - which will be a first in nearly over a year.

 

[lightless]

I'm a c# programmer and I tried looking at some of the code, but it's very alien to me right now lol...
I didn't check to see if there's a tutorial or something, but I wouldn't be able to run it anyways without some extra DLL ou access to the other projects anyways..

If the rotations and priorities could be changed in a way similar to simulationcraft it would be much easier to change things around I think, but that would require big changes.

 

[Jannivkdk]

Hey,

Can't wait for singular to be up and running again!

Good luck on making the script up to date, i'll be waiting patiently for you to finish it

Thanks! really appreciate it .

 

[xalcon]

Hi Echo, thanks for taking over singular. I decided to take a closer look at windwalker monk, since I main that class and the DPS the bot is putting out was a bit low.
I wont focus on AoE DPS in this post, but the current spinning crane kick behavior is not ideal. Anyway

The following issues I'd like to see adressed:

1. Use Artifact Ability 'Strike of the Windlord'. Nice to have: Dont use the ability if the damage would be a massive overkill on non-elites
2. Make use of the WW Monks Mastery: Combo Strikes. See notes below.
3. Minor: Use 'Touch of Karma' if health is getting low and we might need to fight a bit longer

Point 1 should be fairly simple. In fact, I just added it to the Rotation and it works fine - as expected

Point 2 is only possible by changing the Spell Class slighly:
In said class there are 2 properties: LastSpellCast and LastSpellTarget
Due to some unknown reason, LastSpellCast is never written to and only used in the Warlock Routines. To get WW Monk working, I added some code to write the last spell used. I also added a canUse requirement to Blackout Kick and Tiger Palm (single target rotation only though).
Effectivly, you never want to cast Tiger Palm or Blackout Kick twice (or any other ability), even if you have the resources to do so. This can cause problems though if Tiger Palm gets parried/dodged. To counter any dead-locks, I added a simple DateTime property "LastSpellTimestamp". If the routine didnt use a spell for more than 5 seconds (add this to config?), allow the use of spells that have been used before. Better would be some form of detection if said spells missed the target - but I dont know how we could accomplish that easily.

There only one issue with my changes: I dont have a level check in place. The mastery is only available at level 80+ (added)

Here is some code on how I did it. Feel free to use this or discard it.
Thanks!

Spell.cs Changes @ line ~90:

        public static bool CastPrimative(string spellName)
        {
            LastSpellTimestamp = DateTime.Now;
            LastSpellCast = spellName;
            LastSpellTarget = WoWGuid.Empty;
            return SpellManager.Cast(spellName);
        }

        public static bool CastPrimative(int id)
        {
            LastSpellTimestamp = DateTime.Now;
            LastSpellCast = WoWSpell.FromId(id)?.Name;
            LastSpellTarget = WoWGuid.Empty;
            return SpellManager.Cast(id);
        }

        public static bool CastPrimative(WoWSpell spell)
        {
            LastSpellTimestamp = DateTime.Now;
            LastSpellCast = spell.Name;
            LastSpellTarget = WoWGuid.Empty;
            return SpellManager.Cast(spell);
        }

        public static bool CastPrimative(string spellName, WoWUnit unit)
        {
            LastSpellTimestamp = DateTime.Now;
            LastSpellCast = spellName;
            LastSpellTarget = unit == null ? WoWGuid.Empty : unit.Guid;
            return SpellManager.Cast(spellName, unit);
        }

        public static bool CastPrimative(int id, WoWUnit unit)
        {
            LastSpellTimestamp = DateTime.Now;
            LastSpellCast = WoWSpell.FromId(id)?.Name;
            LastSpellTarget = unit == null ? WoWGuid.Empty : unit.Guid;
            return SpellManager.Cast(id, unit);
        }

        public static bool CastPrimative(WoWSpell spell, WoWUnit unit)
        {
            LastSpellTimestamp = DateTime.Now;
            LastSpellCast = spell.Name;
            LastSpellTarget = unit == null ? WoWGuid.Empty : unit.Guid;
            return SpellManager.Cast(spell, unit);
        }

Windwalker.cs changes

/// <summary>
/// Checks if said spell would be affected by the ww mastery
/// </summary>
/// <param name="spellName"></param>
/// <returns>True if below level 80 or if different spell was used last, false otherwise</returns>
private static bool DamageIncreasedByMastery(string spellName)
{
    // If we are below level 80, we want to spam abilities since we dont benefit from our mastery yet
    return Me.Level < 80 || Spell.LastSpellCast != spellName || (DateTime.Now - Spell.LastSpellTimestamp).TotalMilliseconds >= 5000;
}
[...]  @ line ~112
Spell.BuffSelf("Serenity", req => Me.CurrentTarget.IsStressful()),
Spell.Cast("Touch of Death", req => Me.CurrentTarget.TimeToDeath() > 8),
Spell.Cast("Storm, Earth, and Fire", req => MonkSettings.UseSef && !Me.HasActiveAura("Storm, Earth, and Fire") && Me.CurrentTarget.IsStressful()),
[... AOE CODE ...]
Spell.Cast("Fists of Fury"),
Spell.Cast("Whirling Dragon Punch"),
Spell.Cast("Tiger Palm", req => Me.CurrentChi < 4 && EnergyDeficit < 10 && DamageIncreasedByMastery("Tiger Palm")),
Spell.Cast("Strike of the Windlord"),
Spell.Cast("Rising Sun Kick"),
Spell.Cast("Chi Wave"),
Spell.Cast("Blackout Kick", req => DamageIncreasedByMastery("Blackout Kick")),
Spell.Cast("Tiger Palm", req => DamageIncreasedByMastery("Tiger Palm"))
[...]

 

[skillgannonn]

artifact monk attack doesn't work its not in rotation as well as a heap of other talents that are not utelised by singular

 

[justfowowlol]

WW monk keeps healing even at 90% until he dies

 

[xalcon]

WW monk keeps healing even at 90% until he dies

Thats not a bug. Set Effuse Healing in the Bot Config -> Monk Config to 0%. Effuse in combat is useless.

 

[ceduna]

What Class+Spec are you?: BM Hunter
What 'context' is the bot in? (Instance, BG, Normal): Instance
What level are you?: 110
Have you made any modifications to Singular?: remove movement
Are you using the Test Build of Singular?: no

What happened (be specific)?
No an issue with the CR functioning, its that it keeps using Stampede on CD. This looks like a bot when you see it going off with 1 mob up in an instance thats not a boss, or 3 mobs up at 5%. I would prefer it removed from the rotation and let me activate it myself or even if its only on boss fights it would be better than it going off on CD.

 

[Megapowen]

anyone tried arms or fury for warrior?

 

[kmolleson]

What Class+Spec are you?: Fire Mage
What 'context' is the bot in? (Instance, BG, Normal): Questing
What level are you?: 103
Have you made any modifications to Singular?: none
Are you using the Test Build of Singular?: no

What happened (be specific)? Singular properly uses Dragon's Breath to disorient melee ranged enemies, however, the CC will not begin casting a damaging spell until the CC breaks. Likely a preventative measure to keep from pulling CC'd mobs, it's a significant hindrance to the fire mage. I find that often, the mage will die in Legion while leveling by a nearly dead mob... which would have been preventable if it were taking the CC time to appropriately begin casting. An option to turn the preventative feature off for this spec/class or even smart logic (solo/in combat) would be immensely helpful.

 

[EchoTiger]

What Class+Spec are you?: Fire Mage
What 'context' is the bot in? (Instance, BG, Normal): Questing
What level are you?: 103
Have you made any modifications to Singular?: none
Are you using the Test Build of Singular?: no

What happened (be specific)? Singular properly uses Dragon's Breath to disorient melee ranged enemies, however, the CC will not begin casting a damaging spell until the CC breaks. Likely a preventative measure to keep from pulling CC'd mobs, it's a significant hindrance to the fire mage. I find that often, the mage will die in Legion while leveling by a nearly dead mob... which would have been preventable if it were taking the CC time to appropriately begin casting. An option to turn the preventative feature off for this spec/class or even smart logic (solo/in combat) would be immensely helpful.

This issue has been noted and should be fixed by the next Honorbuddy update.
Sorry, I haven't updated the issue tracker or the test build yet to include this.

I'm working on Singular issues today and will update the front thread with all of the changes I've made once I'm done.