Don’t worry about it. Since my update to 4.15 the error dissapeared magically.
My programmer is going to rework the whole thing(I’m bad with this) anyway so it doesn’t matter anymore as well.
But thanks for digging into it again, really appreciating your support.
I am happy to hear that your issue has been resolved. I will be marking your last comment as the answer. If the issue returns and you would like further assistance please feel free to reopen this issue.
Make it a great day