And the same again goes for negotiation/catering costs. So all squad sizes in later encounters are completely determined by your own squad size at the very first Spire encounter – which in turn is completely determined by CAL. And similar to that, your own squad size progression when you ascend the Spire is also fixed. Spire Progression Modelįor a particular encounter in the Spire, enemy squad size always has the same ratio to your own squad size – just like in the tournaments. The tournament progression model connects it all together. ![]() And the same again goes for catering costs. So all squad sizes in later provinces are completely determined by your own squad size at the very first 1* province encounter – which in turn is completely determined by CAL. And similar to that, your own squad size progression is also fixed. Tournament Progression Modelįor a particular province number and stage (1*-6*) in the tournaments, enemy squad size always has the same ratio to your own squad size. Literally all size/amount parameters in the Spire and tournaments for any particular encounter are determined by this single number. if you have a higher CAL number, your squad sizes and catering costs for the same encounters will be higher in both Spire and the tournaments. This number represents city advancement level (duh!) the way the game sees it. relics boost, research, AW levels and expansions) and bakes all of them into a single CAL number. City Advancement Level ModelĬAL, or City Advancement Level Model takes different parameters that developers consider relevant for city development (e.g. ![]() So in the separate posts we will describe all 3 models in the diagram above. If it is somewhat confusing now, it’s OK, you’ll see how it all works together □ But actual base squad sizes are obviously different for Spire and the tournaments. And now we know that both Spire and new tournaments use the same calculation to figure out this city advancement level, and pin all other progressions to that single number. Base squad size was always effectively a representation of the city evolution, and had very little to do with fighting per se. Well, CAL is basically a generalization of that idea. Previously, we would pin Spire and new tournament progression to their respective own base squad sizes. ![]() The orange boxes in the diagram are observable model outputs, so the parameters that we actually want to figure out. You’ve seen those in the respective progression models before. The other ones (star # and province # for tournaments and encounter # for the Spire) are fairly self-explanatory. V – number of placed non-premium expansions (including initial 6).A– total number of AW levels (including currently upgrading).M– total number of unlocked mandatory tech items (research).maxB – maximum unlocked boost percentage for T1/T2/T3 goods.Those who read Spire Squad Size Model v5.0 will recognize these, but here I will list them again: So green boxes in the diagram above are observable model inputs. Probably □ The only new item here is City Advancement Level (CAL), but as you will see it is not exactly new. If you’ve seen previous posts on Spire and Tournament modeling, you already know what’s going on here. It looks complicated, but it really is not that bad. Tournament and Spire Requirements Modeling So a picture may save me a thousand words □ There are quite a few moving parts involved in the modeling, both on input and the output side. ![]() And while most of the completely different stuff will be related to the tournaments, Spire calculation are also impacted by this new development – albeit to a much smaller degree. In fact, if we peek under the hood, we will see that there is a significant overlap between new tournament calculations and the current Spire calculations. I won’t be focusing here on listing all the changes, but suffice to say that tournament calculations are completely different now from what we used to have for several years before that. Summer 2020 brought us some major changes to the tournament structure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |