Increasing ratio of TCs : Megas as game progresses

[phoenixffyrnig]

Offshoot from a discussion elsehwere

I have been wondering if we have too many mega buildings? Could the limit scale downwards, eg first 2 megas req 2 TCs each, next 3 megas req 3 TCs, etc...? ie, I'd rather make them rarer than nerf them.

I also feel that at higher TC counts we have too many mega slots, so I agree here,

Especially on larger maps the number of castles and trebs in the field does become quite tedious. On smaller maps (eg 5 or 6 TCs each) we only have slots for 2 or 3 megas. This is fine i think.

So we probably need a sliding scale of mega slots. Exact details are open to debate, the above suggestion is merely an example of the idea.

[Endru1241]

Especially on larger maps the number of castles and trebs in the field does become quite tedious.

Number of everything becomes too much in larger maps.
Normal factories are 1.25 x TC number, while megas only 0.5 (but minimum of 1).

If we tried to limit megas - factories should probably be scaled similarly too (but of course in smaller impact).

However that won't stop really the most spamming and tedious part - too many workers and all their byproducts.
On the contrary - with even bigger difference of scale between TC capable of producing workers and megas with trebs - I am afraid general tediousness of management could have even gone up after such change.

[b2198]

So the real problem is the TC amount on larger maps? I might have some ideas to make that more customizable, but that's for the future. Meanwhile, I still think the ratio of 2 TCs to 1 mega is still a bit too low, maybe we could make some function that gives that ratio with a low TC count and a bigger one as TC counts increase?

Something like:
1-3 TCs -> 1 mega
4-5 TCs -> 2 megas
6-8 TCs -> 3 megas
9-12 TCs -> 4 megas
13-18 TCs -> 5 megas
x TCs -> max(1, 2 * max(0, x - 3)^0.4)

Python script to check for other simplified polynomial functions, if needed:

Code: Select all

from math import floor

def tcToMegaFunction(
    minimum = 1,
    xTranslation = 0,
    yTranslation = 0,
    coeficient = 1,
    exponent = 1,
    startingAmount = 1,
    finalAmount=20,
    turnNegativesInto0s = True
):
    for i in range(startingAmount, finalAmount + 1):
        translatedX = max(0, i + xTranslation) if turnNegativesInto0s else i + xTranslation
        print("{:d} TCs -> {:d} megas".format(i, floor(max(minimum, coeficient * translatedX**exponent + yTranslation))))

# current function
tcToMegaFunction(minimum = 1, xTranslation = 0, yTranslation = 0, coeficient = 1/2, exponent = 1)

# proposed function
tcToMegaFunction(minimum = 1, xTranslation = -3, yTranslation = 0, coeficient = 2, exponent = 0.4)

Or Geogebra link to the graph of the function with the first 4 parameters to tweak

[makazuwr32]

This might be fine but it will require rewriting engine for all ao games by stratego.

And while it might be fine for aos but for aof for example it will not be good.

I am against such variant.

[Endru1241]

If anything - I'd rather use logarithmic scale.

But to balance things out - many other aspects would need to be limiter in logarithmic scale.

Which all by the end of the day may have turned out futile or even worse - breaking something.

My point was - it's overcomplicating things out for no good reason.

[b2198]

This might be fine but it will require rewriting engine for all ao games by stratego.

And while it might be fine for aos but for aof for example it will not be good.

I am against such variant.

Oh, right, I forgot all ao games use the same factory limits, nevermind then,

it's overcomplicating things out for no good reason.

[phoenixffyrnig]

However that won't stop really the most spamming and tedious part - too many workers and all their byproducts.
On the contrary - with even bigger difference of scale between TC capable of producing workers and megas with trebs - I am afraid general tediousness of management could have even gone up after such change.

Ah yes, good point. As far-sighted as always

[makazuwr32]

This might be fine but it will require rewriting engine for all ao games by stratego.

And while it might be fine for aos but for aof for example it will not be good.

I am against such variant.

Oh, right, I forgot all ao games use the same factory limits, nevermind then,

it's overcomplicating things out for no good reason.

Not same factory limits but same base formula.
We can change mulitpliers per tc for each separate ao-variant. But that is all.

[b2198]

Not same factory limits but same base formula.
We can change mulitpliers per tc for each separate ao-variant. But that is all.

Ooh, I see, thanks for the clarification.