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

Full Questing - All Acts - Complete

Status
Not open for further replies.
sry for my english

example
bot resuming the game from main menu

quest is - get the blood of ZK from two instances, VotA and CoB
but before this we already got the blood from one of them
and quest marker pinging only on one entrance Vault or Cave

but bot thinking we still havent the first bottle of blood and go to the both of this quest locations

Correct. This is a limitation within Demonbuddy - there is no way to detect which quest 'sub-step' we are one. This has been listed on the 1st page under known issues since day 1.
 
Failed to load profile: Element ResumeUseTownPortal is not supported. Please check your XML and try again. (<ResumeUseTownPortal force="False" timeLimit="30" />) Line 72
getting that everytime i try to start a new char and quest him through =\
 
Failed to load profile: Element ResumeUseTownPortal is not supported. Please check your XML and try again. (<ResumeUseTownPortal force="False" timeLimit="30" />) Line 72
getting that everytime i try to start a new char and quest him through =\
[14:29:04.993 N] Stopping the bot. Reason:[QuestTools] Forcing bot stop - high rate of games/hour detected: 57.5098952444318 Games/hour

getting both of these in act one get the second after running the guy to a checkpoint to try and fix the first. have the lastest version of trinity autoeqquiper and autoskilled. i even tried running without the autoeqquiper and autoskilled on and still get these errors

fixed didn't have the lastest questing tools installed but updated that and all works flawlessly again so far. thank you and good work on the profile rixx.
 
Last edited:
any1 know the approximate time required to level form 1 to 60 with this profile ?
 
