Loading...
  OR  Zero-K Name:    Password:   
Title: 1v1: All welcome!
Host: CZrankElerium
Game version: Zero-K v1.2.1.4
Engine version: 91.0
Battle ID: 230364
Started: 11 years ago
Duration: 7 minutes
Players: 2
Bots: False
Mission: False
Rating: Competitive
Watch Replay Now
Manual download

Team 1
Chance of victory: 50%

GBrankExit_Wound
Team 2
Chance of victory: 50%

GBrankTheSponge

Show winners



Preview
Filter:    Player:  
sort
11 years ago
Never rely on Ecell. You will get your com sniped and then have no E to build more E generators with. A solar at each mex seems like the best way to prevent E stalling and maintain a good E income.
+0 / -0
11 years ago
Don't lose your comm then
Ecell is a huge boost to your expansion
+0 / -0

11 years ago
What's the point of having Ecell if you're not going to rely on it?
+0 / -0
11 years ago
Having an E cell is great at the start, but a few solars near your first few mexes is a good investment to keep your energy economy going strong and to make sure that you are not completely crippled if you lose your com early.
+0 / -0

11 years ago
E cell is risky, i prefer the autorepair module but, you lack some metal and e at start if you do that. You must make sure you dont get raided because of that.
+0 / -0


11 years ago
You moved an Ecell support commander with no weapon across the map such that you were halfway to the opponents base. Also they had Scorchers and you knew they had Scorchers. The way to use Ecell (or keep your commander in general) is to not do what you did.
+5 / -0
quote:
You moved an Ecell support commander with no weapon across the map such that you were halfway to the opponents base. Also they had Scorchers and you knew they had Scorchers. The way to use Ecell (or keep your commander in general) is to not do what you did.

I blame the suicide widget auto-reclaim widget.
+0 / -0


11 years ago
I agree that the comm dies way too often when using the autoreclaim widget, because it always seems to have better things to do than shooting enemies. Exclude commander from the widget imo.
+1 / -0
More to the point, maybe uses of an unit's build powers should be consistent with their compatibility to shoot.

You can build and shoot, but not cloak.
You can reclaim and neither shoot nor cloak.
You can rez and not shoot, but can cloak.

I mean.. what?
+3 / -0
What widget is this? How did you come to use it?

EErankAdminAnarchid you could lus that.
+0 / -0

11 years ago
I guess this happens when you rely on widgets to play for you.
+1 / -1
I don't think TheSponge really used the widget here.

But Godde did in his recent game vs randy on deadlands, leading to a hilarious commander suicide and ensuing bug report on forum.

quote:
you could lus that.

So it's just a script bug then? Not something enginesque?
+0 / -0


11 years ago
http://code.google.com/p/zero-k/source/browse/trunk/mods/zk/LuaUI/Widgets/unit_auto_reclaim_heal_assist.lua
+0 / -0
11 years ago
quote:
What widget is this? How did you come to use it?

It is the one FIranksprang posted below. I activated it through the f11 menu.
+0 / -0


11 years ago
So what then, kill the widget? I've never used it and as far as I can tell it was just randomly added at some point.

Attack and Lathe behaviour is poorly defined. Any constructor with a build command can attack unimpeded but those with Repair or any other con command do not automatically attack. They do attack if you give them a settarget command. This is inconsistent behaviour in Spring, it would be best if it automatically targeted in every situation and left it up to the LUS to decide when aiming is blocked. We could get around this by blocking it in every situation which would be fine by me.
+0 / -0
quote:
LUS

What does it mean? Line ufff sight?
+0 / -0
Liberal Underhandedness Squad.

(actually it's lua unit script, a replacement for COB - Completely OBsolete - standard which was used with 3do - "three decades old" - models.)

(ZK still has some completely obsolete scripts for three decades old models, ex: Reef)
+3 / -0