| 1 |
Ultimately,
what
I
would
LOVE
to
see
and
make
use
of,
is
a
personal
config
file
/
UI
that
I
can
set
1
time,
and
tweak
whenever
I
like,
to
control
which
units
fire
at
what
targets.
Or
a
file
that
lets
me
define
Fire-States.
For
example:
|
1 |
Ultimately,
what
I
would
LOVE
to
see
and
make
use
of,
is
a
personal
config
file
/
UI
that
I
can
set
behaviour
over-rides
within
1
time,
and
tweak
whenever
I
like,
to
control
which
units
fire
at
what
targets.
At
first,
the
file
is
empty,
but
you
could
add
a
single
unit
at
first.
|
|
|
2 |
\n
|
|
|
3 |
Let's add lance.
|
| 2 |
\n
|
4 |
\n
|
| 3 |
For
lances,
or
firestate
1:
Fire
at
any
target
that
has
a
metal
value
of
>400
and
is
not
a
radar
dot.
|
5 |
Firestate
1:
Fire
at
any
target
that
has
a
metal
value
of
>400
and
is
not
a
radar
dot,
prioritize
Commander.
|
| 4 |
Maybe
fire
state
2:
Fire
at
any
target
that
has
a
metal
value
of
>200
and
is
not
a
radar
dot.
|
6 |
Firestate
2:
Fire
at
any
target
that
has
a
metal
value
of
>200
and
is
not
a
radar
dot,
prioritize
Commander,
ignore
Halberd/Razor.
|
|
|
7 |
Firestate 3: Hold fire.
|
| 5 |
\n
|
8 |
\n
|
| 6 |
Custom
ignores
like
Halberd,
solars,
nanoframes,
gauss,
razor
would
be
great
to
have.
|
9 |
Custom
ignores
like
Halberd,
solars,
nanoframes,
gauss,
razor
would
be
great
to
have.
People
are
already
tired
of
Felon
blowing
it's
load
on
a
razor
or
halberd.
|
| 7 |
\n
|
10 |
\n
|
| 8 |
Target
prioritization:
Prioritize
by
class
/
cost
/
unitname.
|
11 |
Target
prioritization:
Prioritize
by
class
/
cost
/
unitname.
I
want
my
dominatrix
to
stay
on
that
outlaw,
not
the
1/3HP
rogue
that
I
never
asked
it
to
capture.
|
| 9 |
\n
|
12 |
\n
|
| 10 |
Over-rides
by
direct
fire
command
enabled
too.
|
13 |
Over-rides
by
direct
fire
command
optional.
|
| 11 |
\n
|
14 |
\n
|
| 12 |
That
way,
all
the
heavy
lifting
is
done
before
the
game,
to
the
user's
specification,
without
the
use
of
some
confusing/expensive
widget,
and
can
be
adjusted
as
they
see
fit.
|
15 |
That
way,
all
the
heavy
lifting
is
done
before
the
game,
to
the
user's
specification,
without
the
use
of
some
confusing/expensive
widget,
and
can
be
adjusted
as
they
see
fit.
Until
we
have
something
like
that,
it's
just
the
same
old
frustration
game
after
game,
spending
micro
to
babysit
your
heavy
payloads
against
deliberately,
exploitatively
placed
false
targets.
|
| 13 |
\n
|
16 |
\n
|
| 14 |
Until
we
have
something
like
that,
it's
just
the
same
old
frustration
game
after
game.
|
17 |
I'm
guilty
of
taking
part
in
using
all
the
tricks
in
the
book
when
it
comes
to
messing
with
the
opponent's
AI.
nanospam
vs
moderators,
scalpels,
puppies,
occasionally
artillery.
Deliberately
picking
Guardian
when
predicting
hover
enemy.
Placing
razor/gauss
with
repair
in
arty's
way.
Using
Godde's
closed
halberd
into
AoE
zones.
Combat
terraform,
when
it
was
a
thing.
It's
all
bullshit
that
I
wish
I
didn't
have
to
do,
and
didn't
have
to
play
against,
and
it's
all
almost
mandatory
to
stay
super
competitive.
Kill
it
with
Config.
|
B964586 2 on Fairyland 1.31 (Multiplayer)