| 1 |
[b]Malus points worth noting[/b] (things i dislike and which score a lot of decrement)
|
1 |
[b]Malus points worth noting[/b] (things i dislike and which score a lot of decrement)
|
| 2 |
\n
|
2 |
\n
|
| 3 |
There are too many morphs, and are too few explanations. The redesign specification stated that every morph should have an explanation.
|
3 |
There are too many morphs, and are too few explanations. The redesign specification stated that every morph should have an explanation.
|
| 4 |
\n
|
4 |
\n
|
| 5 |
There
are
no
design
principle
i
can
infer
from
this
graph,
and
none
are
stated
-
except
"let's
have
a
lot
of
morphs",
which
is
barely
admissible.
|
5 |
There
are
no
design
principles
i
can
infer
from
this
graph,
and
none
are
stated
-
except
"let's
have
a
lot
of
morphs",
which
is
barely
admissible.
|
| 6 |
\n
|
6 |
\n
|
| 7 |
Jugglenaut is not accessible to be built directly, and is a 3do model. It is not coming back unless you remodel it, and probably not even then.
|
7 |
Jugglenaut is not accessible to be built directly, and is a 3do model. It is not coming back unless you remodel it, and probably not even then.
|
| 8 |
\n
|
8 |
\n
|
| 9 |
Glaive and raiders in general have too many morph options. Insult to injury, the ones with most morph options are also the strongest ones already.
|
9 |
Glaive and raiders in general have too many morph options. Insult to injury, the ones with most morph options are also the strongest ones already.
|
| 10 |
\n
|
10 |
\n
|
| 11 |
Flea to Roach changes movetype, and gives Spiders access to something they don't have easily. Suggest change to Tick.
|
11 |
Flea to Roach changes movetype, and gives Spiders access to something they don't have easily. Suggest change to Tick.
|
| 12 |
\n
|
12 |
\n
|
| 13 |
Redback to Recluse is just 20 metal difference. Instant transformation much?
|
13 |
Redback to Recluse is just 20 metal difference. Instant transformation much?
|
| 14 |
\n
|
14 |
\n
|
| 15 |
BD to Krow is over 400% cost difference. This is maybe acceptable on Flea, but i don't think it's ok here. This is a significant buff to BD.
|
15 |
BD to Krow is over 400% cost difference. This is maybe acceptable on Flea, but i don't think it's ok here. This is a significant buff to BD.
|
| 16 |
\n
|
16 |
\n
|
| 17 |
Zeus Crabe is self-synergetic role-transitioning movetype-changer of above 100% cost change.
|
17 |
Zeus Crabe is self-synergetic role-transitioning movetype-changer of above 100% cost change.
|
| 18 |
\n
|
18 |
\n
|
| 19 |
Mace Grizzly is role-transitioning movetype-changer of above 100% cost change.
|
19 |
Mace Grizzly is role-transitioning movetype-changer of above 100% cost change.
|
| 20 |
\n
|
20 |
\n
|
| 21 |
[b]Bonus points worth noting[/b] (that is, things i liked)
|
21 |
[b]Bonus points worth noting[/b] (that is, things i liked)
|
| 22 |
\n
|
22 |
\n
|
| 23 |
Swift morphs make sense to me.
|
23 |
Swift morphs make sense to me.
|
| 24 |
Submarine morphs make sense even while being role-changing and over 2x cost.
|
24 |
Submarine morphs make sense even while being role-changing and over 2x cost.
|
| 25 |
Firewalker to Catapult is one of the few transitions that are clean of any malus points (not movedef change; no role change; weight change within bounds)
|
25 |
Firewalker to Catapult is one of the few transitions that are clean of any malus points (not movedef change; no role change; weight change within bounds)
|
| 26 |
\n
|
26 |
\n
|
| 27 |
[b]Other notes[/b]
|
27 |
[b]Other notes[/b]
|
| 28 |
This graph requires disarming and paralyzing units to be capable of gaining experience from inflicting damage. Expect resistance, or be ready to get dirty with code.
|
28 |
This graph requires disarming and paralyzing units to be capable of gaining experience from inflicting damage. Expect resistance, or be ready to get dirty with code.
|
| 29 |
\n
|
29 |
\n
|
| 30 |
[b]Suggestions[/b]
|
30 |
[b]Suggestions[/b]
|
| 31 |
Start small. The specification requirement that morphs should be more or less evenly distributed across factories does [b]not[/b] mandate that there are a lot of them. Get rid of as many problematic ones as possible, and retain only the purest. This will maximize your chances of acceptance, and from that point you can work further.
|
31 |
Start small. The specification requirement that morphs should be more or less evenly distributed across factories does [b]not[/b] mandate that there are a lot of them. Get rid of as many problematic ones as possible, and retain only the purest. This will maximize your chances of acceptance, and from that point you can work further.
|
| 32 |
\n
|
32 |
\n
|
| 33 |
That is advice.
|
33 |
That is advice.
|
| 34 |
\n
|
34 |
\n
|
| 35 |
Also: Dominatrix is not in this graph! Any graph without Domi has no purpose!
|
35 |
Also: Dominatrix is not in this graph! Any graph without Domi has no purpose!
|
| 36 |
\n
|
36 |
\n
|
| 37 |
That was a joke.
|
37 |
That was a joke.
|
morph tree discussion