What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

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!

HB ARCHIVES: Singular--DO NOT DELETE

cevaps said:
My 90 Ret Pally never off-heals party members in 5-man dungeon. He's queueing as Healer. Settings are like this;
...
Also tried severeal other settings. Diagnostic logs are attached.
Click to expand...
Thank you for the post. Unfortunately Paladins are the last class the Off-Healing feature is to be added to. It will come at the same time as the Holy Paladin rewrite. Look for that in the next two weeks, -Bobby53
 
khadgarsserv said:
Hi I am having an issue with my 98 ret paladin in nagrand.
The bot keeps trying to use the garrison ability of the in combat mount. What happens is the bot keeps mounting and dismounting during combat and does this until he dies.
I posted in support first here https://www.thebuddyforum.com/honor...ort/193354-nagrand-talbuk-garrison-issue.html and they said I should come to this thread.
I am attaching my logView attachment 157736

How do I stop this behavior from happening?
I am using the singular profile with the wod questing 98-100 nagrand for ally
Click to expand...
khadgarsserv, Thanks for the post. You are using Singular v4.0.0.3991. The Garrison Ability should be fixed for the case you described in v4.0.0.4014 which is available for download from Post #1 in this thread.

Singular did have code in place in the version you were using to prevent casting the Garrison Ability when in Nagrand. The problem was that your botting session initially started in a different zone where Garrison Ability was overridden by Call to Arms and singular wasn't properly detecting a spell book change (Garrison Ability changing to Telaari Talbuk upon entering Nagrand.) So even though the Garrison Ability is not mentioned as being fixed in Change History for 4.0.0.4014, the specific variant of the issue you are having is fixed by it.

Thanks for the post and good luck with your Singular toons, Bobby53
 
Last edited:
bobby53 said:
khadgarsserv, Thanks for the post. You are using Singular v4.0.0.3991. The Garrison Ability should be fixed for the case you described in v4.0.0.4014 which is available for download from Post #1 in this thread.

Singular did have code in place in the version you were using to prevent casting the Garrison Ability when in Nagrand. The problem was that your botting session initially started in a different zone where Garrison Ability was overridden by Call to Arms and singular wasn't properly detecting a spell book change (Garrison Ability changing to Telaari Talbuk upon entering Nagrand.) So even though the Garrison Ability is not mentioned as being fixed in Change History for 4.0.0.4014, the specific variant of the issue you are having is fixed by it.

Thanks for the post and good luck with your Singular toons, Bobby53
Click to expand...

Is there any way to actually keep the bot Mounted in Nagrand?
 
davecach said:
Is there any way to actually keep the bot Mounted in Nagrand?
Click to expand...
Not while Questing. Although Singular will not cause you to dismount in Nagrand from one of those special mounts, other components are. To fully support, a change would need to be made to the Quest Behavior logic supporting Dismount to avoid dismounting when in Nagrand and mounted on one of the special mounts. Change to questing profiles may be needed if there are certain quests that cannot be picked up or objectives performed while on one of even those mounts. Similar change would likely be needed within Questing BotBase and possibly HonorBuddy, although that is a guess.

The option that would allow you to stay mounted and fight would be to use LazyRaider, RaidBot, or CombatBot with Singular which would require manual movement, but should allow you to remain mounted while in combat and automate your spell priority. -Bobby53
 
Last edited:
Im not happy with affliction warlock behaviour. It cast sequence on mobs is usually Agony --> Drain Soul --> Corruption --> Drain Soul --> Unstable Affliction --> Drain Soul.
While it should be casting Agony --> Corruption --> Unstable Affliction --> Drain Soul.
With a current sequence mob kill times are very long and the spec is extremely low on damage output.
I had a look at Affliction.cs file. Looks like it needs some updates, but I am not skilled to do it myself. Could someone help with the code please?
 
Holy Priest Healing in Molten Core LFR it's a 40man raid but Singular selects INSTANCES instead of RAID healing profile. Also Lightwell is never used. Also Guardian Spirit being used on DPS shouldn't happen in a raid I think. Log attached

View attachment 38852 2014-12-12 19.50.zip
 
Last edited:
bobby53 said:
No, not presently. Please elaborate on why that ability would be needed. Thanks, Bobby53
Click to expand...
For example during questing, currently have the issue that hb attacks other faction and they get angry and will hunt you down making your questing difficult...
 
Phelon said:
I haven't tried a fresh install, but no other CC has these issues.
Click to expand...

How many CC's are managing 11 classes and 36 specs, out of the box ?

Everything is listed "[P] Partially Working - Bugs or missing abilities. Works but less than optimal."

You didn't even provide a spec or log. Just curious, what would happen if i did the same for ultimate pvp suite ?
 
