1 |
Luarules
version
will
[url=https://github.
com/ZeroK-RTS/Zero-K/blob/master/LuaRules/Gadgets/dbg_dev_commands.
lua#L414]not
give
the
inaccessible
units[/url].
|
1 |
To
spawn
anything
at
all
you
first
need
to
enable
cheats.
Host
a
private
battle
and
type
{
{
{
!cheats}
}
}
|
2 |
\n
|
2 |
\n
|
3 |
To
spawn
units
you
first
need
to
enable
cheats.
Host
a
private
battle
and
type
{
{
{
!cheats}
}
}
|
3 |
The
Luarules
version
will
[url=https://github.
com/ZeroK-RTS/Zero-K/blob/master/LuaRules/Gadgets/dbg_dev_commands.
lua#L414]not
give
the
inaccessible
units[/url].
|
|
|
4 |
/give all is likely to explode stuff and will be filled with a lot of chaff (50 versions of each com chassis etc.).
|
|
|
5 |
The safest way is to spawn units individually.
|
4 |
\n
|
6 |
\n
|
5 |
You
can
see
most
units
listed
[url=https://github.
com/ZeroK-RTS/Zero-K/tree/master/units]here[/url].
Check
the
inside
of
the
file
for
the
usual
name
(
armpw.
lua
->
Glaive)
.
To
spawn
the
unit,
use
the
file
name,
for
example
when
the
file
is
called
{
{
{
hoversonic.
lua}
}
}
then
you
can
spawn
the
relevant
unit
with
the
command
{
{
{
/give
hoversonic}
}
}
|
7 |
You
can
see
most
units
listed
[url=https://github.
com/ZeroK-RTS/Zero-K/tree/master/units]here[/url].
Check
the
inside
of
the
file
for
the
usual
name
(
armpw.
lua
->
Glaive)
.
To
spawn
the
unit,
use
the
/give
command
with
the
file
name,
for
example
when
the
file
is
called
{
{
{
hoversonic.
lua}
}
}
then
you
can
spawn
the
relevant
unit
with
the
command
{
{
{
/give
hoversonic}
}
}
|
6 |
\n
|
8 |
\n
|
7 |
Note: this will not show some mission-exclusive ones (like orbital bombardment) or customized ones (for example mission Sunlance is different to the spawnable MP one).
|
9 |
Note: this will not show some mission-exclusive ones (like orbital bombardment) or customized ones (for example mission Sunlance is different to the spawnable MP one).
|