1 |
[q]I understand your point that targeting choices are nontrivial, but specifically for a heatray-wielding comm, probably choosing close-by targets would be wise, and an acceptable computational load. I haven't read the code that determines what target is ideal, but some attempts at heatray sniping makes me suspect there is not a strong preference for close-by targets.[/q]
|
1 |
[q]I understand your point that targeting choices are nontrivial, but specifically for a heatray-wielding comm, probably choosing close-by targets would be wise, and an acceptable computational load. I haven't read the code that determines what target is ideal, but some attempts at heatray sniping makes me suspect there is not a strong preference for close-by targets.[/q]
|
2 |
Target
priority
isn't
done,
especially
for
commanders.
If
Scorcher
or
commanders
could
have
weapon
priority
improvements,
then
work
on
it
and
make
a
pull
request.
I
don't
know
why
Scorcher
lacks
proximity_priority,
perhaps
there
is
an
inbuilt
weapondef
that
achieves
the
correct
behaviour,
so
only
Stardust
needed
it
to
be
luaed.
Check
whether
Scorcher
works
well.
|
2 |
Target
priority
isn't
a
complete
project,
especially
for
commanders.
If
Scorcher
or
commanders
could
have
weapon
priority
improvements,
then
work
on
it
and
make
a
pull
request.
I
don't
know
why
Scorcher
lacks
proximity_priority,
perhaps
there
is
an
inbuilt
weapondef
that
achieves
the
correct
behaviour,
so
only
Stardust
needed
it
to
be
luaed.
Check
whether
Scorcher
works
well.
|