I'd prefer if we could pull this out into AttackBaseInfo too, and then add a seperate `attackoutsiderange` cursor type. We weren't aware of this feature when setting up the original cursor definitions, and so decided to assign this "unused" sequence to attackmove.