"Score = 0 {legendary item}" in Junk log

[LeoChien]

While checking the Junk log, I found something made me puzzled.

Like this:
And actually, these items has been identified.

Offhand - Shield '盾'. Score = 0 {legendary item}
  (no scorable attributes)

Armor - Bracer '护腕'. Score = 0 {legendary item}
  (no scorable attributes)

When occurred, Ancient Item in List which should be kept in stash, will also be salvaged.

 

[dbfriend]

seems you have the Second Stash and have many items on it ,right?

if so, you have the same issue as me.

https://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/228399-d3-china-region.html

 

[xzjv]

I have tested the china client with the second stash etc, and aside from some cube upgrade issues that are also present in non-Chinese client. everything worked fine for me. Could you please try:

* Do a clean install with latest DB.

* Use ItemList as your rules system - see this thread for how to do that. https://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/212365-item-list-stashing-system.html

* Make sure you are on the latest version https://www.thebuddyforum.com/demon...8110-trinity-2-13-47-questtools-3-5-10-a.html and delete old version that comes with DB completely before extracting the new version.

if you still have issues, make sure you have verbose logging on in DB settings. Enable 'Behavior', Movement, Targetting in logging options under trinity settings > advanced. then post the log and then i'll be able to help you further.

 

[dbfriend]

Hi xzjv,

-----------------------------------
Demonbuddy.v1.1.2725.435
Adventurer-1.3.2.144
Trinity-2.13.47
-----------------------------------

* Do a clean install with latest DB - done
* Use ItemList as your rules system - done
* Make sure you are on the latest version - done

and i put almost full items on the second stash.



1 example:
'Blackthrone's Duncraig Cross' - Critical Hit Chance is 8.5 then it should be stashed as per Trinity Item list setting.

'JunkLog.log' info as below:

Jewelry - Amulet '护符'. Score = 0 {legendary item}
  (no scorable attributes)

But DB just salvage this Amulet.....

2 example:
Legendary Potions already set to stash, but DB still keep it in character's bag.

3 example:
DB sometimes won't identify legendaries and just stash them or salvage them randomly.
(will provide you log file if it happen, just testing now)




and of course DB won't have above issues if the second stash is empty.

attached file for your reference.

trust you can help to solve this problem and thanks in advance.


View attachment DB_issue.zip

 

[dbfriend]

another new example:

Ancient CeremonialKnife should be stashed i/o salvage.

View attachment DB_issue - 2.zip

 

[dbfriend]

Item Rules Mode - > File Based Script Rules example

if use this custom rule, DB won't identify legendary and just stash or salvage it.

View attachment DB_issue - 3.zip

 

[dbfriend]

just find out that it will also ignore gems randomly...

View attachment Gem.zip

 

[dbfriend]

last, here is my Second Stash contents for your reference:

PS: again, if the second Stash is empty or have less items, db wont have above problems.

 

[xzjv]

Thank you for such detailed information, i'll look through it.

 

[Doordie]

I have the same issue ……hope it will be fixed in the next version

 

[alainbuddy]

Do more mats drop on asian servers? That's an impressive amount of souls.

 

[dbfriend]

Do more mats drop on asian servers? That's an impressive amount of souls.

actually no lol...

 

[dbfriend]

tried 'DBv1.1.2756.573' and 'Trinity 2.13.61' today.

and cfm that the 'Second Stash' problem still exsit.

----

i put so many items on the second stash and DB works like a charm this morning.

but just find out that the bot doesnt identify legendary and go to salvage it....... -_-#

 

[iamtida]

Thank you for such detailed information, i'll look through it.

Actually, this happens as soon as the item loot. Once an item is looted, the fact whether it can be recognized by Trinity is decided by some fact.
I noticed once the GRift boss loot 5 legendaries, which all not recognized by Trinity, the stat on db panel remained 0 for leg/hour. After bot returned to town, it salvaged all loot legendaries as it was normal items. Therefore, I think you can see where the bug is.

Hope it fixed asap and thanks.

Updated: I updated trinity over assembla, the version 2.13.63, and the bug continues with new situation, that when former TR (2.13.62 or earlier) does not recognized a legendary, the legendary name does not appears in the log, but the newer TR(2.13.63) shows the name, with all attribute gone for nothing. It seems something is being fixed and I'm glad Hope everything goes smooth as the stable version releases.

 

[dbfriend]

Actually, this happens as soon as the item loot. Once an item is looted, the fact whether it can be recognized by Trinity is decided by some fact.
I noticed once the GRift boss loot 5 legendaries, which all not recognized by Trinity, the stat on db panel remained 0 for leg/hour. After bot returned to town, it salvaged all loot legendaries as it was normal items. Therefore, I think you can see where the bug is.

Hope it fixed asap and thanks.

Updated: I updated trinity over assembla, the version 2.13.63, and the bug continues with new situation, that when former TR (2.13.62 or earlier) does not recognized a legendary, the legendary name does not appears in the log, but the newer TR(2.13.63) shows the name, with all attribute gone for nothing. It seems something is being fixed and I'm glad Hope everything goes smooth as the stable version releases.

this bug exist so long.....and seems no one can fix it so far.

svn has v2.13.72 now. i will test it today.

 

[dbfriend]

tried Trinity v2.13.72 and cfm still has the same problem....

 

[Peg_EGG]

last, here is my Second Stash contents for your reference:

View attachment 190241

View attachment 190242

PS: again, if the second Stash is empty or have less items, db wont have above problems.

How long have you been using the bot to have massive material stash like this

 

[iamtida]

tried Trinity v2.13.72 and cfm still has the same problem....

I'm looking in to the source code and I think there is something wrong with data type InventorySlot, and in the file Trinity\Coroutines\Resources\Inventory.cs, line 410. Well I can't tell where and what the bug really is, just searched for keyword "InventorySlot", because this only happens in China server where the only difference lies in InventorySlot numbers.

From line 410, the trinity begins to recognize the item attribute. And from the log file we can see item type is clearly recognized as legendary, as following

201511061820151665.Hero;LOG;PICKUP;[KEY]:1255145609;[BASETYPE]:Armor;[TYPE]:Shoulder;[QUALITY]:Legendary;[D3QUALITY]:Legendary;[NAME]:护肩;[LEVEL]:70;[ONEHAND]:False;[TWOHAND]:False;[UNIDENT]:True;[INTNAME]:shoulderPads_norm_base_flippy;[ITEMID]:-1920650315;[QUALITY]=="Legendary"

 

[dbfriend]

@xzjv

any ETA to fix that problem?

thanks

 

[Doordie]

@xzjv

any ETA to fix that problem? +1

thanks