Fixed the issue! That was a movement bug introduced in the most recent build due to a previous bugfix. Thanks a ton for the help tracking it down
