Okay, realistically, do you expect me to fix the problem when that is all the information you give me? Me: My car is having problems not realising the engine is there. Mechanic: WTF! Mechanic: /CLICK [hangs up the phone] I have emphasised the points in the above analogy that I think you should take note of.
Has post # 210 (http://www.thebuddyforum.com/honorb...adin/12708-fpsware-paladin-21.html#post217464) been added to the CC yet? If not, is this CC still under development?
getting this: ~~ Character is a level 85 Paladin Current zone is: Дуротар Building spell book Spell book built You are a level 85 Protection Paladin ~~ Settings loaded Starting the bot! Chose Fpsware Paladin(0.0.1) by Fpsware as your combat class! Creating 'Rest' behavior Creating 'Pull' behavior Creating 'Heal' behavior Creating 'Combat' behavior Pull Max Distance set to 5 Pull Min Distance set to 3 This profile does not contain any profiles fitting the character! debug log: Code: [19:19:36:765] Compiling Z:\pvp_adds\HB\2.0.0.3956\CustomClasses\Fpsware Paladin [19:19:37:919] Activity: Initializing Flight Paths [19:19:55:827] Start/Stop button pressed. [19:19:56:60] Cleared POI [19:19:57:624] Inserting Сторож химической компании [Gossip] into the database! [19:19:57:875] Stop called! [19:19:58:186] System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.AbortInternal() at System.Threading.Thread.Abort() at Styx.Logic.BehaviorTree.TreeRoot.Stop() at Styx.Logic.Profiles.ProfileManager.get_CurrentProfile() at Styx.Logic.AreaManagement.AreaManager.get_CurrentGrindArea() at Styx.Logic.Targeting.() [19:19:58:189] System.Threading.ThreadAbortException: Thread was being aborted. at Styx.Logic.Targeting.() at Styx.WoWPulsator.Pulse(PulseFlags flags) at Styx.Logic.BehaviorTree.TreeRoot.() at Styx.Logic.BehaviorTree.TreeRoot.() [19:19:58:190] System.Threading.ThreadAbortException: Thread was being aborted. at Styx.Logic.BehaviorTree.TreeRoot.()
This is a profile message not a CC mesage. The profile you are using does not have anything useable for your level character. Use a different profile. A profile is a list of hotspots that tell your character where to grind and what to kill. A CC is code driven logic that tells HB HOW your character should fight.
Basically nothing else I could add. Honorbuddy doesn't know it is there, so obviously it doesn't even add it into it's logs. I'll try it again sometime and see what I can figure out. For now just continue on doing what you do.
As is stated in the very first post - log file or it didn't happen. Regardless of what you think, the information is in the log file.
well I talked to some people on the ptr and testing after the patch and they said something is very wrong. They dropped 20% from the pointer to live damage. All in 1 day rotation is still full of holes and overall a failure just like buzzard wants I guess. I tried it and I was only doing 7.8k on a dummy with 346 eq and you get L O N G pauses with NOTHING off Cooldown. My dk with crap eq can do 11K and his pet is doing 4k I am betting that FPS will have a rotion that will help a lot. OVERALL THIS PATCH IS A JOKE
This is not the place for generally Paladin discussions. What does this have to do with the CC or HB?
is there a solution to this yet? currently I have that problem on every 10th mob. help is much appreciated.
I love the CC, works great, but I do have one problem, when doing BG's it has a bad habit of targeting pets and not players.... is there anyway to fix it so it never targets pets and always targets the player? Pretty big issue, because no player would ever target a pet, only an AI would, so it's kinda a red flag saying "hey I'm a bot" ya know? That's the only issue I see with this CC, it works great, has very few deaths, except when massively outnumbered by horde, although would like to see it use Crusader Strike more on single targets as opposed to Hammer of the Righteous (lower dmg multi targets)..... But all in all it does a nice job.
Unfortunately CombatHelper likes to target pets alot of the time as well.... really need some kind of solution so the bots no longer target pets at all
Having issues with HB using BG Bot, and this CC, not all issues are CC related, nor are all HB related. During AB, several times char needed to stop and heal, eat, drink, but did not stop the bot. Bot continued on it's path to it's destination, wouldn't stop, ran into the enemy several times low on health, and mana. Trouble with aggro and pulling, several times, bot ran past enemy players within just a couple feet and never even looked at them, just kept going. Have tried with only the CC turned on, have tried with Combat Helper assiting, have tried other CC's, all are having same issues, just a guess, but may be something to do with new release conflicting somehow with old code of CC??? No clue really, just guessing. Below is log file, hope you can make sense of it.
None of the issues you have described are caused by the CC. 1. Healing/resting is handled properly 2. Targeting is handled by HB, the CC will blacklist any inappropriate targets pets, totems etc 3. Agro with pulling is caused by HB not the CC.
I have not seen this kind of behaviour in a long time. This was a bug in previous builds but was resolved a long time ago. I am doing some testing over the next 24 hours I will see if I can replicate this.
I may not have "described" them correctly, I just need someone to take a look at the logs, see all the problems that are in there, and figure out who is responsible for fixing it.... I didn't know where to post it, so I posted it under the CC, under the Profile, and under HB, hoping someone who knew how to read the log and understood what it all meant, would "get it where it needs to be". You say it's resting/healing correctly, it's not resting at all, yes it heals sometimes, when HB doesn't force the char to move for one reason or another. All I'm saying is that before this new patch hit, and a new HB was released, this CC was working perfectly, something has broken it. Monday working perfect, yesterday and today, no where near perfect. Programmers need to "be on the same page" working things together to make sure everything "plays nice" with each other. Devs from HB, CC creators, and Profile makers, need to all get together and see what works well with what, and what has issues, so that end-users like myself won't sit and wonder, "well where do I post this, or who do I tell this issue too?" When many people have a hand in making something, and an issue arises, they each say well it's this, or it's that, or doesn't have anything to do with what I did.... it sounds alot like politicitions passing the buck. Just with the way you responded tells me that all ya did was read what I wrote and didn't look at the log file. You just went on what I "Described".... I did find a few posts that said targeting was controlled by the CC because it controls combat. And if blacklisting a target that is standing right in front of my char is the "way it's supposed to function" then I see a problem, because that's what happened in that log file, targetting malfunctioned and enemy players were blacklisted and proceeded to destroy the botted char, because the CC would not fight back. This was posted here because I am not a programmer, I do not know what controls what I only go by what people post and tell me, thus I post the issue in all the relevant threads and cross my fingers that "the right" person will read it and either fix it, or get it to someone that can fix it. This is a great application in concept, but in the short time I've been here all I've seen and read is people posting "oh that's someone else's problem nothing to do with me", and it's getting annoying. The "good customer service" way to respond would be... "Thank you for lettings us know about this issue and we'll make sure to pass it on to the right people for a resolution." Not just say "oh it's not my problem" and "pass the buck". At this point I really don't care whose problem it is, if it's in the wrong spot, then move the thread to the right spot so that it can get fixed, I didn't know where to put it to start with, but when there are lines in the logfile that specifically say "fpsware paladin line blah blah" then it makes ya think there a communication problem between the CC and the Bot. Which we all know if they ain't talking, it ain't workin'. If it ain't yer problem fine, it ain't yer problem, just please, give the log file to whomever's problem it is so they can read it and find the cause and fix it. I'm sorry if I'm coming off abit harsh, but when I drop just over 100 US $$ on a piece of software, I expect it to work, and when it don't I expect those folks that are involved in it's function to work together to make it work. And when folks say "post a log and we'll look at it" , and I do, I expect folks to sit and read thu the log since they asked for it. I'm thrilled that some folks are having no issues at all and it's working flawlessly, but not all people are the same, not all computers are the same, and more times than not, even when the everything IS the same, sometimes things still go wrong and they break. It's called "Murphy's Law" "Anything and everything, can, and will, eventually go wrong, even when it's right." Thank you.
Thank you for your well formed and informative post. I appreciate the time you've taken and the way you have gone about getting your point accross. After reviewing your original post and going through your log file again I can help you in the following ways.... 1. A link to the HB ("Buddy") bug tracker Buddy Bugtracker Main Page There is where you need to report all HB ("buddy") related issues. 2. I have taken 2 Pallys into BGs for testing. HB is not selecting the most appropriate target to attack/pull. This is not uncommon and has been reported in the past. HB chooses the target to attack, and the CC performs the necessary actions to make it happen. After 2 hours of testing I didn't see the character "not heal' All healing and combat appeared to perform correctly. The CC will fight back against all PVP characters 3. I saw 1 line in the log file that indicates a error thrown by the CC. This is a minor error and nothing to worry about. From the log file the CC appears to opperating without fault. 4. I understand you paid $100 for this bot, but you paid nothing for my CC. I am not a paid developer for HB, this CC is my own work and I offer it to the community on an "as-is, no warranty" basis. The only CC(s) you have paid for are the default CCs distributed with HB. 5. I believe I have indicated in the first post this CC is intended for PVE opperation ".. but it may work in PVP" 6. Don't take my original post to mean "I simply don't care about your problem". I support 8 CCs, a wife, a 7 year old daughter and a life. If I can answer posts with a simple answer, using as few words as possible I will, and then I'll move on to the next 20-30 question. At this point there is nothing more I can offer.
Thank you for your considerate reply, it is much appreciated, as I now know more than I did previously. 1st Did not know that you were not paid for your work, figured you were part of the staff since a couple of the default CCs that ship with HB were yours, or at least they had a fpsware filename. 2nd With HB actually "choosing" what targets to attack, then the CC carrying out the order to attack, am I safe to assume that it is HB that chooses when to move to the next target? And if it moves too soon it could interrupt eating, drinking, or healing actions that are being attempted by the CC? Thus resulting in the "appearance" of a malfunctioning CC? (In other words, HB said move, but the CC wasn't finished casting a heal or eating/drinking yet, and HB moved anyway). 3rd I too have a wife, and my daughter is 14, so enjoy the young years while you can, because the teenage years can be pure hell, mine is 14 going on 40 and she thinks "she's" the boss, lol. And finally, even tho your CC is intended for PvE, the experience I had while using it with HB builds 3804, 3881, and 3956 were pure perfection, it tore thru horde and alliance alike much better and more effiecently than my mere human hands could. It is possible that build 4001 just doesn't "play well with others"... Whatever the issue with HB is, or might be, hopefully the "powers that be" will figure it out soon and resolve them, so all things will be right in the universe once again. On a side note, you may be happy to hear that your Rogue CC tears thru horde like tissue paper at level 85, it utilizes almost all of the abilities it has at it's disposal and does so very effectively. I played with it for about an hour in Arathi Basin today and laughed so hard at how many horde players it took to "take it out" I almost cried..... after ripping apart a paladin, shaman, and druid, finally 2 mages kited it to death. I never knew it was possible to "stunlock" a druid, until i watched your CC do it... and I've been playing rogues since WoW was in beta so many years ago. All in all, this is still a learning process for me, and I'm sure there will be things that come up in the future that I won't be able to tell if it's HB, the CC, the Profile, or just "Murphy's Law" causing the issue. Hopefully I'll manage to "get it where it goes" on the first try. Thank You.
