Search results

They aren't that hard, I started running this on my wizard around 1.2m dps and 5m toughness.

I have also noticed since running the newest version I am getting more keys =)

Sorry I meant which version of the profile. Is it v2.2? I added a few lines of code that should have fixed looting issues.

I have not yet encountered the mob but the profile is working, I have made it so the bot will go thru the path at the north part of southern highlands at the end of the run thought I am not sure if the mob spawns there. The lines of code that make the bot run there are located towards the bottom...

The profile will be up shortly, testing it right now.

Thanks for this!

I have found several threads on this problem and they all seem to say the same thing this one says: http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/156079-code-316611-a.html

Which version are you running Cleo?

No longer taking requests, if I did not get to your request sorry! The amount of free time I have has just dropped significantly due to my schoolwork, near the end of semester and the workload is huge.

v2.2 is up with wait timers properly working so keys should always be looted now, also adjusted detection range for wardens to avoid skipping them. The skipping may still happen from time to time but it should there should be an even smaller chance of it occurring than there was before.

This will farm the mobs there, no events are yet implemented but I think its the only FoM profile out there right now. http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-profiles/act-1/155960-field-misery-farm-key-bones.html

I have a pretty good idea why this is happening and I can't believe I didn't think of it before, this will be fixed after I get out of class.

Please upload the log file, that portion is not indicating any stucks and the levelareaid is showing the bot in fields of misery.

In regards to error 3whatever I have never had this issue but I do recall someone mentioning that error was resolved for hem upon completing all acts in campaign. It is possible a quest reset and not having a finished campaign could cause the error to occur again.

I've come to the conclusion that in DB's current state I can't really do anything about the bot every once in awhile skipping warden and moving on unfortunately. The way the code is setup is to load a profile upon detection of warden, the loaded profile then will move to and fight the warden. I...

Alright man, I'll be looking for it too.

Do you have the "Infernal Keys" box checked under the items tab in Trinity? I have wait timers in place as well as useobject tags for each key in every profile to make sure they get looted. Is it just with the a2 key? I'll look into this and see if I can replicate the issue.

<!--lines in here are commented out--> That's how you comment things out in XML I think. I'm on my phone at work though so I didn't actually test it.

Please upload logs, I haven't had these issues before. I have noticed though after killing the warden sometimes it will keep clearing for up to 30 seconds and then port to town, the whole time the bot has the usetownportal tag queued and is just trying to clear an area to avoid interruption...

Thanks for the appreciation man, I enjoy making profiles for the community to help others and it's always nice to get positive feedback for the work I put in.