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

Trinity 1.7.2.11

Status
Not open for further replies.
Allow me to continue wearing my tinfoil hat and say I would hate to be banned for posting a log which could include data that may link back to my account. I noticed in the log that it logs the names of everything stashed/salvaged and in what order it was stashed/salvaged and I don't know what kind of data Blizzard retains about gameplay. I believe I've been pretty verbose in my feedback and if it is indeed a problem with the plugin and the beta version of DB, the problem should be easily replicated.

Great contribution to the thread. Keep up the good work.

The problem is not easily replicated, or it would have already been fixed. I actually can't help you without logs regardless of how 'verbose' you think you are, and there is no personally identifiable information within those logs. If you're seriously that worried about getting banned, you probably shouldn't be botting.

Without seeing if there are specific exceptions, errors, or conditions that usually only a developer will know the root cause and can gauge the level of importance, how can I diagnose your specific problem? No one else has reported a stuck at the stash. How do I verify all the specific conditions for your situation, without having any hard data? There really is a reason I need logs. Although I am flattered at your assumption of my technical abilities to know exactly what *your* bot and character is doing.
 
Allow me to continue wearing my tinfoil hat and say I would hate to be banned for posting a log which could include data that may link back to my account. I noticed in the log that it logs the names of everything stashed/salvaged and in what order it was stashed/salvaged and I don't know what kind of data Blizzard retains about gameplay. I believe I've been pretty verbose in my feedback and if it is indeed a problem with the plugin and the beta version of DB, the problem should be easily replicated.

Great contribution to the thread. Keep up the good work.

First off, I'm running the DB Beta version and v.11 and my bot never gets stuck at the vendor.

Two different stories, same plugin and DB version.

See why you need to post a log? No one can diagnose anything when there isn't any info..

Secondly, why do you have QuestTools enabled if you're doing Skyhigh and Tinn? QuestTools is for going through the acts, not repeat profiles.
 
First off, I'm running the DB Beta version and v.11 and my bot never gets stuck at the vendor.

Two different stories, same plugin and DB version.

See why you need to post a log? No one can diagnose anything when there isn't any info..

Secondly, why do you have QuestTools enabled if you're doing Skyhigh and Tinn? QuestTools is for going through the acts, not repeat profiles.
That information was actually contributing to the thread. Thanks for that. You're running DB Beta and v.11 Trinity. Is yours a fresh install? Mine was.
Not that it's any of your concern but I've pm'd a log to rrrix.
Why are you questioning my use of plugins? AFAIK Questools is harmless to have enabled if it isn't referenced or used by the profile you're running...
DB just offered to update beta to .188 and it isn't hanging at the vendor anymore. I'll test a fresh install of .188 and see what happens.

I understand the need to post logs. I don't understand the need to be a prick to anyone posting a bug without a log.
 
That information was actually contributing to the thread. Thanks for that. You're running DB Beta and v.11 Trinity. Is yours a fresh install? Mine was.
Not that it's any of your concern but I've pm'd a log to rrrix.
Why are you questioning my use of plugins? AFAIK Questools is harmless to have enabled if it isn't referenced or used by the profile you're running...
DB just offered to update beta to .188 and it isn't hanging at the vendor anymore. I'll test a fresh install of .188 and see what happens.

I understand the need to post logs. I don't understand the need to be a prick to anyone posting a bug without a log.

You're cute when you're pissy..

Glad you sent him a log, hopefully he fixes your shiz.

I'm running Beta v185 (never had any vendor issues or crashes so I didn't feel the need to update it) and a fresh version of Trinity v.11 as of last night (was using v.8 until rrrix addressed my need to beat monster ass with Frenzy/Maniac).

And I wasn't being a prick to anyone, just stating what the developer of the plugin you're using has asked multiple times for.

As for QuestTools, why have it enabled if you don't need it? That's just more info for DB to deal with while it's running (sometimes having more plugins enabled than you need can lead to crashes/freezes).

I'm on here helping people everyday, no need to get feisty.

<3 JoshYo
 
Last edited:
I can confirm that the problem was with DBBeta .187 because a fresh install of DBBeta .188 and trinity 1.7.2.11 alleviates the problem.
Your bot never got stuck at the vendor because you weren't using .187, you were using .185.
 
I can confirm that the problem was with DBBeta .187 because a fresh install of DBBeta .188 and trinity 1.7.2.11 alleviates the problem.
Your bot never got stuck at the vendor because you weren't using .187, you were using .185.

Glad to see you're running smoothly.

As for the Beta, don't automatically assume a new version is a good version. If you have a version that's running well, stick with it until you read some posts about any issues going on. I haven't had a stuck or crash since January.

Good luck.
 
@ rrrix, ok! an update on those looting issues should you try to replicate them -

There is something weird happening, an average 20 pack in keeps 2, you kill it, it drops an item - the bot then runs on around 30-40 yards, kills a few more monsters, and retreats back to the item to pick it up.

Another issue is shrines, it doesn't seem to be clicking on them although it is attempting to do so by walking up to them and idling for 0.5 seconds.

With ignore elites on, the barb often gets stuck at doorways/random places when trying to retrieve loot - Is it possible to add "WW to loot pickup if fury high enough" or something like that?

