[A3 Inferno] Alkaizer RUN Gnome Proof - Unstuckable

after close DB to tray fckng radsatom stop working and bot stuck somewhere and spam to log:

Code:

[21:08:44.312 N] Loaded profile 06 v2.7 public [Galkaizer] The Keep Depths Level 2: Random Optimized SEARCH
[21:08:44.375 N] ToggleTargeting, new values: Looting:True LootRadius:50 Combat:True KillRadius:25
[21:08:44.421 N] Kill radius is set to 25 you might want to manual edit 06_keeplevel2.xml file to your likes.
[21:08:45.625 N] Interacting with object g_Portal_Rectangle_Orange-10407
[21:08:51.718 N] ========== Grid segmentation resetting!!! ============
[21:11:28.281 N] [RadsAtom] - Inactivty thead is Closing.
[21:11:28.296 N] [RadsAtom] - MrWorker thead is Closing.
[21:17:05.890 N] The Run is over
[21:17:06.281 N] Loaded profile 07 v2.7 public [Galkaizer] - The Profile Completed -
[21:17:06.453 N] Using town portal
[21:17:14.703 N] Using town portal
[21:17:21.718 N] ========== Grid segmentation resetting!!! ============
[21:17:22.062 N] Using town portal
[21:17:26.781 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:17:26.781 N] [RadsAtom] - Resetting the deathcounter.
[21:17:26.781 N] [RadsAtom] - Leaving the game.
[21:17:26.843 N] Profile completed
[21:17:26.843 N] Number of games completed:1
[21:17:31.875 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:17:31.875 N] [RadsAtom] - Resetting the deathcounter.
[21:17:31.875 N] [RadsAtom] - Leaving the game.
[21:17:36.890 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:17:36.890 N] [RadsAtom] - Resetting the deathcounter.
[21:17:36.890 N] [RadsAtom] - Leaving the game.
[21:17:41.937 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:17:41.937 N] [RadsAtom] - Resetting the deathcounter.
[21:17:41.937 N] [RadsAtom] - Leaving the game.
[21:17:46.953 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:17:46.953 N] [RadsAtom] - Resetting the deathcounter.
[21:17:46.953 N] [RadsAtom] - Leaving the game.
[21:17:52.031 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:17:52.031 N] [RadsAtom] - Resetting the deathcounter.
[21:17:52.031 N] [RadsAtom] - Leaving the game.
[21:17:57.109 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:17:57.109 N] [RadsAtom] - Resetting the deathcounter.
[21:17:57.109 N] [RadsAtom] - Leaving the game.
[21:18:02.140 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:18:02.140 N] [RadsAtom] - Resetting the deathcounter.
[21:18:02.140 N] [RadsAtom] - Leaving the game.
[21:18:07.203 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:18:07.203 N] [RadsAtom] - Resetting the deathcounter.
[21:18:07.203 N] [RadsAtom] - Leaving the game.
[21:18:12.234 N] [RadsAtom] - Loading next profile: C:\Games\Dblast\!Routes\Alkaizer Pure v2.7.1 TRINM -  public\00_Gnome_START_HERE.xml
[21:18:12.234 N] [RadsAtom] - Resetting the deathcounter.
[21:18:12.234 N] [RadsAtom] - Leaving the game.

 

Pardon me for saying this, but statistics? Is it hard to do this on your own? Run the profile you will know after first few runs it's smooth, and indeed top level profile.

I have reason to believe this statistics race could have been the undoing of many resulting in bans. Lots of people talk about optimizations and highest GPH. Problem is this, it's a profile, run by a bot, it will peak at bot level, and never at human play level. This said, these numbers could tip off bliz on another thing to look for.

And if we going to go for an item drop again, alright, well when you 'COMPARE' any run to this via renamed alk runs that are not only fake, but also flawed due to not even doing alk run procedures that comparisons are irrelevant. I know simply if I want to destroy GPH, and XP per hour of any profile, simply remove AC2, and run only AOC, TOWER1, FOS, and KD2 will produce numbers no profile can keep up to. < I have extensively tested this. The moment you compare with a Rakkis crossing profile your totally adding variables completely different. If you do want to compare to tincopy profile, then perhaps you should rethink your question due to the facts tincopy isn't not an Alk run what so ever, so compare is stupid.

I see high volume running a 'single file' profile to me = extremely dangerous, we will just watch and see. Sounds like warning flags everywhere. So much easier for a bliz tech to zero in on those. HOWEVER: all this said, I still do not believe that profile behavior resulted in any bans, but if it did, please read above again.

The resulting "RACE" for best stat profile should be a second hand thing to .... 'non' sticking profiles 'non' bad loop profiles and 'non' crash profiles. These three things are so much more important than GPH and XP/per hour.

