fix for bad blaster behaviour

thought this was a bug in pathfinding or the waypoint allocation, turns out
it was a just a bug in blaster launchers in general :D