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

trinity item rules : strange behavior (all looted leg items salvaged)

T

thw

New Member
Joined
Jan 2, 2015
Messages
19
Reaction score
0
Hello

I am using rift-bot with diablo-3 2.1.2
DB env is as follows:
DB : beta v1.1.2224.507
Trinity : v2.3.0
QuestTools : v3.1.13
Diablo client : "Korean: version (non-english!)
Item Rules Mode : "File Based Script Rules"
Item Rules: "Custom RTFM"


My problem is as shown below:

....
[Trinity] Translation: Missing: -1187471161;요르단의 반지 (ID is missing report)
[Trinity] 요르단의 반지 [Ring_flippy-3093] [Ring] = (TRASH)
[Trinity][ItemValuation] Incoming Salvage Request: Legendary, 70, Jewelry, Ring, NH
[Trinity] Translation: Missing: -1187471161;요르단의 반지 (ID is missing report)
...


The ring name in English is "Stone of Jordan".
And trinity's translation defined as "-531919949;Stone of Jordan"
But DB's log said its ID is -118747116 (I guessed from the log above)


At first, I set trinity not to use "Item ID", and I found all leg items salvaged.
To avoid such a problem, I made trinity to use "Item ID's instead of names".
But the result is same. (all legs salvaged)

Plz help me to handle the situation.
Is trinity's translation problem?
means I have to add some more translation rules to 'translation.dis'?

Or it's a kind of non-english XML encoding problem?

I will highly appreciate if someone guide me to a right direction.

-----
weon
 
This could be a translation issue, I really don't know. But there is a slight chance you are having a related issue to the bot having issues vendoring stuff like horadric caches, rift fragments, crafting materials. This doesn't always happen, I have yet to see anyone else post about their bot salvaging all legs with the right settings. Did you try using trinity scoring over itemrules? if it works with trinity scoring unid or ID'd fine, but has issues with itemrules(so you can filter out the junk items and non ancients) then it could be a translation issue or something else. I know they changed the names/IDs of a few certain things like keys but I don't know about soj
 
Thanks for your reply.
I tried most of rule modes;trinity scoring and item ranking.
When using trinity scoring, no leg item was salvaged.
But, in case of item ranking all legs were salvaged...
my dummy bot salvaged several Kridershots already.
I'm looking at logs in debug-mode..now.


Syn-Ack said:
This could be a translation issue, I really don't know. But there is a slight chance you are having a related issue to the bot having issues vendoring stuff like horadric caches, rift fragments, crafting materials. This doesn't always happen, I have yet to see anyone else post about their bot salvaging all legs with the right settings. Did you try using trinity scoring over itemrules? if it works with trinity scoring unid or ID'd fine, but has issues with itemrules(so you can filter out the junk items and non ancients) then it could be a translation issue or something else. I know they changed the names/IDs of a few certain things like keys but I don't know about soj
Click to expand...
 
Using non-english clients with ItemRules is unreliable, at best. The [ITEMID] the original ItemRules uses is actually incorrect (it uses a field called "GameBalanceID", which can change).

The most reliable way is to use ActorSNO's. I've collected all of these on DiaCollector (with the communities help).

You can use the [SNO] attribute. E.g.:

Code: 
[SNO] == "212582" // Stone of Jordan

You can drive more data into DiaCollector too: https://www.thebuddyforum.com/demon...-diacollector-community-driven-item-data.html
 
Last edited:
Hi

As you wrote, I found most of [ITEMID] translation included in trinity is incorrect in non-english(at least in Korea) dia client.
I was making a new translation.dis fromIR2Tran log files.

I will try with your suggestion.
Thanks a lot!



rrrix said:
Using non-english clients with ItemRules is unreliable, at best. The [ITEMID] the original ItemRules uses is actually incorrect (it uses a field called "GameBalanceID", which can change).

The most reliable way is to use ActorSNO's. I've collected all of these on DiaCollector (with the communities help).

You can use the [SNO] attribute. E.g.:

Code: 
[SNO] == "212582" // Stone of Jordan

You can drive more data into DiaCollector too: https://www.thebuddyforum.com/demon...-diacollector-community-driven-item-data.html
Click to expand...
 
Hello

I found the reason why my item-rules did not work well.
All C# script stuffs like interpreter.cs assumes unicode file input.
Currently .../Plugins/Trinity/ItemRules/translation.dis is just an ascill file.

I worked the followings.
(1) in trinity configuration, I unchecked "Use Item ID's instead of names"
(2) I changed my item-rules to use korean item names and saved as unicoded file.
(3) I rewrote translation.dis with ItemTran which located under .../TrinityLogs/<battle tag>, and saved in unicoded format.
When using non-english diablo 3 client, this work is always required.

My editing tools for (2) and (3) is just notepad on Windows.

After the work, no remarkable strange things found.
 
Tawan Won said:
Hello

I found the reason why my item-rules did not work well.
All C# script stuffs like interpreter.cs assumes unicode file input.
Currently .../Plugins/Trinity/ItemRules/translation.dis is just an ascill file.

I worked the followings.
(1) in trinity configuration, I unchecked "Use Item ID's instead of names"
(2) I changed my item-rules to use korean item names and saved as unicoded file.
(3) I rewrote translation.dis with ItemTran which located under .../TrinityLogs/<battle tag>, and saved in unicoded format.
When using non-english diablo 3 client, this work is always required.

My editing tools for (2) and (3) is just notepad on Windows.

After the work, no remarkable strange things found.
Click to expand...

It is the best useful information to multi-language (2Byte) user

한국 사람같이 2바이트 문자 쓰는 사람들에겐 매우 유용한 정보네요.ㅋ
 
you can share translation.dis with me :-)
The translation.dis mapping included in trinity is not compatible with non-english diablo clients.
 
Korean version translation.dis/legendary.dis

Attached are "Korean" translation.dis and my legendary rule.
My legendary rule is very simple.
Plz keep in mind the two files contain Korean chars.
 

Attachments

You must log in or register to reply here.
Back
Top