Besides my lvl 70 paragons were producing 650kGPH, and 27 - 35k xp, and my lvl 30 paragon produce 20mil and 350GPH. So until you can show me a logical way of doing any item drop and xp drop compare, I really think the results of that are of no need. Bug reports, and non crashes are top priority. Everyone is entitled to an opinion, and this one is mine. There are so many variables, however; those wanting to post stats, do so at your own caution.

 

Thank you very much, I am about to address this by removing Atom need in this profile, as I wrote UFR to not use RadsAtom at all I have learned how to make functional profile without rads. I will complete this very soon, some testing is required.

I wish I knew why this loop happens, however I do not. The best way to combat it is to use Trinity reloads, and remove rads. I know rads can be stable and can be unstable. It's to bad someone can't re-write it to be a lot more stable, in future I will look into mater in depth.

Usually the only way to stop that bug is close db, and restart.

 

[21:08:44.312 N] Loaded profile 06 v2.7 public [Galkaizer] The Keep Depths Level 2: Random Optimized SEARCH
[21:08:44.375 N] ToggleTargeting, new values: Looting:True LootRadius:50 Combat:True KillRadius:25
[21:08:44.421 N] Kill radius is set to 25 you might want to manual edit 06_keeplevel2.xml file to your likes.
[21:08:45.625 N] Interacting with object g_Portal_Rectangle_Orange-10407
[21:08:51.718 N] ========== Grid segmentation resetting!!! ============
[21:11:28.281 N] [RadsAtom] - Inactivty thead is Closing.
[21:11:28.296 N] [RadsAtom] - MrWorker thead is Closing.
[21:17:05.890 N] The Run is over

Do you know if it completed the KD2 dungeon properly?

 

where is it? how to use that? some link plzzz....

 

yes normal. bot use town portal and then go to loop

 

thank you that will source the problem, I can already figure it out just based on this info I know what is wrong.

I am about to push a NONRADS version, in a few moments.

 

didnt see that coming... just to clarify im not comparing your profile to anything i hope non offense taken, but still dont you think that IPH/GPH/XPH is an important part of profile valuation ?
btw i did not ask for a log only a few estimated numbers

 

Would be nice to know what bloody quest do I start this on?

 

This profile has the original quest fixer, unlike copies, you can simply load the 001 jump start file, it will select proper quest, and then loop properly.

 

NON RADS VERSION POSTED PLEASE SEE FIRST POST IN TOPIC

This is a testing version, only had an hour to test... sorry if there is any bug, please post reports here.

 

none taken bud, there are some views that I have to establish, and warnings to people who continuous use exact same profile... beware of this, this is behavioural and could be a bad botting experience, not sure yet, as I compile a ban database to compare results to find similarities.


However if you just mad rush for best profile and items, and gold per hour, you are in the right place.

 

Thanks for the reply!

 

Possibly fixed exit game after complete KD2...

and probably not... try 2.7.3

I have to go to city on business, sorry I can not fix this until i get back..

 

ya sorry .. doesn't fix the exit game..

 

It seems I spoke too fast....it is not working properly with YAR. When db crashes, or d3 crashes, or yar crashes,or you manually close db, I'm getting this error on db when trying to restart the profile:

---------------------------
Failed to load profile:Element Continue is not supported.Please check your XML and try again.(<Continue profile="02_core.xml">) Line 23

---------------------------
And then db error window with:

There is no profile loaded. Please load a profile before starting the bot.
---------------------------
It's happening with both jumpstart.xml and start_here.xml....didn't tried non atom version cause I use 2 profiles that require rads atom (I would gladly see it go or get updated)

 

Radsatom version crashes every 5 minutes. Tried the new non rads version and 3/4 the way thru AC2 it backtracked about 50% of the way then finished the run (or so I thought) then ran back to the entrance triggering the gold inactivity timer. Let it restart and it actually finished a run but instead of leaving the game and resuming it just took the waypoint back to core of arreat as if it thought it reset the game.

 

This was acknowledged already. Please remember this version was tested EXTENSIVELY with 293 db, and of course has been issue for 294, most of which were fixed.

The update to no rads is on it's way now to fix.

The AC2 back trace you experience was not made clear enough in earlier post I guess. I DO NOT HAVE FULL CONTROL OVER Trinity or DB. If I did, I would re-write the explorecode right now. However; I am already doing that with trinity xml.

This map trace and tolerance was adjusted and working amazing. 293. ask any tester there was zero issue with it, looks like I have to slightly tweak it again for 294. I am not sure why the change, other than I have to fix it to run the way I want it.

K, need to keep this short, I have to complete the 1.7.4 test, and release solid non atom version.

BTW; if you are crashing in 1.7 with a rads atom version, please tell your trinity version, I have a feeling that's the problem.

as stated above, I am going to abandon atom 1.5.1 until I get chance to recode it, db without rads is so much more reliable.

I will test and get a working version supporting Yar asap.

 

Element continue not supported means that rads isn't working properly, because Continue profile is rads tag.

 

Fyi, I'm running db 294 and Beta (2 separate folders) , and trinity 1.7.1.10. ----Radsatom 1.5.1.