Help Hey Magi, I am having an issue with this, whenever its in the Caldeum Bazaar for Act 2, it town ports and then my whole Diablo crashes and demonbuddy terminates.
i have the plugin enabled, i doubled checked. it sits in town when i try to run your profiles. BUT for some reason when i run Tins they take off just fine. i dont know whats going on. id like to be able to run yours. not too crazy about the way his are pathing. ** also im not using any other plugins besides unstucker and trinity unity. all are updated
I dont know if someone else is getting this problem. every time that im on leoric map, outside the mansion and i die, the bot return to the last checkpoint which is inside the mansion, but it never get outside again after a death outside. is that normal or what is wrong with it? when he dies and release, it get stuck inside the mansion and leave the game coz of gold inactivity good game
I just wanted to ask what I have to do to make him run only act II? I copied act II files to different folder and in oasis file changed main starting file to the act2_start.xml. However, after Keywarden is vanquished DB generates error: "Failed to load profile: Path to profile element is not valid; file not found" Is there any other place I have to modify to make it work? Cheers! //Edit Heh, nevermind. After my modification bot does not pick up loot from Keywarden so I guess I will do act II by hand
When I try to run this profile, it keeps switching the game mode to MP0 instead of whatever MP i have it set at. Am I missing something? ex. I have my game set to MP6, but when I run the profile, and it automatically starts a new game, it always sets itself to MP0.
Click on the arrow next to "settings" button, choose "bot" and in new window you will have slider on the right bottom part.
I keep getting the same error and the bot won't even start. I choose my act, and this happens before game start: [11:13:05.461 N] Creating new game. Params: [Act:A1 Difficulty:Inferno Quest:72801 QuestStep:36 ResumeFromSave:False IsPrivate:True Handicap:4] [11:13:06.992 N] Closing error dialog The bot will never run.
Every time I try to click settings > bot, my bot freezes. that's why I've never figured it out, haha.
When I killed the monster and receive NV5 the demonic essences will not be picked up. It will townrun and go to find the key.
I've tried a number of different things to wait for loot to drop before warping out to no avail. Wait timers don't work and using some Trinity condition checks don't always work. Your best bet is to increase the wait time for corpse looting inside the trinity plugin settings. It now defaults to 0 where it used to default to 8/10ths of a second way back when. Up that time and it should help. you may have completed the game, but not every quest. Can happen to those who play public games (or used to anyway, dunno if Diablo changed things around since then) Without knowing specifically what the error is, that is my best guess...especially when trying to start a new game.
My buddy has only all last act quests so i had to change gameparams quest&step. Any way to setup monsterpower for each act? ex: act1 mp4, act2 mp2, act3 mp3 (act2 seens most difficult for my buddy)
Great package overall magi.. thanks.. running it in festering woods now and had a stuck in it first run. ill keep an eye on it see how it goes. could i also make a suggestion that instead of the quest markers in use you set it for the last quest in each act? that's much faster to setup on multiple bots and im really paranoid about getting errors trying to create games on quests you havent unlocked.. since its impossible for a legit player to do this via the ui
having some issues with Act2, logg attatched. having pretty much same one with act3 too, while act1 works fine
awesome profile! but this place need to be added to the run - leets very often spams there and all a2 profiles miss this
look, bot jus ignore this loot(2 rares and tome of secret must to be pickuped) after killing keywarden and go tp-out to next profile (keywarden hunt) this is trinity problem, right?