First of all, sorry for keeping you waiting, even if you are not waiting for my reply.
I do agree with your point if we are discussing without matters like personal preference since the Larvae mechanic (at least currently) almost allows Niadra to cheese through any maps, even mutators due to the guaranteed elimination of the enemy.
Imagine a Niadra player who uses the Larva to instantly kill a 10 stacked avenger Thor.
Also, if Larvae will instantly destroy any non-heroic unit upon consumption, Niadra won’t have to make any units at all in the first place.
However, I have no intention to fix this before getting my hands on the coop trigger from the sc2 editor.
To be honest, before I actually could start to create my custom commanders in the editor, everything is meaningless.
First of all, that IMO is for personal preference, just saying.
Secondly, I’ve stored this kind of mechanic for Hanson.
I am trying to make my custom commander become much more… simplistic. But as you can see I’ve already failed, again
This is a great idea.
After reading your comment, I have been thinking of some of the strains during my editing, but all I could remember is an Ultralisk which will spit into two Ultralisk with deduced damage upon morphed… they will gradually gain back their damage output and gain damage increase though.
Btw, Niadra’s upgrades require the player to meet some requirements rather than just researching. Like what I’ve said I have no intention to fix/implement this before actually editing. But still, it is a concept, It would be great to hear your thoughts about this.
No, it is a great concept.
However, again, how Niadra should work will eventually decide by personal preference and most ideally Blizzard.
I will always try my best to avoid implementing my custom commanders with the same kind of mechanics. That’s another main reason why my Niadra won’t work like yours.
Thank you for your time.