I did add a new line of code that resets both to 0 in prevention of it but this will only be operational for the next version, so likely 0.34 :)
