@War0tter It was investigated a while back, but couldn't get it to trigger internally, and "just play the game" wasn't helpful when it came to debugging this. After that it went on the backburner and we'll need to revisit when our next couple of large updates are out of the way.
@War0tter Right, and repro steps were in the task, but it wasn't happening on an internal environment. That usually means that server conditions factor into how the bug actually manifests. Like I said though, we can circle back around to it later this year.
devtrackers.gg