View attachment 4564 2012-11-17 17.26.txt log here Can you guys help me whats this? ound this after the warden is down. [17:40:12.579 N] [KeyRun] Ready to choose new Act. [17:40:12.921 N] Loaded profile [A1 - A3 Inferno] Keyhunting - Choose an Act [17:40:15.955 D] Replaced hook [ProfileOrderBehavior_Hook] 4bf3911f-d7e6-477f-9984-9c1d1e97f10d [17:40:15.981 N] [KeyRun] Ready to choose new Act. [17:40:16.335 N] Loaded profile [A1 - A3 Inferno] Keyhunting - Choose an Act [17:40:19.341 D] Replaced hook [ProfileOrderBehavior_Hook] 9670814c-d86d-4be1-a000-0a96939b5ccb [17:40:19.363 N] [KeyRun] Ready to choose new Act. [17:40:19.768 N] Loaded profile [A1 - A3 Inferno] Keyhunting - Choose an Act Thanks in advice! EDIT: im using relogger, so im using the profil RELOGGERS_START_HERE.
I'm not sure I understand how to use this plugin. Do we HAVE TO use the (modified?) GilesTrinity packed with the profile, or is the same as UnifiedGilesTrinity (0.41) ? Thank you very much!
Game is crashing for some reason in act 2 everytime. [23:27:05.188 N] Creating new game, Params: <Act:A2 Difficulty:Inferno Quest:57339 QuestStep:-1 ResumeFromSave:False IsPrivate:True Handicap:2> [23:27:09.804 N] GameChanged. Clearing actors [23:27:09.895 N] [KeyRun] New Game Started, Reset Variables [23:27:09.898 D] Joined a game! [23:27:09.915 N] ========== Grid segmentation resetting!!! ============ [23:27:09.917 N] ProfileOrderManager.OnGameJoined, Reloading profile. [23:27:10.194 N] Loaded profile [A2 - Inferno] Keyhunting Profile Starter! [23:27:10.353 N] ToggleTargeting, new values: Looting:True LootRadius:80 Combat:True KillRadius:35 [23:27:10.357 D] Replaced hook [ProfileOrderBehavior_Hook] 45aeec6d-d5f5-4b3d-a831-59dfd1f1a121 [23:27:10.888 D] Replaced hook [ProfileOrderBehavior_Hook] 58eb64ba-95d9-4c9c-a004-49152f15d221 [23:27:18.095 D] System.NullReferenceException: Object reference not set to an instance of an object. at Zeta.Internals.Actors.DiaActivePlayer.get_NumBackpackSlots() at Zeta.Internals.Actors.DiaActivePlayer.InventoryManager.get_NumBackpackSlots() at Zeta.CommonBot.Logic.BrainBehavior.() at Zeta.CommonBot.Logic.BrainBehavior.() at Zeta.CommonBot.Logic.BrainBehavior.() [23:27:18.132 D] Replaced hook [ProfileOrderBehavior_Hook] f2528039-2276-4db9-9f8f-cd3cb0800a89 [23:27:18.133 N] Opening door g_LightGlow_PaleYellow_soft-394 Id:184576 [23:27:18.811 N] Diablo III Exited, Demonbuddy terminating Added: I noticed the game crashed once it automaticly teleported back. At the beginning.
You don't have to use my file, no. Everything is now packed up with the Unified Trinity v0.40+ Now that it is officially supported in their version, I will remove my trinity stuff from the zip so there is no future confusion. Thanks!
Is this the full log? Would appreciate the full log (or at least a few pages of the events leading up to the crash and the crash itself) Are you using any form of RadsAtom? Any other plugins? Custom Looting?
Wow simply amazing. So smooth, bugless and fast, great job getting reloggers to work with this too! Amazing work. /me Tips his hat. **Just one question, should i disable atom when using this?**
Yes, I am using Trinity to handle deaths because Atom was giving me too many problems. If you want to use atom, I would remove all references to the trinity death XML tag as I imagine that will screw some stuff up.
I'm a bit confused how do you use this now. I chose Act 2 - Lord of Lies in client, clicked start and it switched to Act I Imprisoned Angel. Also which does one use relogger start here or the other xml file. EDIT: Update, The bot seems to have exited game with just 2 nv stacks. I stopped when it got to quest screen to post log at end. [13:00:27.519 N] [KeyRun] C:\MSN\Plugins\A1-A3 Keyhunt v2.3\act1_start.xml [13:00:27.842 N] Loaded profile [A1 - Inferno] Keywarden Hunt [13:00:30.843 N] [KeyRun] Exiting game to continue with next profile. [13:00:34.886 N] Waiting 19.3 seconds before next game... [13:00:40.418 N] Stopping the bot. [13:00:40.431 N] Bot Thread Ended. Was this requested?
I died on keywarden (A1), but instead of returning to kill him it decided I already did and started new game...
iMax - It's because of the assumed death HP. You died when he had at least 34000 HP (aka not very much). If you are doing less than 80-100k dps, drop the assumed death HP down from 350,000 to something smaller. (you do this on the keywarden profiles) The issue here is we have to do some guess work on whether the warden is truly dead or out of range. There is no PRECISE way to determine if the warden is dead, many times my script will catch him at 0HP (DEAD), but somestimes the warden drops off the actor list before I can register 0HP. So, I check the last known HP of the warden. For my chracter who does about 100kDPS...if the warden is anywhere near 100,000HP, he is dead. Unless you're doing 20K dps, I'd say you just got unlucky that you died right when he was pretty much dead. You can try dropping the assumed warden death HP down a bit and see...though if you set it too low, you could end up killing him and it not registering as a death. Hacker...no clue what yours is doing lol. Send me a full log.
I just updated to most recent unified giles plugin, most recent key run, and most recent beta. The problem I am having is after getting 5nv stacks it will warp to town, and then just idle. Any idea how to fix this?
send me your log if you would. I know some folks were having some issues with the unified plugin if they updated from an older version, might try deleting the trinity config file inside the settings folder (GilesTrinity.cfg)...when you launch DB and start up trinity, it will recreate this. My Ghom slider added a new parameter and the old config files needs to be updated.
Magi, feature suggestion: when all/two key's are even, choose next act to start with random. This way bot looks more like human. And is less detectable.
