Jump commands - can only be used in missions

[hamishwillee]

1. This specifies the minimum repeat count on a jump tag as 1, rather than 0. If a number < 1 is set the mission item is invalid and should be ignored (skipped). Note "ignored" - this is not a basis for rejecting the mission - should it be?
2. I also set the min value for the sequence to 1 - ie the first item in the mission. What this means is that you can't set this to 0 or the "home" position.
   • I think this makes sense.
   • We could also specify what happens if <1 was entered - should we. I would suggest that perhaps the system ignore this and just use 1
3. I have stated these are not intended for use as commands. The semantics are otherwise a bit confusing - i.e. if I send this as a command, am I trying to reset the mission internal counters? etc.

[hamishwillee]

@julianoes @auturgy As discussed in dev call. Made it a draft as there are "questions to be asked".

[hamishwillee]

Note, reverted the change to minimum values.

The only actual content change is the last line:

This is intended for missions, and must not be used as a command outside of missions.

Originally I was concerned about the minimum values too. But thats unnecessarily proscriptive. Where not using this outside of missions should just be common sense.