Hello.
Apparently logs don't split on start/stop. So here's ~7 hours arms warrior running grind bot. Besides the beginning it was afk, running pretty stable.
Maybe you can get some use out if it anyways. Has ~2500 Kills, ~2100 Loots and 10 Deaths... Not perfect but some statistical value at least :)

View attachment 6780 2014-12-13 06.46.zip
log marks below. (can't remember first one)

* #2-3. singular dropping mobs/thinking its left combat for some reason and just running from mobs. (think mobs are fleeing). Without high loot area set you potentially lose loot.
* #4. is singular choosing to pull with taunt. It forces defensive/battle stance switches. Besides pausing swing timer it shouldn't delay rotation (as they're off the gcd) but it looks ingame as its causing a delay for either singular or hb.
* The ilvl counter in the log is off by 7 ilvls (guessing its ignoring heirloom)
* Doesnt seem like the bot is using enraged regeneration or die by the sword while slowly dying.

Edit. The deaths are most likely all due to singular not seeing a mob is hitting you after blacklist.
Should probably override any block, if a mob is actively damaging/attacking you. Force a reload of behaviours or smt :)
 
Last edited:
*new* Singular v4.0.0.4064 available for download!

Quick list of notable changes:
- Spec specific default settings for Pull More
- Extensive fixes for Affliction Warlock in Normal (Solo) Context
- Fix for exception which was generating a lot of debug log overhead for DoT heavy classes
- Full list appears below

Reporting Bugs in Singular (click here): Spend the time following steps in the post linked here if you want me to spend the time reading and responding to your post. Remember, this isn't a general discussion thread. If you don't have a log attached, you shouldn't be posting in this thread.

Change History for v4.0.0.4064
General

*new* - Rest - added [Rest: Fight if Attacked] Class Config setting in Enemy Control section to control whether Singular fights back when attacked during Rest. Some BotBases do not call the CombatBehavior in this circumstance, so this setting controls whether Singular does on its behalf


fixed - Non-Combat Buffs - fixed check to consider Darkflight as being mounted to prevent casting abilities which cancel this aura for Worgen


fixed - Target Change detection - fixed occurrences when targeting something which is not a WoWUnit (non NPCs, non Players)


change- Pull More - more granular messaging describing to user when it is disabled automatically (based on context) and why.


change- Pull More - disabled for Restoration Druid, Holy Paladin, Discipline Priest, Holy Priest, Mistweaver Monks, and Restoration Shaman


*new* - Pull More - specialization specific defaults. Will now set the default max mob count allowed with Pull More based upon specialization ( 3 for tanking specs, 2 for most dps specs, 1 for rogues). These are defaults only and user setting will override.


fixed - First Aid - the Use Bandages ability now correctly detects new bandage types introduced with WoD


change- Debug Messages - have throttled some of the messages which were spammed to decrease overhead of logging


fixed - Position Mobs in Front - corrected so only invoked for melee toons when more than one melee attacker


fixed - Rest while Combat Bugged - will now suppress Eating /Drinking while in Combat


fixed - Debug Exception - error occurring while debug enabled causing large amount of log output and slower performance


fixed - Buff Logic - fixed error in Buff Casting logic which was causing some opportunities for Buff and Debuff casts to be missed. Most noticeable with Affliction Warlocks, to a lesser extent Shadow Priests


change- Auto Manual Movement Bot Detection - Enyo now detected as a manual movement bot


change- Pet Attack messages - reduced these when attacking same target. Additional work to come here to reduce chattiness of log window


fixed - Settings File Upgrade - now correctly detects past versions of log files and invokes upgrade logic to perform various setting adjustmetns, etc based upon new logic. Affects those upgrading from a past version


*new* - Evade Attacks Allowed - new setting (default 8) controls number of attacks on an NPC which miss due to Evading before the mob is considered Evade Bugged and blacklisted


change- Evade Missed Attack message - now clearly states that mob is not blacklisted and only counting Evades until exceeding previously described setting


*new* - Rest Combat Allowed - in Normal Context (Solo) when in the Rest behavior (non-Combat) most botbases do not consider being attacked by an Enemy Player to be in Combat and do not invoke the Combat Behavior. By default Singular will, but this setting allows you to disable




Druids


fixed - Feral - now only casts Faerie Fire on enemy Rogues and Druids in Cat Form


fixed - Worgen - Darkflight fix: will no longer cast Cat Form when Darkflight active until ready to Pull or attacked




Hunter


fixed - Marksman - fixed exceptions occurring when no current target selected




Monk


fixed - MistWeaver - no longer spams Stance of the Wise Serpent


fixed - MistWeaver - no longer spams Stance of the Spirited Crane


fixed - MistWeaver - added support for standard unbuffed Surging Mist in rotation. This was inadvertent deletion in WoD work which significantly impacted lower level Mistweavers and PVP




Paladin


fixed - All Specs - added support for Divine Purpose with Eternal Flame


