Singular - A community driven All-In-One CC - v5

[Azhemoth]

Sounds great! What is the webpage of your github?

Request: Can you do something about the Survival Hunters explosive-trap-spamming-bug first??? (Pretty please... )

https://github.com/BosslandGmbH/Singular

The explosive trap has already been fixed, so you can get the update from GitHub as well.

 

[ZephyrMMO]

@EchoTiger maybe you can share the workload on the rewrite with the Author of the Zingular fork.

I have talked to Echo about this and I made a conscious decision to keep them separate as singular is more for general use and my end goal is more for gold farming purposes.

If they like my changes enough they are more then free to use them but I don't think the goals with singular are the same as mine with zingular which is why I decided to go this route.

 

[ZephyrMMO]

Sounds great! What is the webpage of your github?

Request: Can you do something about the Survival Hunters explosive-trap-spamming-bug first??? (Pretty please... )

Change the line

 Spell.Cast("Explosive Trap"),

To this

 Spell.CastOnGround("Explosive Trap", on => Me.CurrentTarget.Location),

inside Singular\ClassSpecific\Hunter\Survival.cs

 

[Azhemoth]

I have talked to Echo about this and I made a conscious decision to keep them separate as singular is more for general use and my end goal is more for gold farming purposes.

Echo's gold farming version of Singular is "Singularity" which was mostly focused towards gold farming in dungeons.
The name was a bit of a "pun-off" of Singular given that his Singularity version prioritized heavy AoE attacks for the very fast dungeon clear times.

I'm not sure if it still exists though.

 

[ZephyrMMO]

Echo's gold farming version of Singular is "Singularity" which was mostly focused towards gold farming in dungeons.
The name was a bit of a "pun-off" of Singular given that his Singularity version prioritized heavy AoE attacks for the very fast dungeon clear times.

I'm not sure if it still exists though.

That makes much more sense. Since that is more or less what I am doing with Zingular. Just prioritizing aoe / fast hitting spells but instead of dungeons It is made for open world farming.

 

[laria]

A WindWalker monk can split into three with storm earth and fire.
If the main copy kills its target , we totally ignore the fact that other spirits might still be in combat and don't assist them.
This looks weird and we should definately change that.

 

[MazahakaRnD]

I play the druid balance.
How can I rotate the rotation so that astral energy is considered, I have a maximum of 130, when it is complete, it continues to add it, how to make it rational.
Maybe you need to change something here?

private static long AstralPowerDeficit => Me.MaxAstralPower - Me.CurrentAstralPower;

// Rotation
Spell.Cast("Moonfire", on => Unit.NearbyUnitsInCombatWithUsOrOurStuff.FirstOrDefault(u => u.GetAuraTimeLeft("Moonfire").TotalSeconds < 1.8 && u.TimeToDeath(int.MaxValue) > 4)),
Spell.Cast("Sunfire", on => Unit.NearbyUnitsInCombatWithUsOrOurStuff.FirstOrDefault(u => u.GetAuraTimeLeft("Sunfire").TotalSeconds < 1.8 && u.TimeToDeath(int.MaxValue) > 4)),

Spell.Cast("New Moon", ret => DruidSettings.UseArtifactOnlyInAoE && DruidSettings.UseDPSArtifactWeaponWhen != UseDPSArtifactWeaponWhen.None && Unit.UnfriendlyUnitsNearTarget(8f).Count() > 1),
Spell.Cast("New Moon", ret => !DruidSettings.UseArtifactOnlyInAoE && DruidSettings.UseDPSArtifactWeaponWhen != UseDPSArtifactWeaponWhen.None),

Spell.Cast("Stellar Flare", on => Unit.NearbyUnitsInCombatWithUsOrOurStuff.FirstOrDefault(u => u.GetAuraTimeLeft("Stellar Flare").TotalSeconds < 1.8 && u.TimeToDeath(int.MaxValue) > 12)),

Spell.CastOnGround("Starfall", on => Clusters.GetBestUnitForCluster(Unit.NearbyUnitsInCombatWithUsOrOurStuff, ClusterType.Radius, 15).Location, ret => Unit.NearbyUnfriendlyUnits.Count() >= 3),
Spell.Cast("Starsurge", ret => Me.GetAuraStacks("Lunar Empowerment") < 3 && Me.GetAuraStacks("Solar Empowerment") < 3),

Spell.Cast("Solar Wrath", ret => Me.GetAuraStacks("Solar Empowerment") > 0),
Spell.Cast("Warrior of Elune", ret => Me.GetAuraStacks("Lunar Empowerment") >= 2),
Spell.Cast("Lunar Strike", ret => Me.GetAuraStacks("Lunar Empowerment") > 0),
Spell.Cast("Solar Wrath", ret => !Unit.UnfriendlyUnitsNearTarget(5f).Any()),
Spell.Cast("Lunar Strike", ret => Unit.UnfriendlyUnitsNearTarget(5f).Any())

