1 |
@Licho - I was thinking the same thing, actually - a con that drops a bomb. Bomb is a zero-cost "egg" that automatically starts morphing into an immobile nanoturret-like unit.... say, 110 cost 5m/s builder (tricky to balance against the Caretaker, though). Making its deployment morph-based eliminates the bomber having a "firing cost" and the problems associated with that, instead the "cost" being a morph intrinsic to the unit itself. Also, you could start queuing orders while the builder is deploying/morphing, which would help a bit with the lack of queue-ability associated with the builder-dropper itself.
|
1 |
@Licho - I was thinking the same thing, actually - a con that drops a bomb. Bomb is a zero-cost "egg" that automatically starts morphing into an immobile nanoturret-like unit.... say, 110 cost 5m/s builder (tricky to balance against the Caretaker, though). Making its deployment morph-based eliminates the bomber having a "firing cost" and the problems associated with that, instead the "cost" being a morph intrinsic to the unit itself. Also, you could start queuing orders while the builder is deploying/morphing, which would help a bit with the lack of queue-ability associated with the builder-dropper itself.
|
3 |
The trick would be balancing it with the Caretaker though... I mean, how do you make this thing useful without making it OP compared to the Caretaker, or UP compared to a mobile builder?
|
3 |
The trick would be balancing it with the Caretaker though... I mean, how do you make this thing useful without making it OP compared to the Caretaker, or UP compared to a mobile builder?
|