Hi, unfortunately this bug reappeared again in v3.1.22.

Thanks for the continued support though, I appreciate it a lot!

Thanks for your reply!