I hope you can try to replicate these and see if you can come up with any fixes.
 
ok i will provide logs when i can do it

but why you cant just BELIEVE in that w/o logs :(
 
ok i will provide logs when i can do it

but why you cant just BELIEVE in that w/o logs :(
the logs provide important information that help diagnose a problem such as plugin problems that aren't visible on the surface
 
the logs provide important information that help diagnose a problem such as plugin problems that aren't visible on the surface

I've also built into Trinity (on the ADVANCED tab) very customizable logging capabilities. When in doubt, turn them all on, and reproduce the issue. Even your particularly zombie bears behavior will be logged (including the direction of the current target, the spell usage, your location, monster location, etc, etc.)

I actually spend more time asking for logs to evaluate issues in hopes of maybe potentially reproducing the exact condition that the issue appeared than I do fixing bugs.
 
rrix i use your barbarian.cs you posted before but my barb use WOTB always if he was enough fury
even against trashmobs

how i can fix this?
 
I've also built into Trinity (on the ADVANCED tab) very customizable logging capabilities. When in doubt, turn them all on, and reproduce the issue. Even your particularly zombie bears behavior will be logged (including the direction of the current target, the spell usage, your location, monster location, etc, etc.)

I actually spend more time asking for logs to evaluate issues in hopes of maybe potentially reproducing the exact condition that the issue appeared than I do fixing bugs.
never thought of that, i totally forgot that page even existed, things have been going so well, other than a few small nuisances. ill try to get the log sometime soon for the bears problem
 
rrix i use your barbarian.cs you posted before but my barb use WOTB always if he was enough fury
even against trashmobs

how i can fix this?
Yeah...same problem. Bot uses WOTB on every trash mob..or use WOTB on every HARD elite if the option is clicked. I would like to know how to make bot do old style..that's use WOTB when elite(no matter normal or hard) is met ?
Besides that my DH and barb bot are doing perfectly fine. Nothing looks broken. Keep testing if any crashes will occur and keep you informed. Thanks rrrix for your work..as always we all own you a lot.
 
rrix i use your barbarian.cs you posted before but my barb use WOTB always if he was enough fury
even against trashmobs

how i can fix this?

I believe WotB has been added to the out of combat movement spells (due to increase in movement speed). Try unclicking that and see if it still happens.

Personally, I noticed this too but it's just going to make the bot go through the profiles faster (which is better).
 
What does the checkbox " Debug item rules" from Item Rules submenu does?
 
Something is wrong in RunStats. From 1.7.2.8 to 1.7.2.11 the number of dropped items is lower than the picked up ones (ilvl 60, 62 and 63).

Items dropped by quality:
- Rare: 626 [131,68 per hour] {29,14 %}
--- ilvl 58 Rare: 41 [8,62 per hour] {1,91 %}
--- ilvl 59 Rare: 16 [3,37 per hour] {0,74 %}
--- ilvl 60 Rare: 98 [20,61 per hour] {4,56 %}
--- ilvl 61 Rare: 216 [45,43 per hour] {10,06 %}
--- ilvl 62 Rare: 171 [35,97 per hour] {7,96 %}
--- ilvl 63 Rare: 84 [17,67 per hour] {3,91 %}

Total items picked up: 581 [122,21 per hour]
Item picked up by ilvl:
- ilvl58: 3 [0,63 per hour] {0,52 %}
- ilvl60: 104 [21,88 per hour] {17,9 %}
- ilvl61: 155 [32,6 per hour] {26,68 %}
- ilvl62: 209 [43,96 per hour] {35,97 %}
- ilvl63: 110 [23,14 per hour] {18,93 %}


The number of picked up items per hour seems correct so i guess the error should be in the dropped items section.

Btw: tnx for your work on trinity.
 
For some reason when i updated my trinity to .11 my runstats log doesn't update. But all other log does. When I delete runstats log, DB wouldn't create new one to replace it. Anyone else has the same issue?
 
GPH lowered with this version. I got -100k collected by eatch bot now. 10h playtime..still no crashes.
 
hi rrrix, could you please clarify this a bit:

Added Monk Breath of Heaven:Infused With Light + Way of the Hundred Fists:Fists of Fury support

Increased Monk Wave of Light priority

as in the .10 version my WoL is spammed as much as it can when theres enough spirit, which is especially good with the 5 sec Infused with light duration, but the new version it kinda waits and uses it way less frequently during that 5 sec window which makes the whole build much more useless, like it's saving up for something - was this intended? I've tested a few times and it seems like the passive beacon of Ytar isn't recognised by the bot either, is it possible to make the bot used BoH:IwL as soon as it timer is reset? It seems like it still waits for the normal cooldown timer before it is used, same with ascesion.

also when i tried a TR build to ignore elites, it doesnt run very well as it ignores elites but then if it runs out of spirit it will just get stuck with the elite if they're say blocking a doorway and it wont attack them for more spirit and run away. it will therefore just get stuck and get smashed til it dies - any hints for this?

anyhow - appreciate your work always :) thank you for your time!
 
Last edited:
Status
Not open for further replies.
Back
Top