MP is now suported in <GameParams> since latest stable version (build#283). @dcaari: Make sure you have DB build#283 or higher and add monsterPower="1" at the end of GameParams tag, for example: Code: <GameParams quest="87700" step="-1" act="A1" difficulty="Inferno" resumeFromSave="False" monsterPower="1" />
As many people reported these at the pages before in this thread, I'm having the following issues as well: 1)Bot keeps walking onto a wall when it tries to reach a goblin 2)Bot sometimes keeps going south-east in the corner in the city @ A3 3)Bot gets stuck in this place @ Skycrown Battlements ( http://i50.tinypic.com/zoerk0.jpg ) 4)Bot gets stuck in Barracks
Are there any way to farm faster ? Atm when I'm farming i get around 10-14M exp each hour. I'm farming on MP1 with 22% movementspeed as well. And I'm only dying like 2 times each hour only.
Ranged characters keep getting suck trying to kill Demonic Hell Bringer things in Skycrown by shooting over the torches which do not allow projectiles to go through.
You should be farming MP0. What is your gear and xp bonuses? Im getting 16-18m an hour with no xp bonus gear on in mp0 and with 160k dps on my barb. Any deaths at all in MP1+ (if you have the gear to 1-2 shot everything) makes farming MP1+ not nearly as good as MP0, even for items.
I closed demonbuddy today and tried to run this profile again, which I had been doing and it just goes to act 3, then doesn't move at all. Are there any settings I may have messed up? It just says I completed the profile after like 1 minute of standing there
I am running DBRelogger because my diablo3 crashes randomly every couple of hours, but it sees now that my bot is sometimes staying at the resume game screen, bot is still running, but the game is not resuming. I know this was a known issue with DBRelogger and there was a fix released, which I installed, but it is still doing it. Just wondering if anyone else is having this issue with the champion farming route?
hei guys, i modified the line in stonefort to get azmodan after but from 4 runs only 1 time it went and killed azmodan.anyone else had this problem?
Bot often gets stuck when trying to kill something over this ledge. Noticed it about 5 times already. http://i.imgur.com/c1NeZ.jpg This is also a place where the bot gets stuck a lot. http://i.imgur.com/8Lgu7.jpg
ive done a small workaround this, basicly ignores the the demonic hell bearer that spawns the adds, mostly get this if its a ranged class Code: // IGNORE LIST / BLACKLIST - for units / monsters / npcs // Special blacklist for things like ravens, templar/scoundrel/enchantress in town, witch-doctor summons, tornado-animations etc. etc. that should never be attacked // Note: This is a MONSTER blacklist - so only stuff that needs to be ignored by the combat-engine. An "object" blacklist is further down! //intell -- added oldNecromancer (4798) and his Skeleton_A_Necromancer (183892) private static readonly HashSet<int> hashActorSNOIgnoreBlacklist = new HashSet<int> { 5840, 111456, 5013, 5014, 205756, 205746, 4182, 4183, 4644, 4062, 4538, 52693, 162575, 2928, 51291, 51292, 96132, 90958, 90959, 80980, 51292, 51291, 2928, 3546, 129345, 81857, 138428, 81857, 60583, 170038, 174854, 190390, 194263, 174900, 87189, 90072, 107031, 106584, 186130, 187265, 201426, 201242, 200969, 201423, 201438, 201464, 201454, 108012, 103279, 89578, 74004, 84531, 84538, 89579, 190492, 209133, 6318, 107705, 105681, 89934, 89933, 182276, 117574, 182271, 182283, 182278, 128895, 81980, 82111, 81226, 81227, 107067, 106749, 107107, 107112, 106731, 107752, 107829, 90321, 107828, 121327, 185391, 249320, 81232, 81231, 81239, 81515, 210433, 195414, 80758, 80757, 80745, 81229, 81230, 82109, 83024, 83025, 82972, 83959, 249190, 251396, 138472, 118260, 200226, 192654, 245828, 215103, 132951, 217508, 199998, 199997, 114527, 245910, 169123, 123885, 169890, 168878, 169891, 169077, 169904, 169907, 169906, 169908, 169905, 169909, 179780, 179778, 179772, 179779, 179776, 122305, 110959, 103235, 103215, 105763, 103217, 51353, 80140, 4176, 178664, 173827, 133741, 159144, 181748, 159098, 206569, 200706, 5895, 5896, 5897, 5899, 4686, 87037, 85843, 103919, 249338, 251416, 249192, 80812, 4798, 183892,196899, 196900, 196903, 223333, 220636, 218951,245838, [COLOR="#FF0000"]214240[/COLOR] }; the color indicated in red is the ID added for this monster
I had this same problem I did 2 things either of which worked , I downgraded my Radsatom version , and put the bot directly in the c:/Demonbuddy , for some reason the short pathing helped ( read somewhere in forums )
From yesterday said that he became permanently depart the game client and it is connected with such Radsatom. [06:55:35.484 N] Loaded profile [A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed Profile Starter! [06:55:35.484 D] Starting bot Order Bot [06:55:35.484 D] Added new hook [OutOfGame] 0df7ddf9-286a-4e27-8e44-c5b9881a3b02 [06:55:35.484 D] Added new hook [Death] 1be47325-3431-4bc9-afb0-f2055e48c674 [06:55:35.484 D] Added new hook [RoutineBuffs] d5c6bc6c-e039-40d6-a31b-f8e55e4e29b3 [06:55:35.484 D] Added new hook [RoutineCombat] c4da4ba5-fb24-49c1-ab2e-36e41efd120f [06:55:35.484 D] Added new hook [Combat] a11f3fde-47c1-449e-902e-2ee8709ee15e [06:55:35.484 D] Added new hook [IdentifyItems] 3bec778d-f91c-4da5-bde5-e2fbf07479d7 [06:55:35.484 D] Added new hook [StashItems] 4262833f-48d3-4f25-a0fd-3c707cfe434d [06:55:35.484 D] Added new hook [SellAndRepair] d25774d5-0c3a-4de1-acd0-879a5bae0f67 [06:55:35.484 D] Added new hook [SalvageItems] 27b41bd1-8239-4d62-821e-da3fe27f4178 [06:55:35.484 D] Added new hook [VendorRun] 0d87a2cb-13bd-455d-9b22-b7a0fd00855b [06:55:35.484 D] Added new hook [Loot] a903aec1-4f48-4b06-9fbb-2ed7fd9fdd3e [06:55:35.484 D] Replaced hook [BotBehavior] dae5c286-adc2-4e7e-a97a-fec7fe529460 [06:55:35.546 N] [GilesTrinity] Note: Maintaining item stats from previous run. To reset stats fully, please restart DB. [06:55:35.546 D] Spooling up bot thread. [06:55:35.563 D] Bot thread started. [06:55:35.586 D] Replaced hook [ProfileOrderBehavior_Hook] 938135d9-81eb-469a-9723-81202db6e06c [06:55:39.980 N] Using town portal [06:55:47.609 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000788 [299]! в Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative) в Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative) в Zeta.MemoryManagement.InProcessMemoryReader.Read[T](Boolean isRelative, IntPtr[] addresses) в Zeta.ZetaDia.get_CurrentWorldId() в Zeta.ZetaDia.get_IsInGame() в RadsAtom.Functions.Mrworker.MrThread() [06:55:47.612 N] Diablo III Exited, Demonbuddy terminating
My barb runs the profile perfectly however when the profile ends it doesnt relog and restart the profile it just goes back to the first way point and runs through the profile with no mobs. Any idea how to fix this?
Hmm.. the bot suddenly stops after being stuck. Any clue why? [08:23:56.758 N] [Unstucker v2.2.0] Your character appears to be stuck. [08:23:56.758 N] [Unstucker v2.2.0] Attempting to unstuck by restarting the game. [08:23:56.758 N] [Unstucker v2.2.0] Leaving game... [08:24:10.791 N] [Unstucker v2.2.0] Restarting profile 'C:\Users\Byakushiki\Downloads\Demonbuddy 1.0.1162.284\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_START_HERE.xml' [08:24:11.069 N] Loaded profile [A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed Profile Starter! Normaly here there should be a timer, where it will resume the game after some secs. But that doesn't happend at all. Added: I have to manually resume game. For the bot to continue.
Hello, Amazing Script. There seems to be an issue with getting stuck due to obstacle in the way. I have attached a photo so you can see. This would be in Skycrown. This could potentially be an issue only with DHs because of the ranged attack. My barb has no problem killing that monster, but as you can see my DH just keeps firing at the burning logs.