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

Trinity 1.7.3.8

Status
Not open for further replies.
thanks for the mention! tbh I can't exactly remember what I contributed, but I'm elated it helped

Also digging the 'Known Issues' 2nd post, hopefully helps keep down redundant reporting ;)

EDIT: After trying to use 1.7.3.8, my 0 dog WD doesn't spam summon dogs. it seems like he's waiting the full timer even though I can resummon immediately. No problem sacrificing dogs, just won't replace them and hacks away at mobs with his sword since he can't sacrifice.
 
Bats are working much better! Thank you so much. I am quite happy with this version so far!

Couple observations:

* Will sometimes use bats to clear debris, this is a waste of mana due to the initial mana cost of bats. A rule to never use bats to clear debris might do the trick.

* Short bursts of bats are observed. This is always a bad use of bats and depletes mana quick. Bats should be used when there is time to channel and in turn ramp up the damage. Quick "1 shots" should use another offense.

* When channeling bats in an RD pack, spirit walk needs to be used to offset the damage being reflected (which can easily kill a WD with high crit damage)

* Bat channeling and other skills could be better "understood" by the bot. For example: If you have corpse spiders/widowmakers and hex/jinx both configured as skills in addition to bats, it would be nice if the bot knew that WHILE CHANNELING BATS that using HEX/JINX at the same time does NOT interrupt the bat channeling but using corpse spiders does (creating the need to consume the bats initial mana cost again to start it back up).

The following skills can be used at the SAME time while channeling bats and does NOT interrupt bat channeling (this is key to huge damage):

(1) Spirit Walk
(2) Soul Harvest
(3) Hex/Jinx

Will keep observing and report :)
Thanks rrrix and all!

Edit: corrected typos :rolleyes:
 
hmm .. I get a way higher CPU-usage with .8 ... FoM MP10 Eliteskipping with my Barbs becomes quite a Diashow (with latest non Beta DB .317)
 
Unfortunately I also have the same issue again, bot will not repair. Just stands in town with "red" gear. I may have to revert to .5 :( Method of upgrading from .5 to .8 was unzip, overwrite all files. Am i missing something maybe?
Thanks!

EDIT: Attached a log file

[18:44:24.461 Q] [Trinity] Player is dead
[18:44:24.463 N] [Trinity] Items may need repair, now running town-run routine.
[18:44:24.475 V] [Trinity] It appears we need to town run but can't: Cannot use town portal yet. Recall button is not enabled!
[18:44:24.591 N] [Trinity] Durability is zero, emergency leave game
[18:45:09.139 N] Closing error dialog
[18:45:09.258 D] System.NullReferenceException: Object reference not set to an instance of an object.
at Zeta.Internals.Actors.DiaUnit.get_HitpointsCurrent()
at Zeta.Internals.Actors.DiaUnit.get_IsDead()
at Trinity.DbProvider.DeathHandler.TrinityDeathSafetyCheck() in c:\db\plugins\Trinity\DbProvider\DeathHandler.cs:line 27
at Trinity.DbProvider.DeathHandler.<CreateDeathHandler>b__0(Object ret) in c:\db\plugins\Trinity\DbProvider\DeathHandler.cs:line 20
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.CommonBot.BotMain.()
[18:45:11.145 N] Waiting 4 seconds before next game...
[18:45:15.214 N] Creating new game. Params: [Act:A3 Difficulty:Inferno Quest:101758 QuestStep:1 ResumeFromSave:False IsPrivate:True Handicap:10]
[18:45:16.738 N] Waiting 5.4 seconds before next game...
[18:45:20.849 N] ========== Grid segmentation resetting!!! ============
[18:45:20.849 N] GameChanged. Clearing actors
[18:45:21.204 N] Loaded profile Stonefort by rrrix
[18:45:22.106 N] [Trinity] New Game - resetting everything
[18:45:22.223 N] Creating new game. Params: [Act:A3 Difficulty:Inferno Quest:101758 QuestStep:1 ResumeFromSave:False IsPrivate:True Handicap:10]
[18:45:25.393 D] Parsing parent type table: 167097204
[18:45:25.414 D] Replaced hook [ProfileOrderBehavior_Hook] 85d19faa-7325-4fbf-be9e-cb836a239d58
[18:45:25.417 N] Closing error dialog
 

Attachments

d3pt said:
Excellent job!

I got a feature request tho: Sometimes my barb gets stuck in mobs trying to collect items. Is it possible to use WW (out of combat) to go to the object?
Click to expand...

This is already there, so, who knows what it was trying to do. The DB 'status bar' usually tells what Trinity is trying to do.

Kevin Spacey said:
awesome job! rrrix are you working on DB too? or to whom i must link this problem?
Click to expand...

That's Nesox - maybe request it in the DB Beta thread?

Tinnvec said:
thanks for the mention! tbh I can't exactly remember what I contributed, but I'm elated it helped

Also digging the 'Known Issues' 2nd post, hopefully helps keep down redundant reporting ;)

