Thanks for the feedback!
As for that specific bug, the check is actually implemented. The problem is caused by it not resetting when it should, but we sadly didn't have the time to fix it before the deadline.