You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like string decryption occurs by converting the raw string to utf 32 and adding the obfuscation to each utf32 character. There is also a mode where the raw string is directly interpreted as utf-16le (no obfuscation) if the obfuscator value is 0 or Decode_Mode is 240 (this value is not handled by PkgText.)
Changing the string decode to work like this should reduce complexity and also make languages like Japanese, Russian, French, Korean, and both forms of Chinese no longer corrupted.
The text was updated successfully, but these errors were encountered:
TLDR: See https://github.com/andrewathalye/destiny-string-tool/blob/master/src/string_tool.adb
It looks like string decryption occurs by converting the raw string to utf 32 and adding the obfuscation to each utf32 character. There is also a mode where the raw string is directly interpreted as utf-16le (no obfuscation) if the obfuscator value is 0 or Decode_Mode is 240 (this value is not handled by PkgText.)
Changing the string decode to work like this should reduce complexity and also make languages like Japanese, Russian, French, Korean, and both forms of Chinese no longer corrupted.
The text was updated successfully, but these errors were encountered: