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

[A1 - A3 Inferno] Keywarden Hunt (Randomized)

this warden is one pesky fella, thank you! I probably won't get to it for a bit, real life has me in a stranglehold at the moment. Probably good with all the bans lately. Looks like I may have survived this round...for now :P
 
Hi! Today my bot didn't pick up key, when it dropped. I think bot start portal to town too early or pickup radius was too small. Where I can change this 2 params?
 
First of all, I've used this profile to farm over 30 machines and it has worked amazing, sure there are stucks but that happens in most all profiles that I have used.

Is there any way to modify this profile to instead of doing keyruns to do full a1-a3 champ runs randomly, and of course killing keywarden in the process?

In light of the recent bans I think it would be beneficial to not run the same A3 champ run profile day in and day out, mixing them up randomly similar to your keywarden profile would be amazing.
 
You sure could...really the only thing you would want to do is disable the keyrun plugin and remove the keyrunforcewarp tag from the A2 profiles.

solid39 - not sure how it could miss the key. Did KeyRun alert you that a key had dropped in the DB info pane? Make sure you are running the latest version of keyrun. A log would be good too.
 
Magi said:
You sure could...really the only thing you would want to do is disable the keyrun plugin and remove the keyrunforcewarp tag from the A2 profiles.

solid39 - not sure how it could miss the key. Did KeyRun alert you that a key had dropped in the DB info pane? Make sure you are running the latest version of keyrun. A log would be good too.
Click to expand...


thank you very much. Another user linked me to an a1-3 randomized profile on the ciggarc forums however it uses radsatom which I am not a big fan of. I will do my best to get it working without rads.
 
Wow didn't expect this but look where the keywarden was. Bot didn't clear this and was tp'ing out saying keywarden not found :(


keywardenpoint.webp
 
wow really? those random dungeons are problematic in this. I had thought about performing an "exploreArea" at the very end to clear out any missed spots, however it takes a tole on the CPU because of the large map. It might not be too bad in Oasis however, but FoM is really bad because half the the entire Act is in one world.

At least this one is by itself. I'll give it a whirl and see what happens.
 
Not sure why mine is not working but I watched it create 9 games and the same error message came across the screen every time.

12:32:39.215 N] [KeyRun] E:\DB2\Plugins\KeyHunting\A1-A3 Keyhunt v2.8\act2_start.xml
[12:32:39.514 N] Failed to load profile: Element KeyRunForceTownWarp is not supported. Please check your XML and try again. (<KeyRunForceTownWarp />) Line 9

View attachment 12142012log.txt

As usual, any ideas / help would be appreciated.
 
KeyRun plugin is not installed and/or enabled...or very old :)
 
odd, I have it installed and it shows up in the plugin list.

Side note, when I hit config it does open up a large white box with no input.. (intended?)
 
yeah I've removed it from my latest version, feel free to download from my signature. Will be posted updates to everything in a bit. Some more improvements/fixes to Rakki and walk-to's to the Keywarden as soon as it spots him.
 
Magi said:
yeah I've removed it from my latest version, feel free to download from my signature. Will be posted updates to everything in a bit. Some more improvements/fixes to Rakki and walk-to's to the Keywarden as soon as it spots him.
Click to expand...

Seems to be working now, will test it for a while, not sure why but deleting the entire folder and then downloading the new one seemed to have done the trick.

Will keep you posted.
 
Magi said:
solid39 - not sure how it could miss the key. Did KeyRun alert you that a key had dropped in the DB info pane? Make sure you are running the latest version of keyrun. A log would be good too.
Click to expand...

Keyrun version: KeyRun Plugin v1.5 for Trinity CE v1.7.1.3+ users

