An important matter adjacent to that of the weekly reset, the reset itself still being ahead of anything else regarding a redesign—
It is quite obvious that Control systems changed on Monday (30th January 3309), accidentally or otherwise, such that they become suddenly insurmountable. Having watched every point of progress occur in every system quite closely since the start, I made a note of this just after checking at the end of Tuesday:
I suspect quite strongly that Control systems were changed some time yesterday, given that only around 12 hours passed between spotting the first point in Hyades Sector ZZ-O b6-6 and that system becoming complete.
Also, from a Commander who has done
likely more than any to test and document exactly how much Thargoid destruction is required in a Control system:
@Bruce G this patch seems to have broken the war mechanics in thargoid controlled systems.
Progress in them has come to a screaming halt. Killing large amounts of thargoids, far more than enough to have caused an observable effect before the patch, now apparently gives no contribution towards the war.
As an example HIP 20605 went from 0 to 48% in the 24 hours before the patch but hasn't moved at all since then.
That comment itself serves as the direct feedback for that individual occasion, while this feedback post is regarding changes in general. I understand fully that such changes will occur, for as much was stated from the start, however the specific problem here is that the requirement was increased
in the middle of a cycle.
This is connected inextricably to the weekly reset because the latter is designed to make Commanders organise and plan, for which the effort requirement is critical input information:
- Ideally (to state the obvious), nothing would change at all.
- Realistically, it is fair to expect the occasional Thursday morning requirement change.
- At most, one might allow that each Thursday morning includes some incremental requirement change.
- If a mid-cycle change must occur, it may be a requirement reduction without disrupting plans, but may not be a requirement increase.
The Control systems which a lot of Commanders had organised to complete, and in which they had half-invested already, became suddenly beyond scope. That was a lot of time from a lot of people which would have gone otherwise towards completing more of the top Invasion systems.
My suggestion is that changes to the completion requirements are allowed, but become
very strictly controlled regarding when they occur, and perhaps that changes by more than a few percent are announced immediately. To reiterate a comment I made earlier:
The capability is the concern here; the very quantity you are attempting to measure must be varying wildly.
Wherever rates are involved, a fundamental property of measuring them is that such a measurement must occur over time, and also that a high-confidence, low-variance measurement is only achieved by spending more time measuring it (basic uncertainty principle, applies almost everywhere). To modify the completion requirement is to introduce a second-order rate of change, which is guaranteed to cause some amount of oscillation. To do so abruptly will cause immediate instability and undermine any balancing attempt, as well as cause frustration of course.
If the change was unintentional, the point stands that any possibility of such a change needs to be controlled strictly, if only to prevent a recurrence. To be sure though, even if the change was deliberate, consider the responses:
- Commanders perceive Control systems as being easy, therefore invest in them.
- Control systems ruled to be too easy based on data, therefore strengthen them.
- Commanders detect the change, therefore remove all investment (accepting the sunk cost), halting all future Control progress.
- Control systems ruled to be too difficult based on data, therefore weaken them.
By all means use data to make decisions, but please understand that this is a much more complicated feedback loop than, for example, a device which can heat a bowl of water up to a specific temperature. For example, if your measurements indicate that Control systems move around twice as quickly as intended, one cannot simply double the requirement and expect the number of Control completions to halve. Doubling that requirement will also cause withdrawal of the investment, dropping the Control completion to a much smaller fraction than half, and probably below the threshold (imposed by the weekly reset) to see any Control completions at all.
Hopefully you can see the oscillation created by the scenario above, and agree that such an oscillation contradicts the intended balance which the adjustments aim to achieve.