Its worth noting that vectorLen(getWords(%player.getVelocity(), 0, 1)) is more efficient not only in physical space, but also to be executed, as vectorLen is an engine level function, which lets it run a lot faster than doing the math yourself in torquescript. While there's no noticable difference normally, if you start running this script thousands of times a second, then it will start to add up.