[canary] Issue on treasure chest

[Chronos77]

• [x] I have searched existing issues (https://github.com/topaz-next/topaz/issues) to see if the issue has already been opened
• [x] I have checked the commit log to see if the issue has been resolved since my server was last updated
• [x] This issue occurs on canary branch (if other branch, please specify)

Additional Information (Steps to reproduce/Expected behavior) : Resolve treasure chest after kill a mob

[Xaver-DaRed]

In short, the issue is... it told you the "first digit" when it should have been the "second digit" OR it showed a 0 when it should have been a 2 (First digit cannot be 0 ever)

First case could be caused by a textID missmatch. Knowing wich zone you were in and if it happens in other zones and your client version might help.

[Chronos77]

Hi, i'm in kuftal tunnel, i will try in another zone .

[Chronos77]

Same in West Sarutabaruta

[Xaver-DaRed]

So in short, now we know that its returning a 0 instead of the actual number. And it seems like it is the correct number that is being turned to a 0

[wrenffxi]

My guess is the problem is that splitNumbers[1] is string. Probably needs change from

                        player:messageSpecial(baseMessage + casketInfo.messageOffset.FIRST_DIGIT_IS,
                            splitNumbers[1],
                            splitNumbers[1] +1,
                            splitNumbers[1] +2, 0)

to

                        player:messageSpecial(baseMessage + casketInfo.messageOffset.FIRST_DIGIT_IS,
                            splitNumbers[1] +0,
                            splitNumbers[1] +1,
                            splitNumbers[1] +2, 0)

wherever it's being passed as argument into messageSpecial will fix tomorrow if nobody beats me to it

[Chronos77]

It's works!