Loading...
  OR  Zero-K Name:    Password:   

show some kind of eco stats to both teams

13 posts, 970 views
Post comment
Filter:    Player:  
sort

9 years ago
seems it is within the realms of interesting for each team to have a summary of the current eco of the other. actually a bit wierd an idea
+0 / -0

9 years ago
Something like which player has more than one storage on enemy team and is safe to ignore?
+0 / -0
Skasi
9 years ago
A summary of scouted mexes and energy sources really would be handy. I wonder frequently which of two teams managed to outeco the other.
+1 / -0
9 years ago
quote:
Something like which player has more than one storage on enemy team and is safe to ignore?


you dont know my playstyle verry well do you?
+0 / -0
9 years ago
quote:

Something like which player has more than one storage on enemy team and is safe to ignore?

+5 / -0
so with a good plan everybody is on the same page?

+3 / -0


9 years ago
Economy is hard to plausibly estimate because there can be things just outside LOS that are totally wrong: like huge reclaim fields, millions of workers each producing 0.2 income, or just a singu field attached to mexes you cannot see.

However, there's ground control, which is in fact easy to estimate; and in a zero-sum game like ZK, you can just estimate HostileTerritory = 1 - MyTerritory.

Maybe i should make a "Ground Control Counter" widget akin to the casualties counter that would display scary numbers like "Ground control: 0%" from start to make you expand faster.
+2 / -0

9 years ago
if you see an energy building, you see the grid networth at that moment. plus all know taken mexes and tadaa, you have something to estimate.
+0 / -0


9 years ago
quote:
you see the grid networth at that moment

Assumes full connectivity.
+0 / -0

9 years ago
if not fully connected, the impact on the estimated information may or may be not so relevant. if you expect accuracy, get shared vision.
+0 / -0


9 years ago
I'm planning to only display the pylon grid tooltips to the players on their team. I would prefer to wait for an engine upgrade because then UnitRulesParams can be strings.
+2 / -0


9 years ago
Cue horrible workarounds such as querying mex piece rotations between frames to evaluate rotation speeds.

Imo if the information is available indirectly, it should also be available directly.
+0 / -0


9 years ago
quote:
...pylon...
Pylons don't have any visuals whereas mexes do. The mex tooltip would still be visible and that is an ok compromise because mex information is much more local.
+1 / -0