Probably the answer will not be I'm running out of the license for the bot, I'm probably not going to renew it, is your program useless?

 

[darkilliminated]

Where do I find the settings to disable Auto-cast Water Walking for Shaman?

I can't find the code (whatever it might be) in the actual plugin folders either, and I'm either blind or blind because the option isn't on the GUI

Thanks in advance

 

[EchoTiger]

Where do I find the settings to disable Auto-cast Water Walking for Shaman?

I can't find the code (whatever it might be) in the actual plugin folders either, and I'm either blind or blind because the option isn't on the GUI

Thanks in advance

Sorry for the delay.
Do you have a log for when Water Walking is cast?

Its been a while since I've checked, but I don't think Singular handles water walking for Shaman given it causes issues for Questing.

 

[ZephyrMMO]

Sorry for the delay.
Do you have a log for when Water Walking is cast?

Its been a while since I've checked, but I don't think Singular handles water walking for Shaman given it causes issues for Questing.

P sure that it doesn't and it does cause a bunch of quest bugs. Afaik most of the water walking stuff is commented out unless you are in a battleground

 

[Lumenix]

May I am just stupid, but where can I find the current version?
Can just see those Test Builds.

Greetings

 

[EchoTiger]

May I am just stupid, but where can I find the current version?
Can just see those Test Builds.

Greetings

Current test build is outdated.
I'm getting ready for a huge revamp of the project though, so they will be active again soon.

If you want, you can join the Discord server - there I will be posting updates and status reports regarding it.

 

[Lumenix]

Current test build is outdated.
I'm getting ready for a huge revamp of the project though, so they will be active again soon.

If you want, you can join the Discord server - there I will be posting updates and status reports regarding it.

I currently have the Singular Combat Routine (which I've automatically installed with the installtion of Honorbuddy with the Installer).
At some point I have a few problems with attacking neutral/yellow monsters.
(Singular) Dismounting... Reason: Pull is the message that is spammed in the log-file, but I will attach it, so you can take a look.
The log is pretty big - just jump to line 6672 - beginning there.

Thank you in advance.
Greetings

 

[MazahakaRnD]

Singular does not attack bosses who are not half visible when you fix it ? Also, he does not attack if you go behind the obstacle when he does not see the boss .

 

[darkilliminated]

Sorry for the delay.
Do you have a log for when Water Walking is cast?

Its been a while since I've checked, but I don't think Singular handles water walking for Shaman given it causes issues for Questing.

All good, I found the issue - was embedded in one of my plugins, just deleted the code and got rid of the issue

 

[EchoTiger]

Singular does not attack bosses who are not half visible when you fix it ? Also, he does not attack if you go behind the obstacle when he does not see the boss .

I'm not sure what you mean by "half visible."

If a NPC is behind an object, then the bot won't attack it because the NPC is assumed to be out of the bots line of sight.

 

[Nevicarr]

I'm not sure what you mean by "half visible."

If a NPC is behind an object, then the bot won't attack it because the NPC is assumed to be out of the bots line of sight.

He did an awful job of explaining. There's a problem with this routine and Avatar on Tomb of Sargeras. The routine is useless the entire first half of the fight because it's claiming the target it out of line of sight, but it's clearly in range. Please fix this if not already addressing/fixed in an upcoming unreleased build.

[Singular] warning: movement disabled and not in line of sight of Fallen Avatar.EABB @ 0.0 yds

 

[EchoTiger]

He did an awful job of explaining. There's a problem with this routine and Avatar on Tomb of Sargeras. The routine is useless the entire first half of the fight because it's claiming the target it out of line of sight, but it's clearly in range. Please fix this if not already addressing/fixed in an upcoming unreleased build.

[Singular] warning: movement disabled and not in line of sight of Fallen Avatar.EABB @ 0.0 yds

This is most-likely not an issue in Singular, but an issue in the InLineOfSight API that Singular uses.
I'll forward the message to the others so they can see if there's anything that needs to be done with InLineOfSight.

 

[Nevicarr]

Thanks m8 you the real mvp in the house - doesnt seem to happen with my other routine but its a paid demon hunter one provided by Chillz.

 

[EchoTiger]

Thanks m8 you the real mvp in the house - doesnt seem to happen with my other routine but its a paid demon hunter one provided by Chillz.

No problem, and thank you. x3

The Chillz routine may work with it because the developer probably added an exception to their routine for that specific boss where it may ignore LineOfSight completely during that encounter.
This isn't really something we do on Singular because Singular isn't designed for anything "specific" such as raids. Singular is a completely universal combat routine designed for pretty much any/everything.

Having exceptions in Singular for raid bosses (or any other exception for whatever else) adds a lot more overhead to the code which can ruin the performance of the routine.
And only probably 12%~ of the users will even take advantage of these exceptions since a huge majority of the users use Honorbuddy for Questbot related things and not raiding specifically.

So instead, this issue is better addressed on a core level of the bot. That way Singular doesn't spend more resources on handling it.
I've messaged the others, and hopefully there will be a solution in the next update.