Full Questing - All Acts - Complete

[dumptruck]

new gilestrinity 1.6.3.4 v24 mod by myself uploaded to first post of this thread.

Please let me know how it works!

merged all "unified v24" changes into this version, including nesox's inactivity timer fix and ww barb fixes
shrines are used correctly.
Now attacks and kills belial
item pickup prioritization changed slightly
correctly uses health wells when available -- needs more testing with the butcher

yessss!!!!!!!!!!!!!!!!!!!!!!! <3

 

[rrrix]

Just curious if you changed some of the problems with the unified version? It has some problems of it's own with the ww whirling away from enemies including azmodan. I actually stopped using it and went back to bombastic's version which I find works much smoother in general.

I've had this happen a few times too. I'll stare at the FindZigZagTargetLocation method tonight and see if I can make sense of it.

 

[Shinyknight]

The *only* issue I've had with it thus far is picking up the Khazra Staff in Act 1... It finds it, but refuses to click on it and move on, so it reloads over and over, heh.

Any chance of posting a donation link, perhaps?

 

[DBXion]

EDIT: NVM - User error, edited the files and then kept using the un-edited copies I made as backups....

 

[Gandalf]

[13:31:23.325 N] Failed to load profile: Element SafeMoveTo is not supported. Please check your XML and try again. (<SafeMoveTo questId="93595" stepId="8" pathPrecision="5" x="103.8487" y="85.005" z="25.38465" />) Line 48


Always have this error if i want to load the resumable version of your profiles with newest DB. Any idea how to solve?

Edit: Fixxed user error sorry

 

[mrnguyen]

not working after demon update. When I load act 3 profile, it can run the whole act, and I choose act 3_start when it finishes act 3 run in order to create another act 3 run, but after the update, the act 3_start can't work again.

 

[lckwjl]

testing WD now

 

[rrrix]

not working after demon update. When I load act 3 profile, it can run the whole act, and I choose act 3_start when it finishes act 3 run in order to create another act 3 run, but after the update, the act 3_start can't work again.

Logs...

 

[lckwjl]

Ive been using this four a couple hours! It is great
It is not 100% afkable like you said; but I can watch tv and just help it when it gets stuck or confused.
9/10*s! great job
Using WD will test all acts

 

[joe3563]

Good stuff. Biggest issue is that the bot sucks in dungeons and places like The Keep. Shame we can't get some logic in place that will keep the bot from needlessly back tracking into areas already explored.

 

[strepie]

Good stuff. Biggest issue is that the bot sucks in dungeons and places like The Keep. Shame we can't get some logic in place that will keep the bot from needlessly back tracking into areas already explored.

You mean something like this?
(from DB notes)
"Added attribute "ignoreGridReset" to the ExploreArea tag if set to true it will ignore resetting the segmentation grid when the tag starts and finish, can be usefull if you use 2 explore area tags in a row to avoid re-exploring already explored areas."

 

[Blabus42]

bot sometimes get stuck when trying to destroy obstacles which cant be destroyed, is there is a easy way to edit the blacklist?
trying to figure out if its caused by your plugin or DB itself.
btw. is your Plugin "DestroyBarricades" still needed since lastest DB added "Should always destroy barricades now if possible."?

 

[rrrix]

You mean something like this?
(from DB notes)
"Added attribute "ignoreGridReset" to the ExploreArea tag if set to true it will ignore resetting the segmentation grid when the tag starts and finish, can be usefull if you use 2 explore area tags in a row to avoid re-exploring already explored areas."

Almost! The path DungeonExplorer in Demonbuddy tends to explore a direction X grid squares, and identifies it missed a grid square way back there (which is usually just a corner of a room or something) so it will backtrack to get there. All this happens without a grid reset.

ignoreGridReset is useful in situations like Cathedral Level 3, where you have to explore to find the Warrior, then explore again to find his chest, and then explore again to find Jondar, but don't want to explore the areas you've already explored.

 

[rrrix]

bot sometimes get stuck when trying to destroy obstacles which cant be destroyed, is there is a easy way to edit the blacklist?
trying to figure out if its caused by your plugin or DB itself.
btw. is your Plugin "DestroyBarricades" still needed since lastest DB added "Should always destroy barricades now if possible."?

Not if you're using Trinity. Trinity (even the one i modified) still has a few bugs where it doesn't correctly destroy large desctructables and barricades within range.

When I recently tested Belphegor, it didn't quite work as well as hoped either

I still use it.

 

[strepie]

Almost! The path DungeonExplorer in Demonbuddy tends to explore a direction X grid squares, and identifies it missed a grid square way back there (which is usually just a corner of a room or something) so it will backtrack to get there. All this happens without a grid reset.

ignoreGridReset is useful in situations like Cathedral Level 3, where you have to explore to find the Warrior, then explore again to find his chest, and then explore again to find Jondar, but don't want to explore the areas you've already explored.

Aah...now I think I understand. Thx for explaining rrrix. Maybe hopefully someday soon Nesox or another dev will give us an early Christmas gift and add something to the code that will help you guys. We can but hope eh?
Btw thanks again for these profiles - they're awesome.

 

[hermes]

plugins dosnt work for me
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 57

 

[Pocketrocket]

[14:25:52.969 N] ========== Grid segmentation resetting!!! ============
[14:25:54.999 N] [DestroyBarricades] Destroying DestructibleLootContainer trDun_Crypt_Urn_Group_A_03-10183 at <411.6033, 348.875, 0.170166> distance: 7
[14:25:56.159 N] ========== Grid segmentation resetting!!! ============
[14:25:57.129 N] ========== Grid segmentation resetting!!! ============
[14:25:59.149 N] [DestroyBarricades] Destroying DestructibleLootContainer trDun_Crypt_Urn_Group_A_03-10260 at <411.6033, 348.875, 0.170166> distance: 7
[14:26:00.259 N] ========== Grid segmentation resetting!!! ============
[14:26:01.270 N] ========== Grid segmentation resetting!!! ============
[14:26:02.750 N] [DestroyBarricades] Destroying DestructibleLootContainer trDun_Crypt_Urn_Group_A_03-10327 at <410.2607, 330.0197, 0.1701555> distance: 12
[14:26:03.840 N] ========== Grid segmentation resetting!!! ============
[14:26:04.810 N] ========== Grid segmentation resetting!!! ============
[14:26:06.000 N] ========== Grid segmentation resetting!!! ============


Act 1 bot keeps entering and leaving blue path that leads to DEFILED CRYPT from CEMETERY OF THE FORSAKEN , going in and out for 5 minutes now

apparently it is looking for the right CRYPT and once it gets in and decides to leave it forgets that this isnt the right one and enters AGAIN

 

[Pyck]

Nice.. thanks!

 

[dedfriendly]

Where do i input the no grid reset code

 

[dudubiton]

First, I have to thank you for the great job. LVLed 2 chars already with it.

Second, there is seems like an issues with goblin priority in the last Trinity, please check it, cause i've seen that it let them go. I was never using Kamikaze for them, but Prioritize worked just well before that last update.

Last, the bot was very barricade aggresive week ago and now it takes him 1-3 seconds to stand near before he smash it, if ever. I tried both with barricades plugin and without it. Any suggestion?

EDIT: Just saw it follows goblin up until he almost died, then let it go on last 5% hp, thankfully it died of rend debuff. And it almost never use Furious charge, that's a pity since it can do good fury regen.