I am new to demonbuddy and just tried this profile. SO my barb gets 5 stacks and then leaves the game and doesn't hunt for the keywarden. What did I do wrong? lol.
Are the machines supposed to be in your stash or your inventory. Switched over to unified, seems like the scoring system has changed quite a bit, i put in my old trinity scores and i don't stash much now.
Magi: where is this code located so I can tinker with it? Blacklist15 in Weighting? I don't get how that works. Does shielded Magha have zero health? I changed it to Blacklist3 and it seems to be better. TIA BTW the more I look at this, the more i'm convinced it is related to arcane avoidance Also, the bot just gets stuck at the throne sometimes and stands there until it dies
sorry guys, I was serving jury duty all day today (and all this week, I was selected) so I've got twice the work to do. Yama - Machines are automagically moved from the stash to your inventory, no protected slots are needed. It will do this when it is ready to fight ubers. Athora - it should fight ubers after getting NV 5, it will do the warden after all ubers are killed. Not sure if that is what you wanted or if you meant to hunt for keywardens. Doublecheck and get back to me Cfong -not sure on the fighting tactics your bot is performing...it really isn't too smart with arcane sentries in general so I agree that is probably screwing things up for you. I can't say I've gotten stuck at the throne myself either. The tough parts are the 4 corners of the room and Mag likes to park there. That usually spells disaster. Not sure how much I can do about that without really hacking trinity. As far as the blacklist, the blacklist is only performed when the health reaches 0. When she shields, she drops off the actorlist now for some reason (her health shouldn't read 0 and therefor shouldn't have any impact on the blacklist). I used blacklist15 (length of time) because the death sequence can last for 5-10 seconds...the worst was skeleton king. Setting the weight to 0 works when there are two ubers...however once you killed an individual uber (or any boss for that matter) your bot would continue to attack them until they disappeared. Setting the weight to 0 didn't stop this because it couldn't acquire a new target. For this, I temporary blacklisted them as it appeared fishy to me (can also waste fury on elites doing that too). I wasn't sure where else to put it in Trinity and I leave it to rrrix to ultimately decide but they do need to either be temporarily blacklisted or removed from the target list so we don't keep attacking them after they are dead. As for HP detection, for ubers bosses, I actually detect death at 0HP because their death sequence lingers. So when it says they are dead, they are really dead. Wardens, yeah that is assumed and if you want some form of tracking, I can put that in. Right now, it will only display their HP when it considers them "out of range" OR has assumed death at a certain HP. When it says Warden is dead and no HP is provided, it read 0HP. So you should be able to gather what you need from that. Most of the time it can acquire 0HP. 25% of the time, it's usually a low number, but on occasion it can be a high spike and it's those high spikes where we need to set our assumed death. If you want the HP spammed when it changes (you doing damage), I could log it in diagnostic or something for you. LMK. Back to real work.
FYI didn't realize rrrix pushed out a new update....looks like he removed monsters with 0hp from the cache so my weighting/blacklisting might not be needed. I will have to double check though as the last "fix" didn't do it Hopefully this does. I'll give it a whirl and get back to you all.
Well the throne is now definitely drawing attention (w.t.f) Must be a new trinity thing. Testing a blacklist on it now.
Pop this right beneath the game params on the act1_uber.xml...appeared to fix the new throne obsession. Code: <GameParams quest="136656" step="-1" act="A1" difficulty="Inferno" resumeFromSave="False" isPrivate="True" numGames="-1" /> <TargetBlacklists> <TargetBlacklist actorId="196972" /> <TargetBlacklist actorId="175181" /> </TargetBlacklists> EDIT: also, rrrix did fix the death attack bug with the latest trinity (1.7.1.7). Thank you rrrix!
Heck yes, looks a lot better with those blacklisted + 1.7.1.7 My only remaining problem is when the bot misses a death... at that point I have to take over by hand... is there a way to add some sort of timeout to skip to the next section? Or any other ideas? Or have some better death prediction. maybe average a bunch of dps samples to extrapolate a death time, rather than using a fixed dps assumption?
Pretty much only the skeleton king so far, probably because he goes down pretty damn fast compared to the others. Happened twice in about 5-6 runs. Not a big deal, i'm pretty much assuming the uber runs aren't afkable anyway.. it would be nice to set it up to fire and forget overnight, but so far what we have is a great start.
also this just happened [22:29:56.315 N] [UberRun] ========== GHOM VANQUISHED!!! ========== [22:30:50.495 N] [UberRun] ========== RAKANOT VANQUISHED!!! ========== [22:30:54.405 N] [UberRun] =+=+=+=+=+= REALM OF CHAOS CONQUERED!!! =+=+=+=+=+= but now it is waiting another 4 mins.. what does that mean?
try this version out: https://www.dropbox.com/s/7ptgdrumx8gru4a/UberRun.cs it has assumed death HP active. Right now it's set in the plugin to 350,000HP. You can tweak it in the plugin .cs file if you want real quick: Code: private static float uberAssumedDeathHP = 350000f; What I'll try to do is export some type of settings file I can refer to which will adjust the assumed death HP over time if necessary. 350k seemed to be a good base number for many people...the high DPS bots will need more of a buffer. Keep you posted on the venture
My bad...I updated my .cs link I posted above just now. Download it and that will fix it. Problem was my Walk to corpse...I had set it not to bother if you were withing 6feet of the corpse area...you must have been which means it didn't reload the profile. I've removed the condition so it will always attempt to walk to the corpse and properly reload profile (which will have you warp out and move on) Thanks for the bug report!
FYI posted updated UberRun v0.4 to original post which should fix the issues above. The assumed death HP needs some form of management (either XML tag for people to change or a settings file that evolves as you play). Will look into that. For now, 350,000 is the base HP which should be fine for most of you. Anyone doing more than 200K DPS may need to adjust this number. See post above on how to do that for the time being.
btw that verbose message you added showing last health recorded is exposing the possibility that you are spamming something in the logs that is normally suppressed because the logger suppreses repeat messages: Code: [22:49:08.552 N] [UberRun] ========== GHOM VANQUISHED!!! ========== [22:49:08.572 N] [UberRun] Assumed Death: HP last recorded: 0 [22:49:08.572 N] [UberRun] ========== GHOM VANQUISHED!!! ========== [22:49:08.672 N] [UberRun] Assumed Death: HP last recorded: 0 [22:49:08.672 N] [UberRun] ========== GHOM VANQUISHED!!! ========== [22:49:08.692 N] [UberRun] Assumed Death: HP last recorded: 0 [22:49:08.692 N] [UberRun] ========== GHOM VANQUISHED!!! ========== [22:49:08.802 N] [UberRun] Assumed Death: HP last recorded: 0 stuck in a loop for 3 mins ;/
heeh can't now im stuck in middle of uber run... gonna have to kill by hand then restart. ugh. looks like monster power is bugged in db too...
