The morph system was removed because its mechanics, implementation and polish levels had dropped below some arbitrary threshold and nobody fixed it for a lengthy period of time. Apparently a decent number of people like morph so perhaps one of them will fix it. There are a lot of issues so perhaps a group of them will be required.
Turret morphs which cause footprint problems are not going to be readded. Turret morphs in general are unlikely to be readded because morphing a turret is a fairly static thing involving your opponent suciding their units into your defense. There are also very few possibilities due to the footprint problem.
The three main gameplay issues are as follows. They are addressed in by changes required in the ticket.
-
Farming and randomness - I think this would mostly be addressed by requirement 4.
-
Free BP - Would be fixed by optional requirement 6. Otherwise morph times can be increased for light units. Less of an issue in practice because Commanders are already a reliable source.
-
Automatic Synergy - Zeus -> Crabe was a morph which gave your army automatic synergy with itself. The fix is to simply not implement such role crossing morphs.
Apart from gameplay fixes there are many bugs and UI polish issues which would need to be fixed. ZK will need to reach this level of polish and I don't want to spend my own time on the backlog of issues that have grown up around morph.
Also here is a morph discussion with Klon:
http://pastebin.com/hXZMu9h6The morph gadget is 7-year-old spaghetti and I would not like patches which further hinder maintainability. I advise an initial cleanup of the code.
------------------------------------------------------------
Ticket:
https://github.com/ZeroK-RTS/Zero-K/issues/340These are the requirements for readding an XP morph system.
1. Fix the issues in this ticket:
https://github.com/ZeroK-RTS/Zero-K/issues/1652. Fix the way morph is handled by Integral Menu:
-
If some units in a selection have the required XP to morph then the morph button should be active. Currently the activation of the button depends on which unit was added first.
-
Clicking the morph button when many units are able to morph should only give one morph order. Ctrl+click could give all eligible units the order.
-
The morph button should not also be the stop morph button. Create a 'Stop Morph' button with a different image and description.
-
Morph (and stop morph) commands should be placed after every other ordinary command to better preserve the command placement order for the rest of the menu. They should be before Retreat Zone and Ferry.
-
Fix the bug where a morph option from the previously selected set of units appears at the bottom of the command card for the newly selected units. This button is often larger than the rest of the buttons. This bogus command remains even when no units are selected. To reproduce select a unit with a greyed out morph, then select a commander with a commander morph, then select the unit with the greyed out morph.
-
Improve the tooltip to convey what morph is, what the rank requirement is and why the button is greyed out.
3. Improve rank display and make morph easier to spot.
-
Ranks should correspond to the ranks set out by the morph gadget. They currently do not.
-
Ranks should be displayed for enemy units to increase the interaction provided by the system.
-
Units (or their rank icon) should flash or otherwise be more obvious for several seconds after they gain the required rank to morph. A morph-able rank should be more obvious in general.
-
Selected units should somehow have their unit portrait modified (perhaps with an icons) if they are able to morph.
4. Improve the XP system:
-
Remove the last hit bonus for XP. This mechanic is the worst offender for the creation of tedious farming and farm countering (self-ding your units or causing chain explosions to deny large amounts of XP).
-
This will require a re-balance of the rank system if the ranks are supposed to be 1x, 2x and 3x cost.
-
A suggested gadget implementation is to subtract XP from a unit whenever it kills something in such a way that the bonus is counteracted.
-
A better implementation would be to provide a patch for the engine which makes the last hit bonus configurable.
5. A well thought out morph graph. Consider whether monospam + morph becomes a viable strategy (eg Zeus -> Crabe to counter the counters to Zeus). Give reasons for each morph.
6. (Optional requirement that grants a lot more friendliness towards the system)
Nanoframe morph. Constructors have to do stuff to a morphing unit to make it progress. This removes concerns about free BP. Care has to be applied to make sure that UI for this is good.
If 6 is not implemented then low level morphs may need to take a bit longer to reduce their ability to completely tank your economy.
------------------------------------------------------------