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

Trinity 1.7.3.6

Status
Not open for further replies.
Hey Guys,

can u add an "SWBeforeCycloneStrike" Button ? or tell how to do that ?
My monk did CycloneStrike and has than not enough power for SW ( no SET ) lost dmg
its lost time :( because he is using SW just .. maybe 50% of the game

Ty


Edit: MY D3 just close it self when bot is running for ... 10 min. no errors, just close D3 window. ( Trin 1.7.3.5 with DB .317 )
With DB .317 and Trin 1.7.3.4 all fine.... nothink changed in option from trin 1.7.3.4 to 1.7.3.5
 
new trintiy does work well with ur new updated yar.
posted logs in yar topic, cuz i thought it was yar's problem :D
 
Hi rrrix,

I have installed the latest Demonbuddy and Trinity 3.5 and it keeps looping within Act 3 profile by you without any actions.

I revert back to DB315 and Trinity 3.3 and is running quite well.

Attached the log and hope you can advised.

Thanks!
 

Attachments

Hi rrrix,

I have installed the latest Demonbuddy and Trinity 3.5 and it keeps looping within Act 3 profile by you without any actions.

I revert back to DB315 and Trinity 3.3 and is running quite well.

Attached the log and hope you can advised.

Thanks!

You need the QuestTools plugin. Please read the basic requirements :)
 
Working perfectly well for me since release!
Thanks a lot for this new version!
:cool:
 
I'm not quite sure if it's DB .317 or Trinity 1.7.3.5, but after installing the two, this starts happening:

[21:29:19.542 N] Diablo III Exited, Demonbuddy terminating in 20 seconds.
[21:29:19.542 D] System.AccessViolationException: Could not read bytes from 000007A8 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.MemoryManagement.InProcessMemoryReader.Read[T](Boolean isRelative, IntPtr[] addresses)
at Zeta.ZetaDia.get_CurrentWorldId()
at Zeta.ZetaDia.get_IsInGame()
at Zeta.CommonBot.BotMain.()
[21:29:19.558 D] System.AccessViolationException: Could not read bytes from 018CE394 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.MemoryManagement.InProcessMemoryReader.Read[T](Boolean isRelative, IntPtr[] addresses)
at Zeta.ZetaDia.get_CurrentWorldId()
at Zeta.ZetaDia.get_IsInGame()
at Zeta.CommonBot.BotMain.()
[21:29:24.431 D] Start/Stop Button Clicked!
[21:29:32.081 D] System.AccessViolationException: Could not read bytes from 018CE394 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.MemoryManagement.InProcessMemoryReader.Read[T](Boolean isRelative, IntPtr[] addresses)
at Zeta.ZetaDia.get_CurrentWorldId()
at Zeta.ZetaDia.get_IsInGame()
at Zeta.CommonBot.BotMain.()

Using [A2]-In_a_Rush-Dahglur_Oasis_v2.0 and from plugins only Trinity. Reverted back to .316 and 1.7.3.4. Sorry for not being super helpful, I may change that tomorrow when I have more time to investigate.
 
No real problems, just seems to crash on average more than old Trinity I was using.
 
rrrix bro

I did use the new quest tool / clean install / latest trinity / ur latest RA1

It still crashes with some injection/memory error...something like midnightraver posted. I've reverted back to .4 trinity version with DB317 and its okay now.

Nevertheless, thanks for still being active bro! Am hoping for a ACT II profile from you. need to get some ACT II keys :(
 
The ww derp fix is pretty awesome. My barbs running fluid.

There's still problems with trash rules and i'm really not sure what causes it. For some reason or another it will not leave the last 1-2 mobs of a pack alone and continue with profile. I dont know if its from loot on ground or primary target issues or what but thats the only thing left that I have left to suggest a fix for. I'm guessing if you fix it to force obey trash rules it will mess some other logic up, but maybe something will work out sometime.

Thanks for the hard work regardless broski.
 
1.7.3.6 seems really good.

The new low trash mob % and dot % options are great. For dual wielders on mp9-10 they have to be lowered to be more effective, like 10% health and 25% percent dotted health.

Haven't checked for a lot of time, but after seeing 5 or 6 elites with the fire chain affix, the experimental avoidance is working wonders.

There is a problem with WOTB activation. My settings are Ignore elites and Use Wotb when on Cooldown, but it did not use it at all for a long time on the start of the game(yet the bot engaged in combat). Changed it to Use on any Elite /Ignore elites and it worked...mostly, also saw one time it was available and it wasn't being used.

If you have time and will, would you comment on the requests I made for future versions earlier in this thread? I guess some of them could be technically difficult or not possible to implement, but they would make bot behaviour better overall , imho. The blacklist override "feature" for certain situations like townportal or low health % would be so amazing.

Thanks for the update!
 
Rrrix, you are just unbelievable :P
I will put new version to the test right away.

However, as I mentioned before - do you think it is possible for Trinity to override blacklisted mobs in the times of need?
Your new town portal tags is great but bot still dies from time to time when there are mobs from the list around ;)
 
it looks like new trinity .3.6 eliminate closing bug, still testing for dc window bug.
 
ok, 2 things. (even if you don't want to listen to my comments anymore ;) )

first: the Grotesque avoidance seems to be missing a few lines in AvoidanceManager.cs That throws some errors and creates a lot of CPU usage.

I fixed that by adding
Code:
                case AvoidanceType.Grotesque:
                    return 1;

in the GetAvoidanceRadius() and GetAvoidanceHealth() part of the file.

The second thing is that if your equip is damaged too hard, the bot logs out. But if he creates a new game then and logs back in -even if in town- he logs back out again resulting in a crate-game-leave-game loop.

Got to search the function for that one and add some kind of && inTown or something...
 
Is it possible to make so that bot after "Ground Stomp Wrenching Smash" using "Rend"?
 
perfect barb settings for the new trinity?:D
for max iph with the oasis profile...!
 
for me new version Using [A2]-In_a_Rush-Dahglur_Oasis is not good
bot dies a lot, lowers iph to like 1200, from 1450

i get back to 2.13 version

or i just dont know how to set up new settings :)
 
Got the second Problem(when 0% durability game restart loop) fixed:

I changed one if part in the TargetCheck.cs:

Code:
// We keep dying because we're spawning in AoE and next to 50 elites and we need to just leave the game
                if (DateTime.Now.Subtract(Trinity.LastDeathTime).TotalSeconds < 30 && ZetaDia.Me.Inventory.Equipped.Average(i => i.DurabilityPercent) < 0.05 [B]&& !ZetaDia.Me.IsInTown[/B])

Added the bold part of the code To ensure the bot does not perform the quit while he's in town.
 
Status
Not open for further replies.
Back
Top