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

Trinity not adhering to item list rules

Status
Not open for further replies.
I have had this issue with my multi bots setup also. I let the leader bot to drop all legendary without IDing them, but it won't drop all. It drop most of them but salvaged some occasionally. Did multiple clean install and always the same. I have had this issue for a very long time though.
 
hams said:
any news about this "bug"?
Click to expand...

I just saw the bot do it again 1 minute ago, I have puzzle ring on my item list with all the options selected and it only has to have 1 of them, just watched it get salvaged and continue on. It's pretty inconsistent with the salvaging items it should be so i'm not sure what it's related to..
 
Having the same issue with it salvaging The Twisted Sword. It just identifies it as "sword" and therefore ignores all the properties it actually has and salvages it. I watched it do it, it was Ancient, thankfully not good though. Just makes me wonder what else it salvaged that met the criteria of the item list. Any news on what is causing the issue?
 
Actually it is doing it very often. I am doing gr 80 and get little ancients compared to old times. I think it might be related only to ancients. Today I wanted to check this yet again and first ancient and bot try to scrap it. It was this time blade of prophecy. Only this item wasnt identified by bot - in logs it is just two handed sword while others has its names:

[Trinity 2.14.45] Pas [Belt_norm_base_flippy-2981916] [Belt] = ItemListCheck=TRASH
[Trinity 2.14.45] Karwasze [Bracers_norm_base_01-2981927] [Bracer] = ItemListCheck=TRASH
[Trinity 2.14.45] Rozbita Korona [Helm_norm_base_flippy-2981920] = (TRASHING: ItemList Option - Always Sell/Salvage Non-Ancients)
[Trinity 2.14.45] Buława [Mace_norm_unique_flippy_04-2981910] [Mace] = ItemListCheck=TRASH
[Trinity 2.14.45] Rozbita Korona [Helm_norm_base_flippy-2981920] = (TRASHING: ItemList Option - Always Sell/Salvage Non-Ancients)
[Trinity 2.14.45] Miecz dwuręczny [twoHandedSword_norm_unique_flippy_03-2981922] [TwoHandSword] = ItemListCheck=TRASH
[Trinity 2.14.45] Tarcza krzyżowca [p1_CruShield_norm_unique_flippy_02-2981905] [CrusaderShield] = ItemListCheck=TRASH
[Trinity 2.14.45] [UseCraftingRecipes] Finished!

It was ancient. I still have it. I stoped bot when going to blacksmith.
 
Do we have a fix for this yet?!

I've had this issue since the latest update (including fresh reinstall). My issues are identical to what others are reporting. Seems the bot is ID'ing leg items but not using their correct name and thus salvaging, completely ignoring item list rules.

Defeats the purpose of botting, surprised this isnt getting a higher priority with the dev's...
 
Kielbasa said:
Checked [Trinity 2.14.42] version and first ancient was salvaged.
Click to expand...
Hi, Kielbasa,

Not saying this is your problem, but you're several revs behind for one. Trinity is now at '.45. You should update from its thread.

cheers
chinajade
 
Last edited:
Also suffering from this. Very noticeable legendary drop amount across multiple bots
 
chinajade said:
Hi, Kielbasa,

Not saying this is your problem, but you're several revs behind for one. Trinity is now at '.45. You should update from its thread.

cheers
chinajade
Click to expand...


Chinajade,

all my prev tests were on .45. You could see it on all provided logs that were for DIFFRENT ancient items salvage scenerios but you deleted them stating they are duplicates. (and I provided them to help find issue). In one you left (4 up) we can read:

[Trinity 2.14.45] Miecz dwuręczny [twoHandedSword_norm_unique_flippy_03-2981922] [TwoHandSword] = ItemListCheck=TRASH

also on mine page I started new thread because this problem is existing in db for more then month. On main page thread I posted reference to it but you deleted this also.

Here it is https://www.thebuddyforum.com/demon.../235881-trinity-2-14-45-a-53.html#post2139852
 
Last edited:
Hi, all,

The proper way to handle this situation is to report the problem to the Trinity thread with a full log that illustrates the problem.

We're going to go ahead and close this thread. It is apparently misleading people into thinking the developer is aware of the current problem.

Instead, please report the problem WITH A FULL LOG ATTACHED to the most recent Trinity thread. At the time of this writing, the current version is:

You only need to report the problem once, unless the developer asks you to reproduce the problem again.

cheers,
chinajade
 
Status
Not open for further replies.
Back
Top