Key dropped again, but bot start to exit :( I stopped it manually and got key.

[KeyRun] ========== KEYWARDEN WITHIN RANGE ============
[14:27:45.699 N] [KeyRun] WARDEN HP: 3622527
[14:27:45.699 N] [KeyRun] ========== KEYWARDEN OUT OF RANGE ============
[14:27:46.730 N] [KeyRun] ========== KEYWARDEN WITHIN RANGE ============
[14:28:04.465 N] [KeyRun] =+=+=+=+=+= KEYWARDEN VANQUISHED!!! =+=+=+=+=+=
[14:28:05.918 N] [KeyRun] Keywarden Corpse Found...
[14:28:06.074 N] [KeyRun] Ready to choose new Act.
[14:28:06.371 N] Loaded profile [A2 - Inferno] Keyhunting Profile Starter!
[14:28:09.371 N] [KeyRun] Exiting game to continue with next profile.
[14:28:10.059 N] Stopping the bot.
 
Last edited:
the key dropped on that and you're sure you're running KeyRun 1.5? It normally identifies that a Key has dropped:

========== INFERNAL KEY DROPPED ==========

Do you usually see that? I've *always* seen that appear when a Key has dropped.
 
yeah I'm just curious how it did not report a key was dropped unless you were running an older version of KeyRun. It basically retrieves the ActorList of ALL objects nearby (usually within 150ft) and if a key is in the list, it displays that message i posted above.

So if you're running latest KeyRun, then either DB did not properly retrieve all objects (possible I guess?) or there is a missing Infernal key name (doubtful at this stage, but possible).

Can you send your full log or PM it to me?
 
Hey Magi my bot keeps crashing and I keep having errors whenever I do key runs. I've tried several different runs and it keeps crashing. Here is a log of a crash well the last bit atleast. I'm using trinity CE 1.7.1.7 with keyrun 1.5. Could you please take a look and see what is going on. Let me know if you need more information


[20:04:24.329 D] Navigator.Clear
[20:04:24.348 D] Replaced hook [ProfileOrderBehavior_Hook] fd48038e-630d-45ed-b357-1bb900b69a0f
[20:04:24.349 D] Generating path to UNKNOWN - <4161.564, 4503.91, 100.0547>
[20:04:24.396 D] Successfully generated path from {X=1660,Y=1497} to {X=1706,Y=1473} in 00:00:00.0016230 with 54(9) hops
[20:04:24.396 D] Client path generated.
[20:04:24.396 D] Generated path to <4161.564, 4503.91, 100.0547> () with 9 hops.
[20:04:24.955 N] Stopping the bot.
[20:04:24.955 D] CurrentBot.Stop()
[20:04:24.955 D] Navigator.Clear()
[20:04:24.955 D] Navigator.Clear
[20:04:24.955 D] TreeHooks.Instance.ClearAll()
[20:04:24.955 D] OnStop event
[20:04:24.955 D] OnStop Event Invoking
[20:04:24.985 D] ProfileOrderManager.OnBotStop. Resetting caches.
[20:04:24.985 D] Resetting current behavior.
[20:04:25.061 N] Bot Thread Ended. Was this requested?
[20:04:32.012 D] Forcing profile reload.
[20:04:32.298 N] Loaded profile [A2 - Inferno] Keyhunting - Dahlgur Oasis
[20:04:32.298 D] Starting bot Order Bot
[20:04:32.298 D] Added new hook [OutOfGame] 2cc74428-4445-459b-925e-0fa29696fe38
[20:04:32.298 D] Added new hook [Death] d4ebca6f-8b8a-4c57-8f30-bc9ae695195b
[20:04:32.298 D] Added new hook [RoutineBuffs] 8516788a-f89e-4c7e-aacd-4321028e8efb
[20:04:32.298 D] Added new hook [RoutineCombat] 73f104cf-d1b3-4537-8af3-a914fd926d23
[20:04:32.298 D] Added new hook [Combat] a47f8ec7-97b4-4329-87b6-de225dcf690b
[20:04:32.298 D] Added new hook [IdentifyItems] 8fc65ccb-695c-4ac8-8d07-c9abb7909b1d
[20:04:32.298 D] Added new hook [StashItems] 97c0d381-80af-4bb6-9338-a6f90b8c428c
[20:04:32.298 D] Added new hook [SellAndRepair] 0d3b1aa4-7beb-496a-a314-a39d69f15128
[20:04:32.298 D] Added new hook [SalvageItems] fe0488ef-9430-46a0-ab5f-1e12e7cda0c8
[20:04:32.298 D] Added new hook [VendorRun] d31ce148-53c3-4f50-a8a8-1884e1d19b75
[20:04:32.298 D] Added new hook [Loot] 2e2f9d00-3ef8-4c7a-bfd8-4f6a09ed3f22
[20:04:32.298 D] Replaced hook [BotBehavior] 20832477-d756-4673-89d4-982ec6ef0653
[20:04:32.310 N] [Trinity]Note: Maintaining item stats from previous run. To reset stats fully, please restart DB.
[20:04:32.311 D] Spooling up bot thread.
[20:04:32.312 D] Bot thread started.
[20:04:32.354 D] Replaced hook [ProfileOrderBehavior_Hook] da157a49-dd9e-4949-973a-7f35c3b7410c
[20:04:32.462 D] Replaced hook [ProfileOrderBehavior_Hook] c90a6233-c1b5-4f21-9233-6ca2a4f2db86
[20:04:32.463 N] [KeyRun] KeyWarden Assumed Death HP set to 350000
[20:04:32.483 D] Replaced hook [ProfileOrderBehavior_Hook] 250abb72-1852-4e7e-8b90-e61ce3e50552
[20:04:32.650 N] ToggleTargeting, new values: Looting:True LootRadius:80 Combat:True KillRadius:35
[20:04:32.650 D] Replaced hook [ProfileOrderBehavior_Hook] 3539f66e-0d87-4dca-9ee6-9d8bd5fdf515
[20:04:32.678 D] Replaced hook [ProfileOrderBehavior_Hook] d8947873-5b85-4f46-bd5c-662cb3d86be3
[20:04:32.679 D] Generating path to UNKNOWN - <4219.11, 4387.877, 94.4203>
[20:04:32.722 D] Successfully generated path from {X=36,Y=152} to {X=27,Y=152} in 00:00:00.0001647 with 10(4) hops
[20:04:32.722 D] Client path generated.
[20:04:32.722 D] Generated path to <4219.11, 4387.877, 94.4203> () with 4 hops.
[20:04:41.507 N] Diablo III Exited, Demonbuddy terminating
[20:04:42.318 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 01873414 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.MemoryManagement.InProcessMemoryReader.Read[T](Boolean isRelative, IntPtr[] addresses)
at Zeta.ZetaDia.get_CurrentWorldId()
at Zeta.ZetaDia.get_IsInGame()
at RadsAtom.Functions.Mrworker.MrThread()
 
You must log in or register to reply here.
Back
Top