Extraneous Numbers in text After Latest Compile

[Riklin]

I updated my source and recompiled a couple days ago. Ever since then when talking to quest mobs, or as a GM, searching for spells or items during quest construction, a bunch of numbers are being inserted with each item or enclosed text.

For instance here is an excerpt of what happens when you hail Magus Alaria in the Guild Lobby.

Magus Alaria says 'Greetings, Woody. As you may have guessed I have been sent here by the Wayfarers Brotherhood to assist those that dare subkect themselves to our magic. I promise you I have trained long and hard to be up to the task. I only rarely make the type of mistakes you may have heard about regarding these spells of travel. Come, let me know where you would like to go and I'll send you on your way. I can send you to any of the Wayfarer camps in
[07A12D00000000000000000000000000000000000000000000 000000000Butcherblock],
[07A12E00000000000000000000000000000000000000000000 000000000Commonlands],
[07A12F00000000000000000000000000000000000000000000 000000000Everfrost],
[07A13200000000000000000000000000000000000000000000 000000000North Ro],
[07A13100000000000000000000000000000000000000000000 000000000South Ro],
[07A13000000000000000000000000000000000000000000000 000000000Nedaria's Landing],


Any ideas how to fix this?

Rick (HallsHavoc)

[joligario]

Update again. You will see text-link fixes.

[Uleat]

If you happen upon any more issues like this, please post what client observed it and what activity was being performed - thanks!

[Riklin]

That fixed it btw...
Will do regarding providing better information. I suspected I wasn't providing enough information. Will do better next time...



For the record, it did it with Underfoot and SoD clients.

Server is a windows server, compiled in 64bit optimized for 8 cores.

Database is up to version 9066.

[Uleat]

Thanks for that


I ask because I moved text link translation from the server core to the client translators.

This way, we get translation on both out-going and incoming - which was missing before (i.e. someone linked an item from their client and it was
rebroadcast to other clients. In it, there would be missing letters from the name or it would have leading zeros.)


In this particular case, I mis-interpreted a field octet and it caused an overwrite to occur in the string sequence - which is where the 'space'
came from - and it threw off the client's ability to decode the values.