EDIT: After trying to use 1.7.3.8, my 0 dog WD doesn't spam summon dogs. it seems like he's waiting the full timer even though I can resummon immediately. No problem sacrificing dogs, just won't replace them and hacks away at mobs with his sword since he can't sacrifice.
Click to expand...

Most of the rune support came from AutoSkilled :)

WackJagon said:
Bats are working much better! Thank you so much. I am quite happy with this version so far!

Couple observations:

* Will sometimes use bats to clear debris, this is a waste of mana due to the initial mana cost of bats. A rule to never use bats to clear debris might do the trick.

* Short bursts of bats are observed. This is always a bad use of bats and depletes mana quick. Bats should be used when there is time to channel and in turn ramp up the damage. Quick "1 shots" should use another offense.

* When channeling bats in an RD pack, spirit walk needs to be used to offset the damage being reflected (which can easily kill a WD with high crit damage)

* Bat channeling and other skills could be better "understood" by the bot. For example: If you have corpse spiders/widowmakers and hex/jinx both configured as skills in addition to bats, it would be nice if the bot knew that WHILE CHANNELING BATS that using HEX/JINX at the same time does NOT interrupt the bat channeling but using corpse spiders does (creating the need to consume the bats initial mana cost again to start it back up).

The following skills can be used at the SAME time while channeling bats and does NOT interrupt bat channeling (this is key to huge damage):

(1) Spirit Walk
(2) Soul Harvest
(3) Hex/Jinx

Will keep observing and report :)
Thanks rrrix and all!

Edit: corrected typos :rolleyes:
Click to expand...

Thanks, noted... We'll get there .. :)
zorked said:
hmm .. I get a way higher CPU-usage with .8 ... FoM MP10 Eliteskipping with my Barbs becomes quite a Diashow (with latest non Beta DB .317)
Click to expand...

Hm... i'll run performance analysis, but, I don't recall changing anything super. What else are you running (QuestTools, SimpleFollow?)
 
rrrix said:
Hm... i'll run performance analysis, but, I don't recall changing anything super. What else are you running (QuestTools, SimpleFollow?)
Click to expand...
Well sorry, it seems I was a bit fast. I also updated R-YAR and that seems to be the issue ...
 
Apologies if this has been posted before, but how can you update Trinity without it overwriting your current configuration, or is that not possible?
 
I have another weird behaviour to discuss though ^^

When there are elites around that are to be skipped, the bot often focuses on single trashmobs that appear to be nearby even if the minimum trash mob counter is on 7 or higher. He does that until they're finished.
 
Gonna put this official .3.8 to the test really soon.
Thanks for keeping up the good work!

I was really looking forward for blacklist override but hey, what can you do ;)


By the way - is there any way to check Trinity version without starting DB?
 
Nazair said:
Gonna put this official .3.8 to the test really soon.
Thanks for keeping up the good work!

I was really looking forward for blacklist override but hey, what can you do ;)


By the way - is there any way to check Trinity version without starting DB?
Click to expand...

The version is shown in the plugin tab in DB.
 
rrrix said:
The version is shown in the plugin tab in DB.
Click to expand...
alternatively, open up plugin.cs on notepad++ (it should show the version if rrrix remembered to update it :p)

and on the topic of high cpu, I'm pretty sure the api change causes it but not sure where to start diagnosing it do let me know if you need some data
 
rrrix said:
The version is shown in the plugin tab in DB.
Click to expand...
Well, I asked how to check it without necessity to run DB...

w4rr3n said:
alternatively, open up plugin.cs on notepad++ (it should show the version if rrrix remembered to update it :p)
Click to expand...
Thanks! I was searching files for the version line but it is written with spaces and commas. Good to know where to look now ;)
 
Sorry, read that as "restarting" rather than "starting" :)
 
Hi rrrix, I have a suggestion for monk's combat routine:
When monk selects Deadly Reach - Foresight rune AND another spirit generate skill, 99% of the case is that monk only wish to maintain the foresight buff (18% raw damage increase, 30s) but not use Deadly Reach as a main damage skill. So can you do some optimization there?
 
zorked said:
I have another weird behaviour to discuss though ^^

When there are elites around that are to be skipped, the bot often focuses on single trashmobs that appear to be nearby even if the minimum trash mob counter is on 7 or higher. He does that until they're finished.
Click to expand...
me too :(
 
I had to backtrack back to .7.. .8 is taking too much resources and its slowing down diablo to chopping moves. Or maybe its the .20 ryar im not really sure. Something is terribly wrong with something. Anyone else have issues with resource hogging?
 
Status
Not open for further replies.
Back
Top