I think I tracked down the issue and fixed it! It's not a major enough change to push a full update, so it'll (hopefully) work properly in the next big update
