This issue still hasn't been fixed in TU 1.5.6.
A while back, EA_Darko told me that he had reported this issue to the development team. Can't you fix this bug?
If it can't be fixed, you should remove this feature.
If the bug will continue to carry over to new products indefinitely, we're better off without a broken feature.
He got in touch with me two months ago.
Two months have passed, and the issue still hasn't been resolved.
This must mean that they don't intend to fix this bug.
They wasted all the time and effort I spent providing them with the bug verification records.