| 1 |
I am not sure why people say that ZK is a 'macro game' any more than many other RTS? Macro is very important in anything that I would call an RTS. Perhaps people like to call the large scale exponential economy games 'macro games' (think NOTA or SupComm) and lump ZK in the same category due to shared roots.
|
1 |
I am not sure why people say that ZK is a 'macro game' any more than many other RTS? Macro is very important in anything that I would call an RTS. Perhaps people like to call the large scale exponential economy games 'macro games' (think NOTA or SupComm) and lump ZK in the same category due to shared roots.
|
| 2 |
\n
|
2 |
\n
|
| 3 |
Macro is very important in Starcraft and you spend a lot of your time actively manage it to keep it ticking over. Perhaps it is considered to be micro oriented because a lot of micro is required for decent effectiveness of many army compositions.
|
3 |
Macro is very important in Starcraft and you spend a lot of your time actively manage it to keep it ticking over. Perhaps it is considered to be micro oriented because a lot of micro is required for decent effectiveness of many army compositions.
|
| 4 |
\n
|
4 |
\n
|
| 5 |
Perhaps
ZK
is
considered
a
macro
game
because
we
have
comparatively
intelligent
units
and
a
powerful
UI.
Many
difficult
things
in
Starcraft
are
easy
in
ZK.
In
Starcraft
is
is
impressive
when
a
pro
player
executes
the
kind
of
split
made
easy
with
line
move.
Kiting
Marines
with
Stalkers
can
take
all
your
attention.
The
reasoning
would
then
be
that
the
ZK
UI
removes
all
of
that
micro
and
so
what
remains
must
be
a
game
about
macro.
|
5 |
Perhaps
ZK
is
considered
a
macro
game
because
we
have
comparatively
intelligent
units
and
a
powerful
UI.
Many
difficult
things
in
Starcraft
are
easy
in
ZK.
In
Starcraft
it
is
impressive
when
a
pro
player
executes
the
kind
of
split
made
easy
with
line
move.
Kiting
Marines
with
Stalkers
can
take
all
your
attention.
The
reasoning
would
then
be
that
the
ZK
UI
removes
all
of
that
micro
and
so
what
remains
must
be
a
game
about
macro.
|
| 6 |
\n
|
6 |
\n
|
| 7 |
I think that removing this micro has revealed more micro hiding underneath. You cannot just make a battle plan and sit back. Targets will need assigning as they are revealed. Skirmishing units may have to advance or retreat. Most raiding requires you to rapidly decide and implement what you want to kill and whether your raider needs to try to survive. Both players get the powerful UI which allows them to stack layers of complexity on battles which would otherwise be limited to who can keep their Rockos at range most effectively.
|
7 |
I think that removing this micro has revealed more micro hiding underneath. You cannot just make a battle plan and sit back. Targets will need assigning as they are revealed. Skirmishing units may have to advance or retreat. Most raiding requires you to rapidly decide and implement what you want to kill and whether your raider needs to try to survive. Both players get the powerful UI which allows them to stack layers of complexity on battles which would otherwise be limited to who can keep their Rockos at range most effectively.
|
| 8 |
\n
|
8 |
\n
|
| 9 |
The macro:micro clicks ratio is possibly higher in ZK because you tend to constantly be engaged in skirmishes and you do not have to manage each individual action of your economy.
|
9 |
The macro:micro clicks ratio is possibly higher in ZK because you tend to constantly be engaged in skirmishes and you do not have to manage each individual action of your economy.
|
| 10 |
\n
|
10 |
\n
|
| 11 |
Automation does not aim to remove micromanagement. Broadly I think I have three aims.
|
11 |
Automation does not aim to remove micromanagement. Broadly I think I have three aims.
|
| 12 |
\n
|
12 |
\n
|
| 13 |
== 1. Reduce the gap between the complexity of a decision and micro required to execute it. ==
|
13 |
== 1. Reduce the gap between the complexity of a decision and micro required to execute it. ==
|
| 14 |
Say you decide that a nanoframe needs to be complete ASAP but you are at a 2x metal stall. I would call this a fairly simple decision, but without priority you would have to pause many of your other constructions to free up the metal income. You could decide that your Bandits should kite any Glaives they encounter so give them an Attack Move order (you also have to choose where they should move). Without kiting on Attack Move you would need to click a lot whenever your Bandits run into Glaives.
|
14 |
Say you decide that a nanoframe needs to be complete ASAP but you are at a 2x metal stall. I would call this a fairly simple decision, but without priority you would have to pause many of your other constructions to free up the metal income. You could decide that your Bandits should kite any Glaives they encounter so give them an Attack Move order (you also have to choose where they should move). Without kiting on Attack Move you would need to click a lot whenever your Bandits run into Glaives.
|
| 15 |
\n
|
15 |
\n
|
| 16 |
In these examples the number of actions required is roughly equal to the number of decisions made. The micro is introduced when you suddenly are required to make many decisions. For example your Bandits could come across a bunch of Glaives guarding a commander. You have to decide whether to keep kiting the Glaives or to run in and kill the commander. You'll have to use the set target command to communicate your decision to attack the commander. Perhaps there are some turrets around, should you target them first? Maybe it is not obvious which side to attack from. Perhaps you decloak a nearby Sniper during the battle, should you switch targets?
|
16 |
In these examples the number of actions required is roughly equal to the number of decisions made. The micro is introduced when you suddenly are required to make many decisions. For example your Bandits could come across a bunch of Glaives guarding a commander. You have to decide whether to keep kiting the Glaives or to run in and kill the commander. You'll have to use the set target command to communicate your decision to attack the commander. Perhaps there are some turrets around, should you target them first? Maybe it is not obvious which side to attack from. Perhaps you decloak a nearby Sniper during the battle, should you switch targets?
|
| 17 |
\n
|
17 |
\n
|
| 18 |
On top of these decisions you really have to tell your units exactly where to go because they do not know what you are planning to do from one second to the next. Messing with state toggles that fast is infeasible so we are left with line move as the best UI to communicate decisions at that speed.
|
18 |
On top of these decisions you really have to tell your units exactly where to go because they do not know what you are planning to do from one second to the next. Messing with state toggles that fast is infeasible so we are left with line move as the best UI to communicate decisions at that speed.
|
| 19 |
\n
|
19 |
\n
|
| 20 |
Anyone who says ZK lacks micro has not had a good go at 1v1.
|
20 |
Anyone who says ZK lacks micro has not had a good go at 1v1.
|
| 21 |
\n
|
21 |
\n
|
| 22 |
== 2. Make balance at lower skill levels approximate the balance at high levels of skill. ==
|
22 |
== 2. Make balance at lower skill levels approximate the balance at high levels of skill. ==
|
| 23 |
I would like the 'real' balance of ZK to be accessible to many people. By this I mean that the rough shape of interaction between unit types is similar between many levels of play. Obviously it is impossible for units to remain the same over all levels of play but I can at least try.
|
23 |
I would like the 'real' balance of ZK to be accessible to many people. By this I mean that the rough shape of interaction between unit types is similar between many levels of play. Obviously it is impossible for units to remain the same over all levels of play but I can at least try.
|
| 24 |
\n
|
24 |
\n
|
| 25 |
For example imagine that Bandits could not be told to kite Glaives. This would have little effect at high levels of play but it would drastically change their relationship at the level where people do not have the attention to kite Glaives (this high level of play is far beyond our [i]current[/i] highest level). You can imagine examples like this for every bit of automation.
|
25 |
For example imagine that Bandits could not be told to kite Glaives. This would have little effect at high levels of play but it would drastically change their relationship at the level where people do not have the attention to kite Glaives (this high level of play is far beyond our [i]current[/i] highest level). You can imagine examples like this for every bit of automation.
|
| 26 |
\n
|
26 |
\n
|
| 27 |
Unit automation exists here to give units reasonable default behaviours. These defaults should correspond to a common way that the unit is used in high level play. This gives lower level players a taste of the real balance and mechanics of the unit without them having to execute complex micromanagement. Sure, they will be beaten by more skilled players who know when to make the default decision and when to execute the alternatives. But at least more players get a taste of how the unit should be used.
|
27 |
Unit automation exists here to give units reasonable default behaviours. These defaults should correspond to a common way that the unit is used in high level play. This gives lower level players a taste of the real balance and mechanics of the unit without them having to execute complex micromanagement. Sure, they will be beaten by more skilled players who know when to make the default decision and when to execute the alternatives. But at least more players get a taste of how the unit should be used.
|
| 28 |
\n
|
28 |
\n
|
| 29 |
Removing bits of automation increases the time investment (in micro training) required before a new player would get to play 'real' ZK. Creating a resiliently balanced game would be even harder than it is now.
|
29 |
Removing bits of automation increases the time investment (in micro training) required before a new player would get to play 'real' ZK. Creating a resiliently balanced game would be even harder than it is now.
|
| 30 |
\n
|
30 |
\n
|
| 31 |
== 3. Let us get away with adding more complicated and nuanced mechanics. ==
|
31 |
== 3. Let us get away with adding more complicated and nuanced mechanics. ==
|
| 32 |
As a designer, automation allows me to ask players to do more things at once. You can have a Rocko/Storm battle running while simultaneously attacking elsewhere with Bandits and managing your expansion. These situations will require attention and management but at least your Rogues will dance about by themselves and the Bandits will not run in and die if they encounter some Glaives. The automation will not implement any great decisions for your units but it at least maintain a holding pattern. It lowers the APM required for this level of play.
|
32 |
As a designer, automation allows me to ask players to do more things at once. You can have a Rocko/Storm battle running while simultaneously attacking elsewhere with Bandits and managing your expansion. These situations will require attention and management but at least your Rogues will dance about by themselves and the Bandits will not run in and die if they encounter some Glaives. The automation will not implement any great decisions for your units but it at least maintain a holding pattern. It lowers the APM required for this level of play.
|
| 33 |
\n
|
33 |
\n
|
| 34 |
The mechanics of slow projectiles, turnrates, acceleration, blocking etc... would make interactions too complex to handle more than one at time for most people. With automation to implement some handling of these interactions they are 'allowed' to exist.
|
34 |
The mechanics of slow projectiles, turnrates, acceleration, blocking etc... would make interactions too complex to handle more than one at time for most people. With automation to implement some handling of these interactions they are 'allowed' to exist.
|
| 35 |
\n
|
35 |
\n
|
| 36 |
\n
|
36 |
\n
|
| 37 |
These there points are sort of aspects of the same thing. It is not really a critique of Starcraft. It is my current thoughts on what the automation in ZK does and why it is there.
|
37 |
These there points are sort of aspects of the same thing. It is not really a critique of Starcraft. It is my current thoughts on what the automation in ZK does and why it is there.
|
Starcraft II Sucks!