[A1 Inferno] Keywarden Hunt

Thanks a lot !

 

nice profile . work well for me . able get the key after few run . if can make the profile end and repeat after kill the keywaren . This profile will be perfect . Thanks Magi

 

Yea I spoke too soon, the town run thing was just a one time occurrence.

 

Thanks guys. I'll look into the warden kill thing. Problem is, they aren't specific to a quest or a location or else I could probably figure it out. I'll let you know if I find a solution though.

 

I dont know how the profile making process goes, but maybe there is a way that it could leave the game after it picks up the key? Have it leave after a certain Item being picked up may be a feature your able to implement? No idea. Just a suggestion if that is possible.

 

Good idea, I know you can check to see if things exist and ignore certain monsters, so I'm hoping I can check to see if the Warden exists, and if not, safely assume we killed him.

As a side note, I saw someone had posted an Act1-3 keyrun which is cool. I did the same with mine, although I randomized mine so it randomly will cherry pick the acts to help further prevent detection. Ran it last night and got all 3 keys (5 in total, woohoo!)

May post that if people are interested as well. Going to keep working on Warden detection.

 

please someone upload giles trinity 1.6.3.1 .... cant find anywhere..

 

Try their latest version. 1.6.3.4

They say it is fixed...I haven't tried it yet because DB has been giving me some issues.

Also, I will be uploaded some revised profiles to better handle death handling, just doing some testing if DB will stay connected.

 

1.6.3.4 version works fine but

i got two problem in FOM script

FOM A
bot stops attack at the certain posion on map

always stop on that position even kill KeyWarden or not

FOM B
if bot goes from portal to FOM map B

bot stop too...


im using RadsAtom, GilesTrinity(unstuck function disabled), Unstuckme


and my DH bot works Really dumb XD

 

Hi, I'm having some trouble running this profile pack.

All goes well at first and I collect 5 stacks of NV swiftly. However after getting 5 stacks it runs Antidote_FieldsofMiseryB.xml( Using Waypoint Waypoint_Town-9489 Number:8) and runs down through the farm and eventually reaches Fields of Misery. Here it stops and will disconnect when the inactivity timer is triggered.

Any idea how I can fix this?

 

I got problem with RadsAtom download the link looks to be bad (or i do not understand where it lead). Can you give direct download link?

Thx

Ok got it sorry for trouble

 

Hey guys,

Not sure if this was a DB issue or what, but Misery magically stopped working (both profiles) at certain points. Bot didn't get stuck, it just stopped. This seemed to break all Ciggarc's Act1 Profiles

Ciggarc reported that they updated their profile:

Though I can't seem to find a link to the new download....and then I saw DB report they fixed their servers so at this point I don't know what is going on lol. Very strange. Gonna run my script again real quick and see if it is still bugged as it worked great up until yesterday.

Will report back...

UPDATE - As all of you are probably aware, I can't login! DB is still having issues. Until DB resolves their issues, expect some problems with this.

 

Everytime I run this profile it will run for a few minutes then crash my diablo and Demonbuddy. I can run the act 3 Big Red champion hunting for days without error. Any ideas what is causing this to crash for me so often? I have not been able to get 1 key using it.

Here is what I am running with it:
I am using Demonbuddy v1.0.1094.27
GileTrinity 1.6.3.4 I could not find 1.6.3.3 that you recommended, could this be the problem?
RadsAtom 1.5.1

Thats it, thats all I am running and can't seem to get it working. I have tried clean installs also, still crashes after a little while running.

EDIT: I just got it to finally kill a keywarden before the crash, and after he killed the warden he just kept running around the fields of misery, never warped out. Is that normal?

 

Hi,

Yes Act 1 got messed up last night for some reason, it no longer likes certain wave points in the profile that HAD been working for quite some time. I'm not sure if this was a change with DB or what, but it looks like new movement points will need to be assigned. I just checked and this still is not working. Act 3 and 2 should still be working however.

I will let you know as soon as Act1 has been fixed, I may just map new points myself but supposed Ciggarc (original writer of this profile) has a new release that fixes this but I didn't see the post.

As for keywardens, there is no way that I have been able to figure out, to teleport upon their death. They aren't related to a specific quest (to check if you completed the quest) and they are randomly positioned on the map. So at this point, it only TPs on NV5, and then it just runs the keywarden map and clears it. Until I can figure out a way to tell if the keywarden is dead, this is how it will operate.

First priority is to get Act1 working again.

EDIT: I believe the issue is related to the Z coordinate of these profiles...I just mapped a new point and was able to get past the constant stuck point in Misery Profile B. Got a hockey game to go to but when I get back, if Ciggarc hasn't posted their updated profiles, I will re-map Misery Profile A since that one stops near the end.

 

Found this for those more experienced users:

Code:

<MoveTo questId="1" x="2131.725" y="458.1083" z="0.1" name="FoM #20" />
    <MoveTo questId="1" x="2131.725" y="458.1083" z="0.1" name="FoM #21" />
    <MoveTo questId="1" x="2072.387" y="469.429" z="0.1"  name="FoM #22.1" />	
    <MoveTo questId="1" x="1961.413" y="485.4483" z="0.1" name="FoM #22.2" />
	<MoveTo questId="1" x="1920.435" y="372.7823" z="0.1" name="FoM #22.3" />
	
    <MoveTo questId="1" x="1865.47" y="222.6739" z="0.1000001" name="FoM #23" />

Replace these MoveTo points in the MiseryA XML profile. Supposed to fix...

 

Awesome Thank you.

 

Awesomeness. Thx...this seemed to have fixed it. Ran twice now without getting stuck in FOM. Hoping it can go without me babysitting o/n now Thanks muchly!

 

Ugh...spoke too soon. Not working...aaah well...

 

It might be because of Misery profile B which is still broke...it randomly selects A or B, if it selects B, it will get stuck. I'm testing Profile A now, if it works I'll update my files to ignore Profile B of Misery for the moment.

Also, the pre-release from Ciggarc is only available to donors, hence why I can't see it. If you want a fixed version from Ciggarc, you can donate to them.

Will report back shortly...

 

Profile A completed for me, so that is fixed. I am temporary removing Profile B for now so that people can run this profile again...updating the OP now.