over 3 years
ago -
Ignasis
-
Direct link
Hey @arktara
We are aware of this issue and the many frustrations it brought. A fix for it is being finished internally as we speak and we’re expecting it to be included in the next content update (2.4) as long as no further issues are detected.
Thanks for reaching out to us and apologies for the frustration this problem has caused.