Loading...
  OR  Zero-K Name:    Password:   
Title: katastrophe's Battle
Host: DErankkatastrophe
Game version: Zero-K v1.5.8.2
Engine version: 103.0.1-1263-g90a55a2
Started: 2 months ago
Duration: 13 minutes
Players: 1
Bots: True
Mission: False
Watch Replay Now
Manual download

Team 1

DErankkatastrophe
Team 2

AI: Insane (1) <CircuitAIInsane32>
Spectators
AUrankAdminGoogleFrog

Show winners



Preview
Filter:    Player:  
sort



AUrankAdminGoogleFrog
2 months ago
Circuit got into a pretty bad energy stall here. Did something happen to circuit? Is it configured incorrectly?
+0 / -0


UAranklamer
59 days ago
(edited 59 days ago)

No metal excess until AI was raided, so seems fine to me.
But were there any changes to metal/energy pull/income calculations in ZK?
I'll compare the values that AI calculates with those that economy bar displays...

"Sharing & Overdrive" is somehow strange, and AI doesn't count it, because it's only side effect of having more energy than AI needs.
+0 / -0



AUrankAdminGoogleFrog
59 days ago
I don't think there were any changes.
+0 / -0


UAranklamer
59 days ago
I'll exclude enregy tasks from ms_pull rule (currently only mex and pylons are excluded) and will make limit of active tasks for energy larger.
Energy may be bounded by ms_pull value and it was re-configured few times.

Not sure which change is necessary to fix stalling, but AI seems to stall much less with both of those changes on current map (unless it's in the process of building 1st fusion).
+0 / -0



GBrank[GBC]1v0ry_k1ng
59 days ago
quote:
I'll exclude enregy tasks from ms_pull rule (currently only mex and pylons are excluded) and will make limit of active tasks for energy larger.
Energy may be bounded by ms_pull value and it was re-configured few times.


Can that be amended to exclude energy tasks from ms_pull rule ONLY in the event of x seconds of energy stall? The ms_pull limitation on energy structures is highly beneficial in most cases.

what is the reasoning behind pylons being excluded from ms_pull?
+0 / -0


UAranklamer
59 days ago
(edited 59 days ago)

what is the reasoning behind pylons being excluded from ms_pull?
In the middle of the game when there are many tasks along battle fronts (usually defences) AI grids very slowly: delays pylons if not enough units were built (ms_pull rule).
I guess same is happening with energy in current stable. But if it's stalling - let it build energy at high priority and it will have a chance to build more units. I didn't notice energy overproduction with described change, but more tests must be made.

WRT disregard ms_pull only until some criteria: need to test new changes without limitation first, they looked harmless in my very few tests, so i against overcomplications atm.
+0 / -0



GBrank[GBC]1v0ry_k1ng
59 days ago
the purpose of ms_pull was to prevent circuit over-spending on infrastructure & porc/ensure it still makes enough units - if you make all energy structures exempt, the rule will effectively only apply to porc
+0 / -0


UAranklamer
58 days ago
(edited 58 days ago)

well, true. But apparantly - can't exclude from ms_pull mex without energy and energy without mex, economy structures should go as a group.
To enable ms_pull for everything change mex_max to 0.99: it should mex whole map, except maybe last spot under rare conditions, and use ms_pull for everything.

I'll consider criteria to enable/disable ms_pull later after some tests.
+0 / -0



GBrank[GBC]1v0ry_k1ng
58 days ago
I feel that MS PULL should apply to everything except mex (and perhaps pylon, but not sure about that either) UNLESS either E-stalling (in which case, all BP to making energy) or metal leaking (in which case, all BP to making more BP)
+0 / -0


UAranklamer
58 days ago
Ok, next version (0.9.20, not 0.9.19) will have something like ignore ms_pull for energy only if stalling. For metal leaking: it already works almost like IK described, except that limitation is ignored but metal value is still counted.
+0 / -0