What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[A1 - A3 Inferno] Keywarden Hunt (Randomized)

after hours of farming with 1.2.2 i found this big problem which i have last night for 7-8 hours.
21:05:59.859 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.DiaObject.()
at Zeta.Internals.Actors.DiaObject.get_Position()
at RadsAtom.Functions.Inactivitytimer.CheckMovement()
at RadsAtom.Functions.Inactivitytimer.InactivityThread()
[21:06:00.339 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:00.339 N] [RadsAtom] - Resetting the deathcounter.
[21:06:05.345 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:05.345 N] [RadsAtom] - Resetting the deathcounter.
[21:06:10.415 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:10.415 N] [RadsAtom] - Resetting the deathcounter.
[21:06:10.879 N] [RadsAtom] - Reloading profile, stuck in town too long: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_AlcToWinds.xml
[21:06:15.441 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:15.441 N] [RadsAtom] - Resetting the deathcounter.
[21:06:15.893 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.DiaObject.()
at Zeta.Internals.Actors.DiaObject.get_ACDGuid()
at Zeta.Internals.Actors.DiaObject.get_CommonData()
at RadsAtom.Functions.Inactivitytimer.isBusy()
[21:06:15.893 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.DiaObject.()
at Zeta.Internals.Actors.DiaObject.get_Position()
at RadsAtom.Functions.Inactivitytimer.CheckMovement()
at RadsAtom.Functions.Inactivitytimer.InactivityThread()
[21:06:20.463 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:20.463 N] [RadsAtom] - Resetting the deathcounter.
[21:06:25.477 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:25.477 N] [RadsAtom] - Resetting the deathcounter.
[21:06:30.477 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:30.477 N] [RadsAtom] - Resetting the deathcounter.
[21:06:35.557 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:35.557 N] [RadsAtom] - Resetting the deathcounter.
[21:06:40.577 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:40.577 N] [RadsAtom] - Resetting the deathcounter.
[21:06:42.969 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.DiaObject.()
at Zeta.Internals.Actors.DiaObject.get_ACDGuid()
at Zeta.Internals.Actors.DiaObject.get_CommonData()
at RadsAtom.Functions.Inactivitytimer.isBusy()
[21:06:42.969 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.DiaObject.()
at Zeta.Internals.Actors.DiaObject.get_Position()
at RadsAtom.Functions.Inactivitytimer.CheckMovement()
at RadsAtom.Functions.Inactivitytimer.InactivityThread()
[21:06:45.589 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:45.589 N] [RadsAtom] - Resetting the deathcounter.
[21:06:50.637 N] [RadsAtom] - Loading next profile: C:\Users\xtc69\Desktop\db\profiles\A1-A3 Keyhunt\act2_Oasis.xml
[21:06:50.637 N] [RadsAtom] - Resetting the deathcounter.
[21:06:52.972 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.DiaObject.()
at Zeta.Internals.Actors.DiaObject.get_ACDGuid()
at Zeta.Internals.Actors.DiaObject.get_CommonData()
at RadsAtom.Functions.Inactivitytimer.isBusy()
[21:06:52.972 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.DiaObject.()
at Zeta.Internals.Actors.DiaObject.get_Position()
at RadsAtom.Functions.Inactivitytimer.CheckMovement()
at RadsAtom.Functions.Inactivitytimer.InactivityThread()

this is the log .the bot go to base with 5 stacks and stays there forever try running oasis.xml then alctowinds.xml and never stops or do anything.bot does that for hours if u let it.
 
Hate to say it because it sounds stupid, but try a complete fresh install. Put in my version of Trinity and RadsAtom, download profile 1.2.3, enable ONLY those two pluggins, and run. See if it does it again. I looked through my logs for the past 2 hours, and I see none of that.

You could try what avoidlol did if you want...it's a simpler profile in some regards (doesn't appear to have death handling in A1), but he has it ensure NV5 before going after keywardens which should eliminate the crap I have to do to get around RadsAtom. Worth a shot if you can't get mine working.
 
So i tried this yesterday night cause It was pretty exciting seeing a random keywarden profile, and it seemed to work in act3 and act1 ok, but for some reason in act2 i couldn't get 5stacks and it still went to Dalgar Oasis to search for keywarden. I remember catching it at 4 stacks and it foudn the warden and attempted to kill, i manually stopped at that point and went manual mode for the key. I'll check back as soon as another update hits, great work non the less!!!
 
i dlowd 1.23 and testing now.act 3 and act 1 runs all day without problems yet.the only prob is that bug at act 2 so i try this new one and see.
 
Wouldn't it be better to just bot act 3 and and save up the gold to buy a hellfire ring to your liking if you want it so much?
 
Sorry if i missed something somewhere in the thread, but I have seen similar posts. I can't get the profile to run. I have the latest version of DB and all required plug-ins. The profile simply grabs a 5 stack, ports to town, and turns off:

[18:06:37.918 N] [RadsAtom] - Keyrun enabled. The keyrun profile is:
[18:06:37.998 N] Stopping the bot.
[18:06:38.008 N] Bot Thread Ended. Was this requested?
[18:06:38.829 N] [RadsAtom] - You got 5 stacks. Will load the profile to Key warden.
[18:06:38.829 N] [RadsAtom] - Keyrun disabled.
[18:06:38.829 N] [RadsAtom] - Loading: D:\Demonbuddy4\A1-A3 Keyhunt\
[18:06:49.422 N] Failed to load profile: Path to profile element is not valid; file not found

Sorry if its a really simple fix, but I can't figure it out :P.

Thanks!
 
I guess it's not random, just looks like random. The profile goes like a1, a2, a3, a2, a3, a3 again a1, a2, a3, a2, a3, a3......
 
ChineseMate said:
I guess it's not random, just looks like random. The profile goes like a1, a2, a3, a2, a3, a3 again a1, a2, a3, a2, a3, a3......
Click to expand...

Got me, I'm just using the built in "random" picker. Probably about as random as Diablos items rolls :P

Since a few of you seem to be have some issues with the NV5 stacker, specifically Act 2, I'm going to add another region to the profile I think since that is the most common act where you DON'T get NV5 before Oasis. Howling Plateau seems to be what folks have been recommended (I hate Desolate Sands personally, would like to avoid). I'm going to run through that and see what I think about it.

Personally, this this is running like a champ for me, but I am jumping through a few unnecessary hoops because of RadsAtom which I think is the root of the problems. Will post back my findings a bit later if I can keep the wife off my back!
 
Just figured out why people are getting stuck at Act2 Whispering Winds...the "continue to" profile is missing???

Sweet lol. OK fixing up.
 
humble said:
Alright, I've been testing the newest update for two hours, everything went extremely flawless until just now.

It appears the new coding makes the profile loop FoM over and over when it doesn't detect the warden. I let the profile run through FoM three times before I stopped it to manually find warden.

I found him here, which is undetected by the profile:

View attachment 62379
Click to expand...

Do you have any ideas for this problem, Magi?

I find it kind of important for all users not to keep looping through A1, since I'm guessing it would never stop looping as long as it isn't stuck or inactive.

I'm guessing either more areas of FoM are needed in MoveToTags or the profile needs to be told to exit FoM when it reaches last line, eventhough it didn't find warden.
 
humble said:
Do you have any ideas for this problem, Magi?

I find it kind of important for all users not to keep looping through A1, since I'm guessing it would never stop looping as long as it isn't stuck or inactive.

I'm guessing either more areas of FoM are needed in MoveToTags or the profile needs to be told to exit FoM when it reaches last line, eventhough it didn't find warden.
Click to expand...

Hey,

The new version I posted checks that area now. Are you using 1.2.3? Also, it should TP if it reaches the last line...I increased the radius in that as well just to help make sure it does TP back to town and restart. I've tested a few times myself and it worked. Let me know, verify everything is up to date, but I know for sure it scans that entire area now, I added about 8-9 wavepoints in the highlighted area.

All my while loops (looking for warden) include a second condition which checks to see if your player is within range of the last movement point:
Code: 
<While condition="not ActorExistsAt(255996, ZetaDia.Me.Position.X, ZetaDia.Me.Position.Y, ZetaDia.Me.Position.Z, 150) and not ActorExistsAt(ZetaDia.Me.ActorSNO, 1609.576, 369.2259, 0.1000001, 30)">

Make sure your warden are profiles have this. This will cancel my while statement upon finding the warden or landing on the last wavepoint. check the x,y,z coordinates of your last MoveTo point so it matches my numbers in that while condition if you're using someone elses MoveTo points. I triple checked to make sure mine are correct.

I've gone through all 3 acts after killing the warden to run through and make sure that it resets at the end, for me, they do :)

Running an Act 2 test now...hope to have that fixed up shortly.
 
Last edited:
I suggest just not put all the path in the while loop. Just leave them in sequence without looping. not stuck not endless loop is more efficient before it can go more advanced.
 
ChineseMate said:
I suggest just not put all the path in the while loop. Just leave them in sequence without looping. not stuck not endless loop is more efficient before it can go more advanced.
Click to expand...

While loop is used to constantly check for the for keywarden. If you remove this, you will kill the warden, and then clear the map. My intention is to kill the warden, and warp out immediately after.

Personally, mine doesn't have any issues warping out, and almost every time it finds the warden. It does require the latest updates, as well as my attached trinity/radsatom files. It is working for me, I swear I'm not making it up :)

You DO need the latest DB build (not beta, but latest build)
 
Sorry for all the posts guys, just trying to keep ya'll informed.

Act 2 ran well for me, I've injected Howling Plateau so it will run Mines - Alcarnus - Howling Plateau - Winds - Oasis.

I've also removed all of my hacked RadsAtom tags which means you can go back to using original RadsAtom 1.5.1 if you want (although if you keep mine, it *shouldn't* make a differece).

Look for an updated profile shortly. Just finishing up Act 2, going to run another Act 1 real quick to make sure I'm not talking out of my ass. (or didn't mysteriously remove something) :)
 
im getting stuck in act 1 festering woods not sure how to tell you location
 
log would be good...there are a few stuck areas depending on monster layout, but my bot has always managed to get out of it.
 
hold off...im posting a new version in a second. Wait for that. Should hopefully address most people's problems.
 
ok if you are doing that can you post the official RadsAtom as well since you no longer use your modded version, I cant seem to find it anywhere and searches just bring me to this thread lol.
 
You must log in or register to reply here.
Back
Top