Exo Wave Costs

[TechSY730]

Short of querying the ship type definitions in the code, is there a way I can get the exo costs (both the "nice names" and the numeric) of all the various eligible ships for exos?

[keith.lamothe]

The reference-tab export gives you EventAttackTier and EventAttackSubTier columns.  If a row lacks those, the type is not exo-eligible.

The actual numeric costs are set in this block:

Code: [Select]

            SetReferenceCost( EventAttackTier.Drone, EventAttackSubTier.Light, 1 );
            SetReferenceCost( EventAttackTier.Drone, EventAttackSubTier.Medium, 2 );
            SetReferenceCost( EventAttackTier.Drone, EventAttackSubTier.Heavy, 3 );
            SetReferenceCost( EventAttackTier.Cutter, EventAttackSubTier.Light, 4 );
            SetReferenceCost( EventAttackTier.Cutter, EventAttackSubTier.Medium, 6 );
            SetReferenceCost( EventAttackTier.Cutter, EventAttackSubTier.Heavy, 8 );
            SetReferenceCost( EventAttackTier.Corvette, EventAttackSubTier.Light, 16 );
            SetReferenceCost( EventAttackTier.Corvette, EventAttackSubTier.Medium, 24 );
            SetReferenceCost( EventAttackTier.Corvette, EventAttackSubTier.Heavy, 32 );
            SetReferenceCost( EventAttackTier.Frigate, EventAttackSubTier.Light, 64 );
            SetReferenceCost( EventAttackTier.Frigate, EventAttackSubTier.Medium, 96 );
            SetReferenceCost( EventAttackTier.Frigate, EventAttackSubTier.Heavy, 128 );
            SetReferenceCost( EventAttackTier.Destroyer, EventAttackSubTier.Light, 256 );
            SetReferenceCost( EventAttackTier.Destroyer, EventAttackSubTier.Medium, 384 );
            SetReferenceCost( EventAttackTier.Destroyer, EventAttackSubTier.Heavy, 512 );
            SetReferenceCost( EventAttackTier.Cruiser, EventAttackSubTier.Light, 1024 );
            SetReferenceCost( EventAttackTier.Cruiser, EventAttackSubTier.Medium, 1536 );
            SetReferenceCost( EventAttackTier.Cruiser, EventAttackSubTier.Heavy, 2048 );
            SetReferenceCost( EventAttackTier.Battleship, EventAttackSubTier.Light, 4096 );
            SetReferenceCost( EventAttackTier.Battleship, EventAttackSubTier.Medium, 6144 );
            SetReferenceCost( EventAttackTier.Battleship, EventAttackSubTier.Heavy, 8192 );
            SetReferenceCost( EventAttackTier.Dreadnought, EventAttackSubTier.Light, 16384 );
            SetReferenceCost( EventAttackTier.Dreadnought, EventAttackSubTier.Medium, 24576 );
            SetReferenceCost( EventAttackTier.Dreadnought, EventAttackSubTier.Heavy, 32768 );
            SetReferenceCost( EventAttackTier.Mauler, EventAttackSubTier.Light, 65536 );
            SetReferenceCost( EventAttackTier.Mauler, EventAttackSubTier.Medium, 98304 );
            SetReferenceCost( EventAttackTier.Mauler, EventAttackSubTier.Heavy, 131702 );
            SetReferenceCost( EventAttackTier.Planetoid, EventAttackSubTier.Light, 262144 );
            SetReferenceCost( EventAttackTier.Planetoid, EventAttackSubTier.Medium, 393216 );
            SetReferenceCost( EventAttackTier.Planetoid, EventAttackSubTier.Heavy, 524288 );

[TechSY730]

Oh dang. Is there anything that is considered a heavy planetoid for exo waves?

[keith.lamothe]

No, the mothership and H/K-V are both Light Planetoid, and that's as high as it's gone.  The H/K-V probably shouldn't be even that high, hard to say.

[TechSY730]

No, the mothership and H/K-V are both Light Planetoid, and that's as high as it's gone.  The H/K-V probably shouldn't be even that high, hard to say.

Wasn't the problem that the MK. I H/K was too cheap (and by extension, the other Mks of H/Ks) and thus were bumped up in cost?
(Each mark goes up one step in the cost tier, right?)

However, while Light planetoid is too expensive for H/K V, as shown previously Heavy mauler was too cheap for H/K V. Does that mean their should be more granularity in the higher echelons of the exo-costs, and reassign accordingly?

Like if not even Motherships, the toughest unit in the game, is touch enough to be worth a heavy planetoid (at 524288 cost), doesn't that mean that the scale goes too high, and the scale should be adjusted such that the toughest unit is worth the most expensive classification?
For example, make heavy planetoid something closer to 262144, rescale light mauler and up accordingly, and then you get more flexibility in classification for the big stuff. Like having a cost for H/K Vs that is not too cheap and not too expensive.

[keith.lamothe]

No, I don't think that stuff is necessary, because it's already fun   You're looking at the hotdog factory machinery.  That's never as pleasant as a well-served hotdog.

[TechSY730]

No, I don't think that stuff is necessary, because it's already fun   You're looking at the hotdog factory machinery.  That's never as pleasant as a well-served hotdog.

Aww, but I like the looking at things with an absurd level of detail, and knowing how everything works, even if it can get messy.

Oh well, you are right though. The balance, although could be better, is pretty good, which is good enough for something that very occasional like exo-waves.

[Solarity]

No, please, dont do it, god no!  I dont think I could cope with more than one mothership coming at me, 30 - 40 HKs are quite bad enough.

[TechSY730]

No, please, dont do it, god no!  I dont think I could cope with more than one mothership coming at me, 30 - 40 HKs are quite bad enough.

If exo costs were refactored, motherships should keep their existing absurd cost. (They should be moved to a category with a similar cost as they do now)

[Eternaly_Lost]

No, please, dont do it, god no!  I dont think I could cope with more than one mothership coming at me, 30 - 40 HKs are quite bad enough.

You think that 30-40 are bad? You should try 30-40 under 900 Shield Bearers. I don't think you can take them without a planetary armor inhibitor, even with a full Spire Fleet of 10 DD and all the ships that comes with that many of those. They have an insane amount of firepower, but when you have 30 HK under almost 1000 Shield Bearers, it starts to become hard to figure out how to kill them.