[TERA PC & Console] En Masse is closing, but TERA lives on! We will continue to support TERA PC (NA) and TERA Console until service is transferred. Stay tuned for more information.
[TERA Console] The Grotto of Lost Souls update (v85) is now live! Read the patch notes here: https://bit.ly/TERACon_v85
[TERA PC] The 64-bit update (v97) is now live. Check out all the changes delivered on August 11 here: https://bit.ly/tera64_patchnotes
[TERA PC & CONSOLE] Summerfest Part 2: The Beach Bash is on from August 11 until September 1! Participate in event activities to earn tokens redeemable for costumes, consumables, mounts, and more! Details: https://bit.ly/tera_sf20
Items in bank say they're soulbound to someone else?
Some items in my bank say they're soulbound to someone else, for example: 
It doesn't affect how I use the item or anything and the status of it being soul bound disappears after I take it out of my bank but It always seems to reappear eventually though which is strange. I added the person who it says its soul bound to and its a level 18 Sorc called Suffocating and my name isn't suffocating and never was so iunno I thought this was strange as its been this way for multiple different patches.
Maybe my bank is just haunted
It doesn't affect how I use the item or anything and the status of it being soul bound disappears after I take it out of my bank but It always seems to reappear eventually though which is strange. I added the person who it says its soul bound to and its a level 18 Sorc called Suffocating and my name isn't suffocating and never was so iunno I thought this was strange as its been this way for multiple different patches.
Maybe my bank is just haunted
0
Comments
I guess it's theoretically possible that there could be some sort of ID conflict behind the scenes and these items are linked to that person's ID for whatever reason.
This is on Celestial Hills so no merges and I haven't server transferred this character or any other since the beginning of last year so it can't be that either. I've asked around and no one else seems to have this strange bug, probably is some type of ID conflict like you had said.