fixed - Protection - prevent cast of Guardian of Ancient Kings unless in melee range of target


fixed - Protection - prevent cast of Avenging Wrath unless in melee range of target


fixed - Retribution - when Divine Shield active, will spam Flash of Light until buff ends or health above 90


fixed - Retribution - revised Holy Avenger and Avenging Wrath to not stack in Normal context (Solo)


fixed - Retribution - changed Divine Purpose handling to cast Divine Storm rather than Templar's Verdict when more than 3 mobs in range




Priest


fixed - Discipline - Solo: fixed so PW:S is reapplied during combat


change- Discipline - Group: if Glyph of Reflective Shield equipped, change targeting priority for PW:S to Tanks > Self > Healers > DPS if Priest has aggro




Shaman


fixed - All Specs - Elemental Blast: prevent second cast being queued immediately after first cast but before buff was applied or cooldown initiated




Warlock


fixed - Affliction - now correctly applies and maintains Corruption, Agony, and Unstable Affliction


fixed - Affliction - AOE now correctly applies and maintains Corruption and Agony on multiple mobs


fixed - Affliction - Soulburn / Soul Swap now corrected to treat this as a 2 Shard sequence


fixed - Affliction - Solo: Haunt how cast only if all DoTs exist on target and more than 2 Shards


fixed - Affliction - Drain Soul now correctly cast regardless of target health


fixed - Affliction - Shadow Bolt now correctly cast if Drain Soul not known


fixed - Affliction - Drain Life if health below configured value


*new* - Affliction - Drain Life Cancel % setting added to control at what Health % a Drain Life in progress is cancelled


fixed - All Specs - Soul Link no longer cast (since now a Passive ability)


change - All Specs - Drain Life for Healing is now only cast in Normal (Solo) and Battleground (PVP) contexts


fixed - Affliction - removed Soulburn for buffed Health Funnel (WoD)


fixed - Affliction - removed Soulburn for buffed Drain Life (WoD)


fixed - All Specs - error occurring in Pet Summon logic which prevented summoning demon
Click to expand...
 
Abyssion said:
I keep getting this error:

[12:47:31.777 N] (Singular) .... [REST] h=100.0%/m=100.0%, combat=N, evang=0, archa=0, spiritsh=0, borrtim=0, target=Me th=100.0%/100.0%, @ 0.0 yds, combat=N, tloss=True, pw:s=3399, renew=0, spiritsh=0

Causing my priest not to move AT ALL. Very frustrating
Click to expand...
After 280 posts, I am assuming you know how to post a log especially regarding behavior that makes you frustrated. Just in case you never saw this link before: Reporting Bugs in Singular (click here).

So no idea about any error you are encountering, other than to say the log line you copy/pasted does not indicate an error in Singular. It simply shows that the BotBase (whatever one you are using) is calling the Singular Rest Behavior. If you are continually resting and nothing else is happening, you will want to post in the Support thread for the BotBase you are using. If you have no idea where that is, then post in the HonorBuddy Support forum.

Combat Routines (which is the type of component Singular is) are slaves -- they can only do what the BotBase tells them to. In this case your BotBase is calling the Rest Behavior. The line shown is just a status message written to the log by Singular so when a user submits a log I can see that it was resting and what the current status of its health, mana, etc are. Based on this one line it looks like you are topped off on health and mana, so have no idea why your Priest is not moving but it is not due to Singular as it has nothing to do with Non-Combat movement. -Bobby53
 
Carbonated said:
Blood Death Knights: The Combat Routine refuses to use Death Coil several logs are attached.

No log-marks because it literally never uses it
View attachment 157985
Click to expand...
Carbonated - Thanks for the log. I'll take a look at this a bit later, but for now want to clarify the point of a LOGMARK. It is useful in identifying a point of interest in the log file that corresponds to what you are noticing and describing as an issue in game. In this case, where you are identifying a problem regarding something that never occurs it is critical because it would identify the point in time where you believe it should have occurred. Thanks for the post and look for an additional follow up by tomorrow, -Bobby53
 
daemon9 said:
Death Knights: Defile should be used during BOTH Single and Multi target encounters. Currently, Singular isn't using Defile at all during single target encounters.

View attachment 157986
Click to expand...
daemon9, Thanks for the post with log file. Priorities are based upon Noxxic by default, which do not indicate using Death and Decay or Defile in Single target encounters. If there is another spell priority you would like a spec to support, post a link and I'll happily add it once completing support / fixes for all specs in Singular (which is still in progress.) If you would like to discuss the necessity of Death and Decay and/or Defile in Single Target encounters, the best place for that at the moment would be the Noxxic forums. If they add it to the Solo spell priorities please let me know. Thanks for the post and good luck with your DK, Bobby53
 
You must log in or register to reply here.
Back
Top