- In older versions of the tools every ItemSetType line with
item_idxabove 255 was calculated wrong: 256 became 0, 257 became 1, 258 became 2. - Update MuClientTools16 to the version with the author's fix (commit 933d218 from 2021-10-22).
- Decode ItemSetType.bmd again and check the indexes before you encode it.
MuClientTools16: in ItemSetType.bmd every item index above 255 comes out as 0, 1, 2 and so on
Herramienta: MuClientTools16
La persona que abrió el issue confirmó que esto lo solucionó.
En el issue, 2021-10-22 (texto original)Palabras originales (Inglés)
“Fixed. Thanks for testing.”