Bobby, Thanks for your work on singular! Having some trouble still with bot not defending itself. 90 disc priest in party using grind bot. Gets attacked and stand there till party member bails it out or I die hope log helps.
I won't be able to get you a log until i get iLvl 460 so i can do LFR.. but i experienced an issue on my now banned account a few weeks ago. All went well until i reached Elegon.. and then none of my damage characters where attacking elegon. Maybe someone else could mimic the issue in LFR?
Ruinit, Sorry for your issues and thanks for the log file! The only thinkgadditionally I need is to know when the behavior you described occurred. That would be a specific time or a LogMark added to the file. That info is always important, but is vital when the issue is regarding something that did not happen. The current Disc implementation lacks the diagnositic output that is logged by most other classes, so I cannot be certain what caused the behavior you observed. My guess is that your Mana % dropped below 70% which is your current setting for DPS Mana in Class Config. This setting controls at what mana % your remaining mana should be preserved for healing and applies only while in a group. That is why your group member bailing out corrected the behavior. For what you described you should probably set to 0%. Just remember to set to a higher value if you run a Instance. Good luck with your Priest, Bobby53
tumbum, Thanks for the post! That is not current behavior designed into Singular, but a good suggestion. I'll look at trying to add something to address that. Also, there was a revision in the prior release to targeting which may have influenced one of your prior reports. How are your dailies going since the last release? -Bobby53
Thank you for your reply.... the Dailys running smooth now till the latest release. But i saw some little speed/timing issues with my Shaman and LFR. He casts his (ele) rotation and sometimes there is a little 2-3 sec. hick up where he waits till he recast a spell. If i play with hand its possible to cast in this seconds. will try to get a log next wednesday, maybe you can take a look. best regards
UFCFreak89, Possibly, but impossible to know without a log file. I'll keep an eye out for others reports, but would need that detail to look into further. Thanks, Bobby53
EpicXss, Thanks for the post but that's not enough detail. Please see Reporting Bugs [CLICK HERE] for a description on how to post regarding a bug/issue/question. Word of Glory gets cast as follows: Eternal Flame is cast by virtue of it being an override of Word of Glory, so if you take that talent casts will appear in your log as Word of Glory. Happy to look into this further but will need a complete debug log file as described in Reporting Bugs. If you are generating a log file to post for this or other issues, perform the following steps: This will produce a log file that outputs status information about the condition of the fight and your Paladin that will be needed to understand the reason for the symptoms you described. Thanks for the post and good luck with your Paladin, Bobby53
In the log I posted this is when it happened 15:07:44.775 D] We died, Clearing current POI Also to test your low mana theory I set health and mana to 10 and watched the toon it did the same thing at 80% mana. Doesn't even try to heal itself just stands there getting beat on. Also notice that when the party toon killed the mob that was attacking my priest. The priest immediately healed itself and ran over to loot the corpse.
HP < 50% and 3+ Holy Power OR Divine Purpose active HP < 25% and 2 Holy Power HP < 15% and 1 Holy Power That explains it. In settings, class specific, common we have the option for changing the treshold for word of glory. I would like to use it under that level regardless of charges.
@Ruinit: Thanks for helping a fellow Singular User with an accurate response. +rep -Bobby53 @Mario27: The lines saying UseItemOn-v479(debug) are issued by the UseItemOn quest behavior, announcing that it is about to use an item on a mob named 'Wayward Ancestor'. The next line is the output of the HonorBuddy Navigator class where UseItemOn is attempting to move towards the Wayward Ancestor. Being unable to generate a path in this case is an issue with either the navigation mesh, the HonorBuddy Navigator, the UseItemOn quest behavior, or the installation it is being run from. Thanks for the log file and good luck with your questing, Bobby53
EpicXss, Will gladly look into that after getting the details about your usage requested earlier. Thanks and good luck with your Paladin, Bobby53
What Class+Spec are you?: Rogue Ass What 'context' is the bot in? (Instance, BG, Normal): Grinding What level are you?: 90 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? Not sure, but it's the very last thing going into the log termination, lots of attempts to Ambush + Pickpocket but it's behind the mob. What happened (be specific)? It approached a Shao-Tien Soul-Render from the front and tried to pickpocket + ambush, it kept spamming in the log that "You must be behind your target" Did you attach a complete debug log? (choose one: YES or YES) YES
TC9869, Thank you for the well written post with complete debug log attached! You are currently using: That issue was resolved in a later release. You can download the most recent release from Post #1 of this thread. Thanks for the post and good luck with your Rogue, Bobby53
is there a way that i can fix this? because it just keeps standing stil it doesend do anything once it does those could not generate path from because i can never leave my pc when im botting or els it wil just dc from wow because it keeps standing stil. its that the char was not close to the quest that he needed to do in njade forest so i moved to that place and then he didnt do the cant generate spot blacklist anymore what is weird
Combat log of not using word of glory/eternal flame. In class specific/common I set the treshold to 90. It never cast it even at some point I am below 44% [28.824 N] [Singular-DEBUG] .... h=82.3%, m=94.6%, moving=False, hpower=0, grandcru=0, divpurp=0, sacshld=0, mobs=1, Prince Tortheldrin.3572, 17.0%, 3.7 yds, threat=255% loss=True [28.826 N] [Singular] Casting Crusader Strike on Prince Tortheldrin.3572 @ 17.0% at 3.7 yds [28.827 D] [CGSpellBook::CastSpell] Override ID: 35395, KnownIndex: 37 [30.323 N] [Singular-DEBUG] .... h=82.3%, m=98.5%, moving=False, hpower=1, grandcru=0, divpurp=0, sacshld=0, mobs=1, Prince Tortheldrin.3572, 13.6%, 3.7 yds, threat=255% loss=True [30.325 N] [Singular-DEBUG] CanCast[Crusader Strike]: still on cooldown for 2910 ms [30.326 N] [Singular] Casting Judgment on Prince Tortheldrin.3572 @ 13.6% at 3.7 yds [30.327 D] [CGSpellBook::CastSpell] Override ID: 20271, KnownIndex: 45 [31.820 N] [Singular-DEBUG] .... h=60.8%, m=93.8%, moving=False, hpower=2, grandcru=0, divpurp=0, sacshld=0, mobs=1, Prince Tortheldrin.3572, 10.7%, 3.7 yds, threat=255% loss=True [31.821 N] [Singular-DEBUG] CanCast[Crusader Strike]: still on cooldown for 1413 ms [31.822 N] [Singular-DEBUG] CanCast[Judgment]: still on cooldown for 4413 ms [31.823 N] [Singular-DEBUG] CanCast[Avenger's Shield]: still on cooldown for 8912 ms [31.823 N] [Singular] Casting Consecration on Prince Tortheldrin.3572 @ 10.7% at 3.7 yds [31.824 D] [CGSpellBook::CastSpell] Override ID: 26573, KnownIndex: 36 [33.318 N] [Singular-DEBUG] .... h=60.8%, m=93.5%, moving=False, hpower=2, grandcru=0, divpurp=0, sacshld=0, mobs=1, Prince Tortheldrin.3572, 7.0%, 3.7 yds, threat=255% loss=True [33.321 N] [Singular] Casting Crusader Strike on Prince Tortheldrin.3572 @ 7.0% at 3.7 yds [33.322 D] [CGSpellBook::CastSpell] Override ID: 35395, KnownIndex: 37 [34.831 N] [Singular-DEBUG] .... h=44.0%, m=96.7%, moving=False, hpower=3, grandcru=0, divpurp=0, sacshld=0, mobs=1, Prince Tortheldrin.3572, 4.7%, 3.7 yds, threat=255% loss=True [34.833 N] [Singular] Casting Shield of the Righteous on Prince Tortheldrin.3572 @ 4.7% at 3.7 yds [34.834 D] [CGSpellBook::CastSpell] Override ID: 53600, KnownIndex: 54 [34.917 N] [Singular-DEBUG] CanCast[Crusader Strike]: still on cooldown for 2818 ms [34.917 N] [Singular-DEBUG] CanCast[Judgment]: still on cooldown for 1317 ms [34.918 N] [Singular-DEBUG] CanCast[Avenger's Shield]: still on cooldown for 5816 ms [34.919 N] [Singular-DEBUG] CanCast[Consecration]: still on cooldown for 5818 ms [34.920 N] [Singular] Casting Hammer of Wrath on Prince Tortheldrin.3572 @ 4.7% at 3.7 yds [34.921 D] [CGSpellBook::CastSpell] Override ID: 24275, KnownIndex: 43 [36.363 N] [Singular-DEBUG] .... h=62.4%, m=100.0%, moving=True, hpower=0, grandcru=0, divpurp=0, sacshld=0, mobs=1, Prince Tortheldrin.3572, 0.0%, 4.3 yds, threat=0% loss=True [36.364 N] [Singular-DEBUG] CanCast[Hammer of the Righteous]: still on cooldown for 1384 ms [36.365 N] [Singular-DEBUG] CanCast[Crusader Strike]: still on cooldown for 1384 ms [36.366 N] [Singular] Casting Judgment on Prince Tortheldrin.3572 @ 0.0% at 4.3 yds
Mario27, Was going to review the log file again for to advise on versions in use, but the post containing the log for this issue appears to have been deleted. As for a fix or support for the questing behavior and UseItemOn, you'll want to post in the HonorBuddy Support Issues forum or the support thread for the questing profiles you are using. An although this issue is not related to the Combat Routine, you mentioned not encountering the issue with CLU so while awaiting a change to the quest profile/behavior it sounds like that is a viable option for you. Good luck with your questing, Bobby53
