naomimyselfandi
naomimyselfandi
> This could also make sense as a FRED feature, though that wouldn't account for motion I'd be into it solely for my inability to estimate the space between fighters...
> If you only want to fix `hv.Key`, it's probably possible to implement that in a reasonable time That would actually be totally sufficient! The issue, basically, is that "The...
You've heard correctly! Your proposal is nicer than mine, though, so I'm incorporating elements of it. :)
It's something I've been on the fence about. If there's a need for it, I can certainly implement it.
Yup! Supporting that use case has always been part of the plan.
I'd love to have this for main drives as well - BTA has a script to shut off a ship's thrusters when it's not moving that would greatly benefit from...
The abrupt cutoff also just looks kind of weird.
> As long as `kwargs` itself is optional (and doesn't raise any errors by not being present), I'd think existing SEXPs could be retrofitted without issue. On reflection, my framing...
I don't agree that `[sg]et-variable-by-index` are "perfectly usable". They require the FREDer to be aware of variable indexes, which, to my knowledge, aren't shown anywhere in FRED; they require the...
What other reasons is it required for?