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!
all classes have been fully updated for Legion, however they have not been fully tested or cleaned up!
any issues under "Fixed Issues" will be availible in the next Honorbuddy update or on the test build of Singular!
Current Class+Specialization Status
Color Key Red - Unsupported. Orange - Supported. Untested. May have rotation issues. May not use some talents. Green - Supported. Tested. Optimal rotation. May not use some talents. Light Blue - Supported. Tested. Exceptional rotation. Full talent use. Dark Blue - Supported. Tested. Fully optimized rotation. Full talent use. Extra functionalities included.
a guide on how to report issues found within Singular
When you come across a bug in Singular, the first thing you'll want to do is logmark the issue.
This will put a stamp in your log that will show me where the issue is occurring within the log.
To Logmark; To generate a logmark, follow these steps:
Click the "Class Config" button on Honorbuddy
Wait for your issue to start occurring.
Once the issue occurs, click the "LOGMARK!" button at the bottom of the "Class Config" menu that appeared in step 1.
After you've logmarked the issue, the next step is to upload your log to this thread here.
When you do, be sure to explain the issue you're having in as much detail as possible.
To make things easier for me, when you upload your log - also answer these questions on your post:
What Class+Spec are you?: What 'context' is the bot in? (Instance, BG, Normal): What level are you?: Have you made any modifications to Singular?: Are you using the Test Build of Singular?: What time (HH:MM:SS) or LogMark did your issue occur? What happened (be specific)?
If you do not know how to attach your log, then follow the steps in this guide: How to Attach a Log File
Why do I have to buy combat routines because Singular isn't good enough for my needs?
Singular is meant to be a completely universal combat routine. It's not meant to be a high-end PvP or a "DPS topping" PvE routine.
It is designed to work in under any circumstance and it's designed to work for every class + every specialization.
Singular is a "It Just Works" routine for every function in the bot.
Some example functions being: 1-110 questing, solo dungeon/raid farming, mount farming, ore+herb farming, etc.
"Why not add high-end PvP or chart topping DPS support?"
Given Singular is designed to work for every specialization - this alone means it takes a tremendous amount of development time to maintain absolutely every specialization.
Also, having actual testers for every specialization and have them at various levels can be a bit of a time-hog as well.
Most combat routine developers struggle keeping up with 6 different specializations designed specifically and only for PvP.
That's a huge difference when you consider Singular is designed to support all 36 specializations for PvP, PvE, Solo, Questing, etc
With that said, to make all specs designed for high-end PvP or chart-topping DPS would be impossible for me alone to do.
And to favor a single class (or specialization) wouldn't be right. I plan on putting an equal amount of effort into all specializations in Singular.
What is the "Test Build" and how do I use it?
Singular is only updated when Honorbuddy is updated.
The test build is a compiled ZIP of my developer branch, so it includes all my changes to Singular before Honorbuddy is updated to include them.
If you want to use the Test Build, simply download it and extract it into your "Routines" folder.
When you start Honorbuddy up, two Singular options will appear.
The test build will always be version 0. eg: v0.0.0.XX
The official build will always be version 5. eg: v5.0.0.XX
For the test version, the last few numbers will be populated with the SVN version.
If you look at the download button, the current SVN version is listed here - you can use this as reference to see if your Test Build is out of date.
Simply choose the test build and you should be good to go!
This combat routine is community driven, so how do I contribute my code?
Currently there is plans to setup a user-contribution branch for Singular, or to setup a developer site where you can contribute snips of code, but this is still a WIP.
If you have something to contribute, simply post it to this thread and I will look into merging it for you!
Credit will be given in the commit message so that your name will show up on the next Honorbuddy changelog message.
I may also setup a "Hall of Fame" for people who actively contribute so to credit them!
Does Singular support Legion, and will it support Artifact Weapon usage?
Yes, and yes!
Currently Singular is updated to fully support all class specializations in Legion. However, some have not been tested yet!
Once Legion comes out, Singular will be updated to support all Artifact Weapons as most of them act as an entirely new "spell" that can be included into your rotation.
What are "contexts"? Singular seems to say "Instance" "Solo" or "PVP" when I enter groups or battlegrounds.
Singular has the ability to detect and change its rotation or behavior depending on what environment it's in.
So for example: if you go into an instance, Singular will see this and try to detect your group role.
If you're assigned as DPS in the group role, it will use the Instance rotation for DPS.
Often, the Instance rotations will be different than for example: the Solo(Questing) rotations.
The same occurs for Battlegrounds.
If you go into a Battleground, Singular will detect this and use more PvP oriented attacks or behaviors.
Anytime a context is changed, Singular will tell you in Honorbuddy's log. An example would be:
[20:40:59.508 N] [Singular] Context: using Normal (SOLO) behaviors since not in group
There are some caveats where Singular will use (SOLO) behaviors instead of Battleground behaviors in zones like Ashran.
Ashran is indicated as a World PvP zone and not a battleground. So being inside of Ashran will trigger the solo behaviors instead of Battleground behaviors.
Bobby53's original answer:
"Singular's behavior selection attempts to base the decision of what behaviors to use (solo, pvp, instance) on what you are trying to do rather than solely on where you are. Instance behaviors attempt to fulfill your role in the group and trust that other group members will fulfill their roles as tank, dps, and healer as expected keeping the group alive. The key there is Role. If you have a group role assigned to your character then Instance behaviors are selected. If you are in a group and inside an instance, it also assumes this was done with a group purpose in mind so uses Instance behaviors. If you are in a World group and do not have a role assigned, then it assumes the group was formed solely to be able to see location of group members on a map, share kills if you are coincidentally near each other, etc. but that you will not depend upon others in the group so will heal yourself, expect to take aggro and avoid abilities that could cause you to lose a mob kill, etc.
Singular always indicates on a Context change how it chose the selected behaviors. Here is the entry from the Context change that occurred when your toon entered Ashran:
[20:40:59.508 N] [Singular] Context: using Normal (SOLO) behaviors since not in group
There is more to it, but that is the basics of current context detection logic. As for battlegrounds and arena, those always use the PVP behaviors. In this case, Ashran is indicated as a World PVP zone and not a battleground, so not being in a group resulted in Solo behaviors being used. -Bobby53"
I constantly get caught in an seemingly endless loop of casting "Healing Touch" on my feral druid. Putting up the HoTs from Regrowth and Rejuvenation plus using the talented Swiftmend would solve this.
Right now I'm picking at each spec with a toothpick to clean out old/bad/leftover code and to hopefully improve some rotations in the process.
I'm still taking rotation contributions, but processing them and getting them merged after testing may be a bit slow.
I'll see about getting all the current contributions and reported issues addressed by the next Honorbuddy update assuming there's not a ninja-patch!
Thanks for all the reports + contributions so far everyone!
Updates will be rolled out this week. I'll try to make announcement posts here for people that are subscribed so they can grab test copies!
Thanks again for the contributions so far everyone!
not sure if I am posting to right place. Thing is - Blood DK start using pull more only since 108 level. Until that level it simply ignores PullMore settings from singular. I get things in log like:
[19:52:40.192 D] Stopped moving.
[19:52:40.238 D] Dismount for attacker.
[19:52:40.243 D] Stop and dismount. Reason: Combat
[19:52:40.518 N] (Singular) (Singular) info: 5.4 seconds since BotBase last called Singular (now in Heal)
[19:52:40.582 N] (Singular) (Singular) Pull More: attacking non-trivial Mob Rampaging Squallhunter.C446 #107469 maxhealth 1558901, disabling pull more until killed
Sorry for the delay.
What are your pull more settings set to?
From what your log is showing - it is pulling more, but disabling the pull more until the existing one is killed.
That leads me to believe your pull more is only set to pull 1 extra mob.
Hello, any way to make singular use Rejuvenation and Swiftmend? my bot keeps dying as it only uses regrowth and some other CDs but it doesn't use rejuvenation or swiftmend. Kind regards
