Not unreasonable, and easily done. I'll add the default upkeep and undermined upkeep to the spreadsheet. It should be available 5 to 10 minutes after this post, and then I'll calculate the 6:32 estimate. I am not 100% certain what the cost of the expansions were though, but we can figure that out later.
Powerplay Leesti undermine CANCELLED AFTER TICK.
- Thread starter CMDR Admiral Perses
- Start date
Not unreasonable, and easily done. I'll add the default upkeep and undermined upkeep to the spreadsheet. It should be available 5 to 10 minutes after this post, and then I'll calculate the 6:32 estimate. I am not 100% certain what the cost of the expansions were though, but we can figure that out later.
There we go.
Before expansions, the 6:32 AM cycle as I know it, gives Mahon a surplus of 690 CC.
Before expansions, the 6:32 AM cycle as I know it, gives Mahon a surplus of 690 CC.
Okay, thanks. That gets what I was curious about.
I must admit I perhaps was mis-stating what my point was after a while I was thinking about it - its not necessarily the turmoil itself, but it would have prevented certain expansions that could cause it.
I'll blame my anger bleeding over from this whole powerplay fiasco blinding me somewhat in blind rage over this entire ordeal.
So its the calculations of the impending expansions you had which had a negative effect - Galnet would calculate that in, creating the 332 CC estimation. The expansions causing a rough -358 effect from your 690 as I understand it.
Its not perfect, but its a rough rule we've been going by *most* of the time. Its not always accurate in that endevour.
Of course you were right, and i was mis-speaking the issue, but the undermining effect would drag the CC down to threaten turmoil.
You are right as you were not in threat of actual turmoil as it would cancel out an expansion that would put it there to ensure turmoil would not happen.
The thinking being the largest expansion with the most merits in would be the first on the list, thus canceling it out to ensure the rest. If Asgaa was denied your CC balance would still be above turmoil, but by no means at this 479.
Of course, assuming that's the logic I'd like to see. No guarantee it would be that specific system you did not get, but you would not have had at least one of your expansions.
Now this presents me with some rational behind the CC however.
I may be going out on a stretch, but I think the CC calculations went trough without the negative CC impact from the expansions affecting the changes after 7:00, leaving the Alliance with the 479 CC level.
I might be mistaken here, but to me that makes a bit more sense now at least.
That, or its all spaghetti code unraveling as the 479 doesn't look like it'll add up much when actual hard math is put to it.
But I'm just eyeballing it here.
I must admit I perhaps was mis-stating what my point was after a while I was thinking about it - its not necessarily the turmoil itself, but it would have prevented certain expansions that could cause it.
I'll blame my anger bleeding over from this whole powerplay fiasco blinding me somewhat in blind rage over this entire ordeal.
So its the calculations of the impending expansions you had which had a negative effect - Galnet would calculate that in, creating the 332 CC estimation. The expansions causing a rough -358 effect from your 690 as I understand it.
Its not perfect, but its a rough rule we've been going by *most* of the time. Its not always accurate in that endevour.
Of course you were right, and i was mis-speaking the issue, but the undermining effect would drag the CC down to threaten turmoil.
You are right as you were not in threat of actual turmoil as it would cancel out an expansion that would put it there to ensure turmoil would not happen.
The thinking being the largest expansion with the most merits in would be the first on the list, thus canceling it out to ensure the rest. If Asgaa was denied your CC balance would still be above turmoil, but by no means at this 479.
Of course, assuming that's the logic I'd like to see. No guarantee it would be that specific system you did not get, but you would not have had at least one of your expansions.
Now this presents me with some rational behind the CC however.
I may be going out on a stretch, but I think the CC calculations went trough without the negative CC impact from the expansions affecting the changes after 7:00, leaving the Alliance with the 479 CC level.
I might be mistaken here, but to me that makes a bit more sense now at least.
That, or its all spaghetti code unraveling as the 479 doesn't look like it'll add up much when actual hard math is put to it.
But I'm just eyeballing it here.
Last edited:
After the tick I made a little sheet myself to figure out what went down. Hopefully it's even correct
You can tick UM/fort states to see how the end result would have changed. Right now the end results are ticked (and marked yellow) as I don't know how things really looked at cycle tick. I'm pretty sure Partha was already cancelled before the tick, so the bomb would have been Leesti & Kokoimudji. If Leesti hadn't been fortified the Alliance would have still gotten all expansions and came out with 200+ CC. That's if they didn't fortify about ~10 systems (depending on their default CC upkeep) after the tick that weren't done before (which wouldn't be impossible for them with their usual strategy to push up several systems up to near completion). So in the end I can't see from the results whether the Alliance either did close a lot of systems after the tick or if the majority of those were already done. I'm more inclined to believe the second possibility is how it went down, but without actual cycle tick data from FDev (which even they can't get apparently) we'll never know for sure.The CC effects of the expansions were taken into effect correctly from what I can tell, judging that the sheet gives out the correct end balance after expansion costs. Or I just got the end result right with wrong inputs
Everybody is really angry about the tick and everything that it did, and it's easy to get everything conflated once everything is this messy. Especially when it looks like your hard work was negated by us cheating.
THAT is the reason I've been taking my time to explain what we think the proper tick outcome should have been. It's why I've been exceedingly open with our numbers, because there's no way in Helmand that if the roles were reversed, that I wouldn't be foaming at the mouth angry. So I've been (I hope) quite diplomatic in my attempts at explaining this, to the point that I think I even managed to convince Basskicker that I'm not trying to cover our asses, and that as far as we can tell, while you did great work against the insane AI, the difficulty was simply higher than you could overcome.