DMO Bugs

[Deficator]

For my gear and paragon level I should be able to clear higher 70's. I can farm 71 easy with 5 minutes to spare or more at times but this is only when using Trinity .19 version. I'm using the newest DB and newest Trinity with the modifications to the combat, but the bot still seems to get hung up on single trash mobs. I've tried adjusting trash range, pack size, everything, but I can't seem to find a way to correct the problem and it is slowing down my runs significant;y to the point I'm failing 72s. I cleared 72 with 3 minutes left prior to the D3 mini patch.

 

[Fisher67]

Check page 3 of this thread.

Fisher, I'm afraid I won't do that today, sorry, too late already. I'll try it tomorrow most likely.

That's fine! I'll be testing myself tonight when I get home from work.

hey Fisher67 what .CS are you using File Type: cs WizardCombat.cs (44.4 KB, 12 views)
File Type: cs Enemies.cs (5.6 KB, 10 views) or the one from the 2nd page ?

I attached my current file in my guide. I'm going to try out Jubisman's file tonight. If it is superior, I'll attach that one.

For my gear and paragon level I should be able to clear higher 70's. I can farm 71 easy with 5 minutes to spare or more at times but this is only when using Trinity .19 version. I'm using the newest DB and newest Trinity with the modifications to the combat, but the bot still seems to get hung up on single trash mobs. I've tried adjusting trash range, pack size, everything, but I can't seem to find a way to correct the problem and it is slowing down my runs significant;y to the point I'm failing 72s. I cleared 72 with 3 minutes left prior to the D3 mini patch.

Check out my guide: https://www.thebuddyforum.com/demon...238762-2-4-dmo-db-wizard-guide-70-grifts.html

 

[jensenbeach772]

o hey Fisher67 i was wondering are you going to make a Trinity for Flash Fire for farming T10 ?

 

[Fisher67]

o hey Fisher67 i was wondering are you going to make a Trinity for Flash Fire for farming T10 ?

I use LoN one-punch monk for farming. The speed of that build is far superior to flashfire in my opinion. It does pretty much everything else in the game really well too except for Grifts past 55.

I am planning on making a farming guide with that build, probably not flashfire though. I'm waiting for Jubisman to fix this issue before I make the guide: https://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/238678-unstucker-failing.html

 

[jensenbeach772]

ok man

 

[Ehnoah]

Wrong Thread. NVM

 

[jubisman]

For my gear and paragon level I should be able to clear higher 70's. I can farm 71 easy with 5 minutes to spare or more at times but this is only when using Trinity .19 version. I'm using the newest DB and newest Trinity with the modifications to the combat, but the bot still seems to get hung up on single trash mobs. I've tried adjusting trash range, pack size, everything, but I can't seem to find a way to correct the problem and it is slowing down my runs significant;y to the point I'm failing 72s. I cleared 72 with 3 minutes left prior to the D3 mini patch.

I can revert the only change that could've done this since .19, but if I do it I'm going to go ahead and ignore any and all complaints about dmo wiz not getting close enough to mobs to proc the orbs.

 

[Fisher67]

I can revert the only change that could've done this since .19, but if I do it I'm going to go ahead and ignore any and all complaints about dmo wiz not getting close enough to mobs to proc the orbs.

Please let me do some testing tonight before you make any final decisions!

 

[Deficator]

I can revert the only change that could've done this since .19, but if I do it I'm going to go ahead and ignore any and all complaints about dmo wiz not getting close enough to mobs to proc the orbs.

I'm not sure if the problem is entirely with DMO or Trinity itself. It seems like the combat sliders for trash mobs and such just get ignored by the bot. It does not seem to obey pack size or range and it just gets hung up on a single mob. For the most part the range at which the bot stands is fine, occasionally I'll have to force move it into a pack and everything blows up. This is just my experience as of late. Thank you for your work.

 

[jubisman]

Please let me do some testing tonight before you make any final decisions!

Don't worry, I'll wait for your feedback .

I'm not sure if the problem is entirely with DMO or Trinity itself. It seems like the combat sliders for trash mobs and such just get ignored by the bot. It does not seem to obey pack size or range and it just gets hung up on a single mob. For the most part the range at which the bot stands is fine, occasionally I'll have to force move it into a pack and everything blows up. This is just my experience as of late. Thank you for your work.

AFAIK those settings are working properly. Could be something to do with your misc combat settings. Could you please post a screenshot of them here?

 

[Fisher67]

