New guard-range sexp

[TheForce172]

New guard-range sexp which allows different ranges for different guarders. As requested by Iain baker.

[MjnMixael]

Can this not be done as an expansion of the old sexp instead of adding yet another -new sexp? I know there's convention for that but it's not really a user friendly convention.

[TheForce172]

Not without changeing the old sexp's behaviour which were not allowed to do as it's been in a stable release.

[Sessile-Nomad]

I suspect I'm the only dev who has used the 'old' set-guard-range Sexp since 26 is so new and I have no issue with adding this to the existing Sexp 🙂

[Sessile-Nomad]

I did a poll to ask if anyone had used the set-guard-range Sexp and it looks like no one has except myself, and most people didn't even know it was 'a thing', so I think we can safely add to it without upsetting anyone.

[Goober5000]

Got a review for this which I'll send over Discord.

[TheForce172]

Ok, Is clang having a nervous breakdown today or something? This one makes no sense either?

[MjnMixael]

Ok, Is clang having a nervous breakdown today or something? This one makes no sense either?

The codebase in general prefers nullptr over NULL always. Just replace it and it should pass.

EDIT: Oh I see.. it's saying there's a NULL on that line when there's clearly not. Uh. That's neat.