Using Giles 1.6.3.4. I am also using GilesBattleRoutine, which seems to work pretty well for my purposes.
Are you using a radsatom? thanks man. My guy just stands there and doesnt move when I do get it loaded. Thanks
Both the most up-to-date RadsAtom and GilesTrinity are in on the first page of this post. In terms of the combat routine, however, can be found here: http://www.thebuddyforum.com/demonbuddy-forum/plugins/giles-plugins/70841-trinity-download-here-v1-6-3-4-a.html Edit: Yes, I am using RadsAtom.
I have restarted my computer, downloaded again the entire new DB file for this patch, radsatom 1.5.1 from this first page, and trinity 1.6.3.4. Now it is loading up (Alkaier pure 2.4) but starting in ACT 1 and not moving. WTH. Any ideas. Thanks again Negotiator
So, you are loading the profile and then pressing "Start Bot" on the DB application screen? Do you have all of the waypoints in Act III? Make sure you are allowing DB to start the game, it starts and stops them on their own. Not sure what else could be the issue. As long as you press "Load", find the folder, open the one with "Load me first!" in the file name and press "Start Bot", everything should simply work.
I figured out my issue and this may help others. For some reason I just had to create a game on my own in act 3, then leave, then start this profile. Working fine now. Last question, for this pure 2.4 what file do you load first? JumpStart_loadmefirst, or Gnome_start_here? thanks so much.
Well this is sad. Today I found my char standing in KD2 and restarting the game. I don't know how it happened since there is no log for it, however the thing is that now when the start profile does "resume" I don't think there is a way "unstuck" character if something goes wrong. Any ideas?
Is there any way to have the bot run into Ice Caves or any other random dungeons? Just curious... wondering if I downloaded an older one.
Same problem, if i use yetanotherrelogger and it's try to connect from login/password. If i login manually it's ok. Start xml 00_Gnome_START_HERE.xml with checkpoint near azmo. add. 35xp/hour, 450k g/h. 150k dps ww barb cm2 with 24% ms.
2.4 is working perfectly for me now. Been running almost 24hours without problems. The first time i ran the script i started the one where he runs through the core to the Azmo checkpoint and from then on he ran it all perfectly for several hours. This morning i checked the stash and when i resumed the bot he loaded random Keep 2 map and he got stuck. So i loaded the core one manually and all is working well again. conclusion: always make sure he loads the right profile About 2.4 it's a great and stable version which increased my gph and xph by quite a bit in comparison with the 2.98d which i was running before.
Load me first is intended to start the correct quest number and starting point, after that the profile never uses 'Load Me First' again, it loops to Gnome_start_here later to be renamed for logic reasons. So Load Me First -- > then Gnome_start_here then main body of profile, then it loops to Gnome_start_here ignoring Load Me First. In the versions I am working at now, it actually brings the Load Me First profile back into play to address repairs / corrections to using a break timer. Very excited about this new feature I will be adding to make this profile not only unstuckable but also unstoppable! I will take a later post here and list some new features coming to the run, and some explanation of why this profile is differant that others why others can work and why this one can do the bug thing (insert always coders fault).
The Next Part of reply from people I would like the following: List of what you believe to be the easiest to run and stable versions that you have found. I can list a few that I see the version id for from reading the topic. These will be added as 'Stable' releases in place of where version 3 is on first post. No worries version 3 is being worked on, version 2 isn't done yet. - Known stable release by reading done here ver 1.0 Rate 8.5 / 10 (don't read much about it, but it's a great fall back nearly fool proof please re-rate accordingly) ver 2.98d Rate 9.5 / 10 (read a lot of good reports about this version) I hope this is a good basic guide, this will help me a lot due to my future ideas with profiles, some future ideas. - dungeon 2 was worked on forever, it's now nearly where we want it, the current fix could be applied to all downloadable versions - version numbers added to every version ( you are seeing this change now in version 2.4 and a few previous ) - Coffee breaks added! experimental, this is for debug purposes only, we are concerned it might make for larger log files in db, in testing now. - fixer code, bot will know it's in the wrong place and reset back to the main 'load me first', this will accompany using break timers, loggers (rads or YAR) - testing all beta codes to existing plugins - add versions that do need rads atoms and do not - implement strict targeting distances - specialized profile for demon hunter, will also work for any ranged ( this is entire rework won't be anytime soon ) - implement alkazier run path in FOS ( all new paths ) - implement alternative runs of a few key areas, Tower 1, and FOS, AOC - remove use of door to dungeon 3 - Optimize dungeon 2 path nodes - box tol, reducing cpu needs - more fine tuning of AC2 Short of that... keep up the good work on bug reports.
Working pretty good, however... It'd be a lot better if it did support the new trinity and newest atom... http://www.thebuddyforum.com/demonb.../91188-unified-trinity-community-edition.html http://www.thebuddyforum.com/demonbuddy-forum/plugins/86785-beta-test-atom-2-0-15-a.html
Quick fix for anyone stuck on a tabel, Deal with Fire Walker boots, it will destroy any obsticle the bot may get stuck on (If it gets stuck) Also change your kill radius down from 45 to 30 to reduce having your character getting stuck on a wall while trying to attack a mob on the other side of it. This is a great profile, Enjoy it very much and after a little more tweaking is done i would probably pay money for use of this profile. Using 2.99.2 Ran 7 hours, 1 stuck minor issue on my end.