Identify data type of MsgEntry.attributes about mhrice HOT 5 CLOSED

Fixed in 3eb805c. Thanks!

from mhrice.

I have seen -1 that has corresponding data "1400" (in integer), so I believe that's just garbage data

because when I checking those file has -1 value. I saw the value inside always going to the string part(larger than data_offset) if we handle it as offset.
for example:
natives\STM\npc\Message\nid801_MR.msg.539100710, all the values are 151948, which if I found the value at that offset, it is 0x0000
natives\NSW\Message\Quest\Quest_Demo_MR.msg.539100710, all the values are 32304, which if I found the value at that offset, it is 0x0000
natives\NSW\Message\Quest\Quest_Demo.msg.539100710, all the values are 160168, which if I found the value at that offset, it is 0x0000
for that file has 82ADE89D-FEB631FA mmh, all the values are 1400, which if I found the value at that offset, it is 0x0000

so I guess -1 is some thing like disabled. and its value is an offset always pointing to the string part with the value 0x0000 which is ""

I tried to assert its value must be between the data_offset and EOF, and assert the string value must be 0x0000, its fine with all the msg files in current game version

although it is still garbage data

from mhrice.

I remember last time I saw some inconsistent data so I didn't resolve it this way. Will revisit

from mhrice.

-1 : could be a string? (a u64 offset pointing to a actual string), it seems like it is always pointing to a null string(0x0000). From the nid801_MR.msg.539100710 and Quest_Demo_MR.msg.539100710 file

from mhrice.

I have seen -1 that has corresponding data "1400" (in integer), so I believe that's just garbage data

from mhrice.