So this is a 1 man farm and you get around 40k per day on say a level 100 with some gear from legion trial? not too shabby considering gold prices, but ofc.. a bit less than a way more expensive legion account. Is it completely AFK, like could i leave it from wednesday to tuesday and just sell gold? I assume a retri pala, feral druid or dk would be really good here, or is prot prefered?
I hit the start in the fireland. my toon finished first run and went to acherus through death gate. Then open the flight map and doing nothing. What is wrong? Korean version client could be a problem?
Zojak. How can i prevent my Dk from mining, whenever he is minning at the end of the profile he is directly in Shannox's moving path and then my dk dies and the profile stops. I liked how v0.5 worked never had to babysit it. V0.7 a different story
it should not be a problem however if you are above lvl 100 it could mess up i have a proflie posted a while ago try this and you should be good
Allright guys, this morning my bots (5 of them, 24/7) all simultaneously got banned running this profile. I'm not in the least surprised of course; I was testing the limits. Didn't care much for them anymore, so I sent them on a suicide mission. It only took 2 days for them to catch a hammer, so you're all warned, don't run this 24/7. my next crew of bots (5 level 100) will be composed of the best AoE and self-healing specs, and i'll be logging their gph. I'll report the best performing spec, and the gph. Anyway. I got a question for you, Zojak, if you wouldn't mind answering. I'd like to know for sure that the 24/7 part got me banned, and not something suspicious about the profile. How much random elements are incorporated into this profile? Are the wait times random? What about the move locations? My programming fu isn't advanced enough to find it in the code. Either that, or there isn't any. Thanks in advance.
there are not much rnd elements in there ... anyway blizzard is not stupid such things like random movement is not stopping them from banning you
Very interesting. My situation is very similar, as they got banned 9 days after creation, and also 2 days into the farm. I propose that all of us who got banned doing this profile chip in with all the information we have, in order to look for the common pattern. Here's a detailed description of the 9 days: All 5 accounts ran from the same IP and game folder. E-mails were of the form X@cartelera.org; a not well-known throwaway e-mail generator. Because of the gold price, I chose NA Illidan, horde. I ran 5 orcs; a monk tank, a shaman healer and 3 hunters. Names were generated using blizz name generator. I handleveled them all to 20, because my buddy told me there are wires all over 1-20 questing, and they'd probably get banned before even reaching level cap. I threw them into dungeons until 90, about 18 hours a day, for 3 days. In order to gear them for warlords dungeons (average item level 500), I used the default Draenor questing profile for 90-92. After that, thrown into dungeons till 100 again. They ran heroics for about 3 days, but they really sucked at doing it. They constantly wiped, and Honorbuddy + Singular was so, so bad at healing with shaman. On top of that, there were a bunch of bugs in the warlords dungeons. meshes getting fucked up, tacts being heavily fumbled, etc... I tried tweaking them a lot, but they only ever did a mediocre job. The monk was fucking MVP though. The hunters were allright, the shaman was complete dogshit. I quickly realized that smashing heroics no longer worked in legion (either that or my group just sucked), so i resolved to simply use them to experiment. I loaded this profile and made them use it 24/7. 2 days later they were all dead, and from the looks of the log, almost at the exact same time. My banker, whom I also logged on the same IP and game folder, was left untouched. The gph was very good. The monk had a solid 1500-2000. The others were kinda shitty because they lacked either reliable self-heal (hunter) or AoE (shaman). Died about once an hour. Probably about 800-1000 for them. That's about all I can say. Let's get to the bottom of this, shall we? +-1800 gph for a battle chest account is damn good, multiplied by 5 if a configuration is made where everyone is as insane as that monk. Anyway, everyone who got banned that had anything to do with this profile, write your experience here. Let's find the pattern. It's blatantly obvious they were banned by the Warden algorithm, so we can outsmart this. PS. Did you play on a PvP server, gruby? I got a feeling that might be a clue. I saw a lot of skeletons outside the instance, I don't think it's entirely impossible somebody reported them after fucking around with them, and realizing they were bots. Be sure to include the run-time/day of your bots. It might be as easy as programming them to take breaks.
The way you get banned is by inciting an initial investigation, so you will very rarely get banned for just running a bot., you have to look suspicious first, and once you pass a certain treshold, the RAM gets scanned, and the banhammer is already on the way to your face in about a day. If you feel like working on the profile again, I got some suggestions: - Make the hotspots random. Instead of a fixed value, move to a random point in a 1 yard circle. I've heard many rumours of fixed points being a flag. - Make the wait times random. I've noticed the wait time per reset is always (6.05 minutes - time of previous run). Adding a few random seconds to that might be a good idea. Also, I'd recommend to get rid of the Shannox problem once and for all, by: -measuring his patrol path, and adjusting the hotspots so it's absolutely impossible he gets pulled. -If he does get pulled (by for example, a multi-shot), add a line of code that scans for him being in combat, which makes the bot stop doing ANYTHING until the toon dies. This is of course, entirely up to you. If you don't feel like working on it anymore, that's also fine. I'm planning on leveling my programming fu, so me and my buddy might actually take this profile and give it a makeover once I know the ropes of this particular code. Peace out guys. Stay awesome.
Yeah I play on PVP server. However i've been using druid moonglade + dk death gate. Did not run outside instance. But few days ago I have seen people that were ganking bots (outside everbloom and in moonglade where druids teleport). I always turn off bots when those people are there but they still may report players that are in firelands for days etc.
as said before blizzard is not stupid they will ban you even with rnd hotspots. if you check the ban section (btw all ban report should be posted there) there are many diffrent ban reports for various farmspots
guys... blizzard detect HB easily... its not profiles or anything like that.. they just see who is using bot. if you are using more then 1-2days - you can say goodbye to your account.. also they are checking how old and "playable" your account is. for example I did bot on 3 legion accounts and on 1 main acc. 3 got banned in 1 time and main account still alive, but same hard-botted as previous 3.
I have a problem.. v0.6 working (but stuck at Archerus) on HB 3.0 but 0.7 cant even start... Diagnostic: Code: Changing current profile to Firelands Multi Profile V0.7 Hardcore no gbank Profile loaded successfully! Starting the bot! Currently Using BotBase : Questing Character is a level 110 Tauren DeathKnight Current zone is Mount Hyjal (http://wowhead.com/zone=616) [SpellManager] Adding known spells: Anti-Magic Shell (048707) | Armor Skills (076282) | Artisan Riding (034091) [SpellManager] Adding known spells: Asphyxiate (221562) | Auto Attack (006603) | Blood Boil (050842) [SpellManager] Adding known spells: Bonestorm (194844) | Brawn (154743) | Cold Weather Flying (054197) [SpellManager] Adding known spells: Combat Ally (211390) | Consumption (205223) | Control Undead (111673) [SpellManager] Adding known spells: Crimson Scourge (081136) | Cultivation (020552) | Dancing Rune Weapon (049028) [SpellManager] Adding known spells: Dark Command (056222) | Death and Decay (043265) | Death Gate (050977) [SpellManager] Adding known spells: Death Grip (049576) | Death Strike (049998) | Death's Caress (195292) [SpellManager] Adding known spells: Endurance (020550) | First Aid (010846) | Flight Master's Li.. (090267) [SpellManager] Adding known spells: Garrison Ability (161691) | Gorefiend's Grasp (108199) | Heart Strike (206930) [SpellManager] Adding known spells: Honorable Medallion (195710) | Languages (079746) | Mark of Blood (206940) [SpellManager] Adding known spells: Marrowrend (195182) | Mastery: Blood Shi.. (077513) | Mind Freeze (047528) [SpellManager] Adding known spells: Nature Resistance (020551) | On a Pale Horse (051986) | Path of Frost (003714) [SpellManager] Adding known spells: Raise Ally (061999) | Runeforging (053428) | Vampiric Blood (055233) [SpellManager] Adding known spells: Veteran of the Thi.. (048263) | War Stomp (020549) | Weapon Skills (076292) [SpellManager] Adding known spells: Wisdom of the Four.. (115913) | Wraith Walk (212552) [Singular] Hotkey: To add a LOGMARK, press: [Shift+Alt+Ctrl+M] [Singular] Your Level 110 Tauren Blood Death Knight Build is [Singular] ... running the Questing bot in Mount Hyjal [Singular] ... Zone: Kalimdor using my SOLO Behaviors alone Updating repair cost for current equipped items. New value: [2g98s53c] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. This Profile contains hardcore pullroutine Goal: Nothing Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Inserted new hook [Questbot_Main @0] c23c7056-76b1-4bbd-ab00-17c153aed16b [Azyul Death Handler]: v2.0 - Enabled Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Enabled EchoTigers Dungeon/Raid Death Support with Reset on Death. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior Bots.Quest.QuestOrder.ForcedIf. Unable to evaluate/compile condition in If tag. Please check your profile. Honorbuddy stopped System.NullReferenceException: Object reference not set to an instance of an object. at __CompileBatchNamespace6__.__CompiledBatchClass__.HearthIsPriorityLocationKalimdor() at __CompileBatchNamespace6__.__CompiledBatchClass__.<__ExpressionFunc__4>b__18_0() at __CompileBatchNamespace6__.__CompiledBatchClass__.__ExpressionFunc__4() at lambda_method(Closure ) at Bots.Quest.QuestOrder.ForcedIf.OnStart() Bot stopping! Reason: Unable to evaluate/compile condition in If tag. Please check your profile. Done with forced behavior Bots.Quest.QuestOrder.ForcedIf. Starting behavior Bots.Quest.QuestOrder.ForcedIf. Done with forced behavior Bots.Quest.QuestOrder.ForcedIf. Starting behavior Bots.Quest.QuestOrder.ForcedIf. Done with forced behavior Bots.Quest.QuestOrder.ForcedIf. Starting behavior Bots.Quest.QuestOrder.ForcedWhile. Starting behavior Bots.Quest.QuestOrder.ForcedIf. Done with forced behavior Bots.Quest.QuestOrder.ForcedIf. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Goal: FlyTo-FlyTo.: In Progress (no associated quest) [Ref: "Firelands Multi Profile V0.7 Hardcore no gbank" @line 526] Behavior flags changed! All -> Death, Combat, Vendor, Roam, Rest, FlightPath [FlyTo-FlyTo.(debug)] WaypointVisitStrategy set to PickOneAtRandom Goal: FlyTo-FlyTo.: In Progress (no associated quest) Flying to '<3987.989, -2944.655, 1002.547>' (<3987.989, -2944.655, 1002.547>) [Ref: "Firelands Multi Profile V0.7 Hardcore no gbank" @line 526] Activity: Flying to '<3987.989, -2944.655, 1002.547>' (<3987.989, -2944.655, 1002.547>) [Flightor] Set up for movement from <4012.353, -2989.492, 1075.622> to <3987.989, -2944.655, 1002.547> Behavior flags changed! Death, Combat, Vendor, Roam, Rest, FlightPath -> All [FlyTo-FlyTo.(debug)] Behavior completed in 0s Activity: Honorbuddy Stopped LOL. fixed after I changed my Hearthstone place
Is there a way to fix the stucking thing every 4/5 runs without dislearn Mining? BTW: Great work Zodiac!!
