Attack direction convention

[raymondben]

End coord of an attack can either be the intended attack direction, or the actual end location (if e.g. deflected off the block). Need to consider which/how we accommodate.
There is already an option for attack_end, which by default is "actual" but can be set to "intended". The only difference this currently makes is that if it's "intended", then an attack scouted with a block touch will have its end coordinate recorded, but that coordinate is not assigned to the subsequent dig action if there is one (but it would be assigned if attack_end was "actual", because the dig was actually made from that point).

[ick003]

I though about that a bit. Entering the coordinate as proxy for the cone direction s misleading tbh. Could we have a end coordinate reflecting the actual end coordinate, and a cone which is not calculated based on end coord? So in the attack popup (or more likely in the dig one) we could have another set of boxes, 'Cone 1', etc to reflect the intended direction...