I don't know if it's the new trinity, but current release with all newest stuff is nowhere near as reliable as it was a month ago. I am already tired of the babysitting and none of the bots had even left a1 yet =( Before they only required help with skeleton king and after that it was a cake-walk. Now they get stuck at the most random locations, get strange errors while questing and just die way too much =(
 
I don't know if it's the new trinity, but current release with all newest stuff is nowhere near as reliable as it was a month ago. I am already tired of the babysitting and none of the bots had even left a1 yet =( Before they only required help with skeleton king and after that it was a cake-walk. Now they get stuck at the most random locations, get strange errors while questing and just die way too much =(

Hmm sorry to hear that!

Would help me if you could keep a really basic log of where they get stuck, and also post any logfiles that have errors.

I've been running these 24/7, working on automatically restarting Acts and such now so it's even more reliable.

keep sending me logs... those help a lot when trying to debug!
 
The exact spot that I've had problems with 5/8 bots in act1 quest-wise is the Imprisoned angel. The part after you clear manor, before you get to agony level 1. Bots somehow get stuck between quest parts, refusing to take wp to manor and go to agony level 1. Had to do it manually. I will remember to get logs, when I encounter this one NM difficulty, for now they are past that and I can't really recreate what has happened -_-
 
Last edited:
The exact spot that I've had problems with 5/8 bots in act1 quest-wise is the Imprisoned angel. The part after you clear manor, before you get to agony level 1. Bots somehow get stuck between quest parts, refusing to take wp to manor and go to agony level 1. Had to do it manually.

Ok. Got a log? Then I can find all my ID's and such that i need to fix this...
 
I tried to find a log of this, but I have 8 bots running from the same folder, pretty much impossible to find relevant file on that folder, sorry. I will try to not forget and get a log when it's current, so I can pinpoint the exact time of this, because something tells me this will happen on NM too. Also some of my "bad experience" so far might be because of some other factors like latest equipper behaving very odd to say the least (I caught it trying to melee a boss just because he thought a white shield is fucking awesome and swapped his 2handed weapon out for it.), and autoskilled seems to be working much less reliably. I relied on those 2 addons heavily to level before also, though I realise I shouldn't be whining here anyway, just saying :D

PS. I don't mean to take away from the pure awesomeness this pack of profiles and plugins have been for me so far. Doing hell of a job here, man!
 
random stop where in act 1 during the broken blade quest after i defeated the clan members or w/e it didnt pick up the sword and got stuck up there... didnt fix after restart or anything
PS. did i ever tell you ive waited for over a month to hope youd finish this profile lol its the best thing yet and made it worth buying 2 of these keys
 
Last edited:
[08:22:18.899 N] Loaded profile [Act1] Fallen Star
[08:22:18.975 N] Bot started. Reloading item rules.
[08:22:19.034 N] [Items] Loaded Item Rules: Weight Based Item Rules
[08:22:19.206 N] Waiting 4.4 seconds before next game...
[08:22:23.603 N] Creating new game. Params: [Act:A1 Difficulty:Inferno Quest:87700 QuestStep:-1 ResumeFromSave:False IsPrivate:True Handicap:0]
[08:22:25.124 N] Closing error dialog
[08:22:54.337 N] Stopping the bot.
[08:22:54.363 N] Bot Thread Ended. Was this requested?
[08:23:04.902 N] Failed to load profile: Element SafeMoveTo is not supported. Please check your XML and try again. (<SafeMoveTo questId="87700" stepId="-1" actorId="3739" x="2837" y="2931" z="24" />) Line 70
[08:23:09.227 N] Loaded profile [Act1] Fallen Star
[08:23:09.227 N] Bot started. Reloading item rules.
[08:23:09.266 N] [Items] Loaded Item Rules: Weight Based Item Rules
[08:23:09.268 N] Waiting 11.3 seconds before next game...
[08:23:20.627 N] Creating new game. Params: [Act:A1 Difficulty:Inferno Quest:87700 QuestStep:-1 ResumeFromSave:False IsPrivate:True Handicap:0]
[08:23:22.148 N] Closing error dialog
[08:23:27.292 N] Stopping the bot.
[08:23:27.351 N] Bot Thread Ended. Was this requested?
[08:23:51.374 N] Loaded profile Start New Act 1 by rrrix
[08:23:53.812 N] Loaded profile Start New Act 1 by rrrix
[08:23:53.812 N] Bot started. Reloading item rules.
[08:23:53.852 N] [Items] Loaded Item Rules: Weight Based Item Rules
[08:23:53.853 N] Waiting 4.2 seconds before next game...
[08:23:58.138 N] Creating new game. Params: [Act:A1 Difficulty:Normal Quest:87700 QuestStep:-1 ResumeFromSave:False IsPrivate:True Handicap:0]
[08:24:02.332 N] GameChanged. Clearing actors
[08:24:02.371 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[08:24:02.642 N] Loaded profile Start New Act 1 by rrrix
[08:24:02.642 N] Game joined, Resetting profile caches.
[08:24:02.655 N] ========== Grid segmentation resetting!!! ============
[08:24:02.775 N] [GilesEquipper 1.7.1] Evaluated 'Adventuring Sash'. Points=23
[08:24:03.323 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:03.348 N] Profile completed
[08:24:03.348 N] Number of games completed:1
[08:24:03.608 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:03.872 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:04.136 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:04.408 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:04.675 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:04.943 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:05.213 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:05.485 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:05.759 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:06.031 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:06.301 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:06.571 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:06.845 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:07.112 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:07.387 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:07.661 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:07.927 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:08.219 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:08.510 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:08.791 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:09.062 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:09.330 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70
[08:24:09.587 N] Stopping the bot.
[08:24:09.603 N] Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor actorId="191492" questId="1" />) Line 70

Repeats self. Been away from the bot game for a half a year now its all Chinese for me. Will donate once its running and not just staring at mobs (can't get it to do that yet). Much love.

edit: I will re-download DB and try again. I get the same error on both this and the beta version.
edit: Same error tried double checking my XMLs but its still spitting out the error blah carpal tunnel ....
 
Last edited:
This is more than likely the wrong forum, so sorry, but how do I stop it from picking up all common items? I have every addon listed in OP that can be used for this, click Set Questing, and its picking up every common item :(
 
just reload profile for ethernity and stay at one place forever and casts skills

i am using YAR

gKB6W9O.jpg


3304 2013-03-04 12.27.zip
 

Attachments

  • gKB6W9O.webp
    gKB6W9O.webp
    65 KB · Views: 83
the same shit without YAR and with last trinity...

bot cant join into the ghom's location
 
i did fresh install and start Act3 from the beginning - nothing change
fix this pls
 
Hi.
I just started this and trying this one out.
What i done is that i made a fresh install of DB and unziped your files the that directory.
But when i chose Trinity as combat routine DB crashes.

Cant solve this one so i turn here :)
Log attached
 

Attachments

Runnig nice without so called fresh install but I've noticed something.
During these little "cutscenes" after killing Leoric or rescuing Decard bot is moving in the background. No idea if there's a way to check it by Blizzard that you are running your character while movie is playing ;P
However, is it possible to make the bot skip these things like it skips bosses talking (Ghom, Zoltan etc.)?

//Edit
Little update. During Butcher fight bot tries to stand in one spot (near entrance location) what causes hell of a trouble to not die ;)
Is it only my bot or is it known issue? ;>

//Edit 2
Little more feedback. While my char was in Act I I started the profile with char already in game. Everything went fine and bot continued to walk from the point I got to. But in Act II he didn't want to resume under the same conditions. I had to leave the game and than start the bot.
Attaching log file from this 'event'.
 

Attachments

Last edited:
Leveling my second character with this profile, and I have to say it's incredible. The profile is actually too good sometimes, like just now I reached the skeleton king being only level 7 so I couldn't kill him :D
But with some sporadic supervision this is an amazingly nice way to level.
 
Status
Not open for further replies.
Back
Top