I'm not sure if the problem is entirely with DMO or Trinity itself. It seems like the combat sliders for trash mobs and such just get ignored by the bot. It does not seem to obey pack size or range and it just gets hung up on a single mob. For the most part the range at which the bot stands is fine, occasionally I'll have to force move it into a pack and everything blows up. This is just my experience as of late. Thank you for your work.

Have you followed my guide? Should fix the problem.

https://www.thebuddyforum.com/demon...238762-2-4-dmo-db-wizard-guide-70-grifts.html

 

[Deficator]

@Fisher, I have tried your trinity settings and I did not notice a difference. Trying your settings again though.

My current settings are a result of tweaking the options while the bot runs attempting to get a better performance.

 

[jubisman]

Try increasing you 'Ignore trash further away than' to 60 or so. See if that helps

 

[Fisher67]

Try increasing you 'Ignore trash further away than' to 60 or so. See if that helps

Also make sure you have the right skills, items, and combat file I posted in the guide. Trust me, it's something wrong on your end, you just gotta figure it out!

 

[semial1337]

From what ive noticed if you set it to always attack elites in clusters it ignores elites form time to time when it runs out of trash in search of a new cluster. Meaning that it will port away and often leave low hp elites behind

 

[jubisman]

From what ive noticed if you set it to always attack elites in clusters it ignores elites form time to time when it runs out of trash in search of a new cluster. Meaning that it will port away and often leave low hp elites behind

You probably got the wrong impression. All that option does is override any 'Ignore X Elites' that you may have checked.

 

[semial1337]

You probably got the wrong impression. All that option does is override any 'Ignore X Elites' that you may have checked.

I might have, but none the less it only seems happens when i have that option checked must be a coincidence then hehe

 

[Fisher67]

It works almost exactly the same as Calamity though.

Also can you try this? I coded what you asked for in a kind of roundabout way, so I'm hoping it'll help a bit.

Ok, here are the results on Grift 70. Still using calamity rune instead of safe passage on teleport and using exact settings on my guide, I ran 3 Grifts for each combat file. I copied the entire directory I was previously using and installed the new files in the copy directory (to make sure everything else was equal).

Round 1
From the combat files here (see attached log file "new"):

• First Run: 19:32:04.402 INFO Logger [Adventurer][Rift] All done. (Total Time: 8 mins 42 seconds)
• Second Run: 19:46:55.849 INFO Logger [Adventurer][Rift] All done. (Total Time: 13 mins 24 seconds)
• Third Run: 19:56:47.778 INFO Logger [Adventurer][Rift] All done. (Total Time: 8 mins 40 seconds)
• Average Time: 10 mins 15 seconds

Observations:

• Did not teleport enough (calamity requires more teleport to perma stun them, this is really really important in higher Grifts). Something was overriding the minimum 500ms teleport combat delay and it was waiting longer. This put the bot at risk and caused a death. There were more close calls in general.
• Bot noticeably tried to explode in densest part of trash pack, which was really cool to watch
• Occasionally, bot would get stuck in places it hadn't been stuck before, just sitting there while trash hit it

Round 2
From the combat file here (see attached log file "old"):

• First Run: 20:27:37.890 INFO Logger [Adventurer][Rift] All done. (Total Time: 10 mins 4 seconds)
• Second Run: 20:41:45.542 INFO Logger [Adventurer][Rift] All done. (Total Time: 12 mins 33 seconds)
• Third Run: 20:51:27.074 INFO Logger [Adventurer][Rift] All done. (Total Time: 8 mins 30 seconds)
• Average Time: 10 mins 22 seconds

Observations:

• Bot behavior was much smoother.
• No deaths, survivability far superior, had bad luck on rift density
• Bot would sometimes skirt around dense trash packs

Hard to make conclusions based on only 6 Grifts, but hope this helps. Honestly, if you could include a simple routine to explode in the center of densest trash packs without messing with the teleport delay, the "Round 2" combat file would be flawless for DMO in my opinion.

 

[jubisman]

Hey, thanks for the very nice feedback Fisher. I'll see if I can work something out to make it avoid staying in the outskirts of clusters.

 

[Deficator]

Just posting some feedback:

Modified my settings to increase trash radius to 60 and fixed the rest of my misc combat settings to mirror Fisher's. I have been getting faster times on 72s, much better than before when it would either fail the time or make it with less than 1 minute left. I am using traditional DMO, not the Unity set up. Thank you for the support. My previous settings were settings that were successful for 72s with Trinity .19 but seem to no longer be effective with Trinity .31. Thank you for all the help.