Hey guys, what do you think would be a good config for Kill and loot radius? And I noticed my bot isn't opening sewers chests. It opens from every other place but sewers, even if it's right in front of. Just a curiosity, how much yards from my char to the end of the screen? Char to Top for example.
Ah I see.. this is why Oasis isn't in yet. Altho I'm not into the materia as you are.. would it be possible to perhaps make a time-based command to the bot? Like for example, first you run and explore the place for 3minutes, and if you find another kind of that ID, join it? Or that you let the bot move away at first, and flag that route as "don't go ever back there"? Or you mix up those two Hope you get me there mate Also, after escaping from the audience with hakan and destroying the four demon-callers blocking the path, the bot stays in there for about 1minute and waits.. until it walks on any issues there?
I've been on IRC a lot lately askin questions (CIGGARC is so WIN) and it appears update 227 addresses the multiple portals with the same ID issue, and I now have the portal working Now I just have to script the final portal to Oasis, and fix some cutscene code and we'll be in business.
ill try this out and keep you posted on how long it takes to actualy get the signet running 24/7 greetz lytylisius
I am having a lot of trouble with this profile, and only this profile. I can't go away from my computer for more than hour. I either have "Session Invalid" or my guy is just chilling lost in sewers. It worked fine for me before the recent DB patch, as I found two signets and it would run smooth with 100% afk. I am back to Act 3 Inferno Elite Farming until I figure out whats going on. What do you need from me in order to tell whats happening to my profile? What kind of log, etc.? Thanks for all the work.
Update: 1.4 is coming along nicely, I now successfully have DB making its way all the way through to the Oasis. However, after doing "Unexpected Allies" and making your way through the Wretched Pit and back to town, the cinematic (yes, cinematic, not cutscene) currently has no way of being skipped/disabled by DB in its current form. I have spoken to several others about this and apparently it is a known issue, but I will be looking to find a workaround. It should be noted, as ghetto as it is, if Diablo is not your window of focus (aka its in the background, you have something else on top) the cinematics skip automatically. So, if indeed there is no true fix atm this could be one workaround. That being said, I am slowly generating new blacklist ID's to go into GilesTrinity pertaining to mostly the Act 2 sewers (Archer spawners, things out of reach). Once the blacklist is to where i feel mostly complete, i may just release a beta for those willing to use the Diablo-in-the-background-ghetto-awesome-workaround until DemonBuddy implements a way to skip cinematics.
Hey, I'd like to throw some coin your way for all your awesome effort. Can you give us your paypal info please???!!!???
Changelog: Code: [B][B][B][B][B][B][B][B][B][B][B][B][I][I][B][B][B][B][B][B][B][B][I][B][B][B][B][CENTER][B][COLOR=#333333][FONT=Verdana][U]1.4 HandBananna BETA [/U]This version extends the profile through the Oasis. It explores 2 randomized areas, and seems to do so rather well ATM. You MUST edit GilesTrinity as mentioned above to work properly. UnstuckMe has been removed from the recommended plugins. ^ It's awesome, but no longer needed and seems to cause some issues.[/FONT][/COLOR][/B][/CENTER] [/B][/B][/B][/B][/I][/B][/B][/B][/B][/B][/B][/B][/B][/I][/I] [B][I][COLOR=#ff0000] IMPORTANT: This version encounters a Cinematic, which is not to be confused with a CutScene, and DemonBuddy currently has no way of dealing with these Cinematics. It is a known issue, and I have recently inquired as to progress on handling them. However, at the moment there is no way of skipping the cinematic and while the profile will continue on in the background while the cinematic plays, when it ends the screen stays black until user interaction (pressing escape). I have been told it would be possible to code a plugin to call for a keypress of the escape key when triggered by a tag in a profile, but that it would be labor intensive and might not actually work in the end, so I will be waiting for DemonBuddy to implement some sort of handling for this event. [/COLOR][COLOR=#ff0000][I]Now, there is currently a workaround that I happened to come across, and here it is:[/I][/COLOR][I][B][B][B][B][B][B][B][B][I][COLOR=#ff0000] Do not have Diablo 3 as your focused window!! It sounds dumb, but if DemonBuddy is on top of your Diablo 3 window, or anything besides Diablo for that matter is in your foreground, the cinematic will automatically close and stop the screen from getting stuck on "blackout" from the cinematic until you step in by pressing esc. It is because of this issue that I have considered this version a BETA, but were Cinematic skipping fully implemented this would be an official release. Enjoy![/COLOR] EDIT: Added another mob to the blacklist on the main page: 4109[/I][/B][/B][/B][/B][/B][/B][/B][/B][/I][/I][/B][/B][/B][/B][/B][/B][/B][/B][/B][/B][/B][/B][/B]
Running it now. Will edit with results. [21:19:48.064 N] Loaded profile [A2 - Normal] Champion-Hunting and Questing 1.4 HandBananna Profile 6 [21:19:48.064 N] [RadsProfileManager beta] Reset death count to 0. [21:19:49.785 N] Path with 3 hops received (partial: True) [21:21:50.430 N] Inactivity timer tripped! Leaving game [21:21:50.430 N] Leaving game [21:21:50.460 N] Last run acquired 9591 gold. [21:21:50.870 N] Loaded profile [A2 - Normal] Champion-Hunting and Questing 1.4 HandBananna Profile 4 [21:22:04.009 N] Waiting 14.8 seconds before next game... [21:22:18.911 N] Creating new game, Params: <Act:A2 Difficulty:Normal Quest:57331 QuestStep:-1 ResumeFromSave:False IsPrivate:True> [21:22:38.823 N] GameChanged. Clearing actors [21:22:38.993 N] ========== Grid segmentation resetting!!! ============ Ran twice. both times it goes when it clicks on the portal from the super short sewers into the next set of sewers, the whole screen turns yellow like you are looking really close at a candle and doesnt come out of it. game isnt frozen and I can log out, check inventory etc.. but cant see anything and cant move. Yes I updated black list and yes I ran as "non-focused"
Interesting, I haven't ran across this. Can you post a screenshot? The logging info you posted doesn't give any information that would imply any issue. In giles trinity under advanced check debugging status info bar and take a screenshot of db ontop of your "yellow" Diablo 3 client, so that i can see what the bar says and what the screen shows. EDIT: I see you edited your post. Something is tripping your inactivity timer, and its not listed in that log as to what specifically it was. What does the debugging bar say on the bottom of the DB window when it happens? Also, if you are using rad's profile manager it should go back to your starting profile after leaving the game due to a stuck, which would not be profile 4. Make sure you are starting with the correct profile, aka Start_Here.
Running beautifully so far. Seem to be getting 3-5 more packs per run, and all in the sweet spot. Hopefully find Signet soon. Been running for a few days with no luck. +286% MF pre NV. Finding a bunch of not-so-great legendaries though Keep on keepin on.
Hi I did not understand where it is and where to get up? NOTE: You MUST edit the GilesTrinity.CS file located in the Plugins/GilesTrinity directory and add the following ID's (just CTRL+F and search for blacklist, you'll see the area) or this profile WILL NOT WORK: discover that it is clear and where there is a fit I can not understand
Open your DemonBuddy folder, go to your plugin folder, and open the file named GilesTrinity.CS with Notepad++ or notepad or whatever you choose. Press CTRL+F to open the search dialog, and search for blacklist. It will take you to the section that is commented as the blacklist area, and you need to add the folllowind id's to that list: 56598, 53628, 54272, 209018, 219223, 62522, 5512, 55005, 2965, 4109, EDIT - Like This: Code: // Special blacklist for things like ravens, templar/scoundrel/enchantress in town, witch-doctor summons, tornado-animations etc. etc. that should never be attacked 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, 103217, 105763, 110959, 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, [U]56598, 53628, 54272, 209018, 219223, 62522, 5512, 55005, 2965, 4109, [/U] }; The underlined portion being the new additions.
I may see the issue. I show handbanana oasis as set for Inferno difficulty in your script. <Profile> <Name>[A2 - Normal] Champion-Hunting and Questing 1.4 HandBananna Profile 6</Name> <GameParams quest="57337" step="26" act="A2" difficulty="Inferno" resumeFromSave="False" isPrivate="True" numGames="-1" /> <Order>