[TS5 Bug] Imported identities with special escaped unicodes, remain escaped when imported

Steps to reproduce:

  1. On TS3 create an identity that has a in their nickname.
  2. Export the identity with the custom unicode
  3. Observe the .ini file and see how turned into \x263a.
    Note: If you would be importing that exported identity file in TS3, \x263a turns into
  4. Now import the identity into TS5.
  5. Note how it didn’t turn \x263a into a unicode.

Thank i can reproduce this and send it to our developers.



Nooow, are there “Solved” flairs or something in this forum? I saw that this framework does.

This is not solved as long the bug exists :wink: