Rank	Allocation
1st Place	30%
2nd Place	18%
3rd Place	12%
4th Place	9%
5th Place	7%
6th Place	6%
7th & 8th Place	5% each
9th & 10th Place	4% each

Rank

Allocation

1st Place

30%

2nd Place

18%

3rd Place

12%

4th Place

5th Place

6th Place

7th & 8th Place

5% each

9th & 10th Place

4% each

### Strategic Materials #### Military

Military units have unique properties: * **Deployment Only**: Cannot be converted back to tradeable form once deployed to an army * **Army Transfer**: Can be transferred between armies if located on adjacent hexes and of the same type and tier * **Essence Requirement**: All troop production requires Essence

#### Transport (Donkeys)

Essential for logistics: * **Food Cost Only**: Donkeys only cost food to produce (no $LORDS cost) * **Single Use**: Consumed after a single journey * **Required Transport**: Essential for moving materials around the world

### Special Materials #### **$LORDS** Currency

**$LORDS** is Blitz's economic backbone: * **Entry Fees**: Used for Warrior bracket entry fees * **Prize Pools**: Distributed as prizes to top performers * **No Donkey Production**: Not required for donkey production in Blitz #### Labor

Labor is a fundamental production material: * **Universal Production**: Can be produced by any Realm * **Construction Required**: Required to construct most buildings * **Resource Burning**: Produced by burning resources, with rarer resources yielding more labor * **Essence Integration**: May require Essence for some production #### Essence **Essence** is the key strategic resource in Blitz: * **Exploration Required**: Found by exploring the map and interacting with world structures * **Upgrade Requirement**: Required for all Realm upgrades and building construction * **Troop Production**: Essential for producing all troop types * **Strategic Value**: Control of Essence sources provides competitive advantage * **No Production**: Cannot be produced, only found through exploration ## Blitz-Specific Mechanics ### No Bridging Out * **Internal Only**: All materials remain within the Blitz game world * **No External Trade**: Cannot bridge materials out as ERC20 tokens * **Relic Bridging**: Players may only bridge relics into the game * **Scoring Focus**: Materials contribute to scoring rather than external value ### Simplified Resources * **9 Resources**: Simplified resource system for fast-paced gameplay * **No Fish**: Food simplified to just Wheat * **Balanced System**: Resources designed for 3-hour competitive games * **Strategic Choices**: Choose production based on immediate needs ### Increased Production Rates * **Faster Production**: All production rates increased for fast-paced gameplay * **Altered Recipes**: Production and building recipes modified for Blitz balance * **Efficient Scaling**: Optimized for 3-hour competitive sessions * **Strategic Timing**: Production timing crucial for competitive success ## Strategic Considerations ### Essence Management * **Early Acquisition**: Secure Essence sources quickly * **Exploration Priority**: Focus exploration on Essence discovery * **Strategic Control**: Control Essence Wells for steady production * **Upgrade Planning**: Plan upgrades around Essence availability ### Resource Optimization * **Production Efficiency**: Optimize production for maximum scoring * **Strategic Building**: Choose buildings based on immediate needs * **Resource Conversion**: Convert resources to scoring opportunities * **Balanced Development**: Balance all resource types for maximum efficiency ### Competitive Strategy * **Early Game**: Establish basic production quickly * **Mid Game**: Scale up production based on strategic needs * **Late Game**: Optimize for maximum scoring * **Resource Control**: Control key resource sources for competitive advantage Remember, in Blitz's fast-paced environment, efficient resource management is crucial for maximizing your Total Score and competitive performance! --- file: docs/pages/blitz/materials/storage.mdx meta: {} import { WeightTable } from "@/components/WeightTable"; import { formatNumberWithCommas } from "@/utils/formatting"; import { divideByPrecision } from "@/utils/resources"; import { CapacityConfig, ResourcesIds } from "@bibliothecadao/types"; import { ETERNUM_CONFIG } from "@/utils/config"; # 🏺 Storage Your available storage limits the amount of materials your Realm can hold. Each Realm begins with a base capacity of **{formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.Storehouse]/1000)} kg**. You'll need to construct storehouses to expand your storage capabilities. ## Weight and Storehouses ### Material Weights Materials have different weights that affect storage: DRAFTING NOTE: Review and add essence. ### Storehouses

Each storehouse adds {formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.Storehouse]/1000 )}kg of storage capacity. Lords must be careful not to exceed the storage capacity of their Realms, as any produced materials that cannot be stored will be permanently lost. ## World Structure Storage All world structures have set storage capacities **(that cannot be expanded through the use of storehouses)**. These capacities are as follows: DRAFTING NOTE: Review table. | Structure Type | Storage Capacity | | -------------- | ------------------------------------------------------------------------------------------------------------ | | Hyperstructure | {formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.HyperstructureStructure]/1000)} kg | | Essence Rift | {formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.EssenceRiftStructure]/1000)} kg | | Camp | {formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.CampStructure]/1000)} kg | --- file: docs/pages/blitz/materials/transfers-and-trade.mdx meta: {} import { importantNote } from "@/components/styles"; # 📜 Transfers **Blitz has no trade system.** Blitz focuses on individual competitive performance without economic trading mechanics. As such, there are no Banks, no P2P transfers, and no AMM/Orderbook through which Lords may trade. ## Transferring Materials Throughout the game, Lords will face the need to transfer materials from place to place around the world map, whether it be to their own Realms, or other structures like Hyperstructures, Essence Rifts and Camps. Lords have two primary options for initiating transfers: * **Detailed Transfer**: Players can use the comprehensive transfer menu accessible from the Trade tab. This allows transfers of multiple types of materials simultaneously, to any of their own structures on the map. ![Detailed Transfer](/gifs/transfer-all.gif) * **Quick Transfer**: Alternatively, Lords can swiftly transfer resources between their own structures using the resources sidebar, ideal for managing internal logistics and maintaining supply chains. ![Quick Transfer](/gifs/transfer-own.gif) ## The Donkey Network When a transfer is initiated, donkeys travel through the invisible and immutable donkey network. This is the key infrastructure upon which all material transport takes place. One donkey is capable of carrying up to 50 kg of materials, so the number of donkeys required for a transfer depends on the total weight of the materials being moved. Once a transfer is initiated, it cannot be cancelled, and the journey will take some time depending on the distance to the destination structure. Upon arrival, transferred materials and donkeys must be manually claimed via the 'Resource Arrivals' tab before they become available for use. ### Blitz Restrictions While troops can be transferred between Realms as normal, donkeys cannot be used to transport troops between Realms and Hyperstructures, Essence Rifts or Camps. This is to reduce the defensive advantage that a player can leverage by being able to move troops quickly into guard armies on these structures once claimed. All players must therefore deploy armies from Realms and move them across the map to contest these critical points. --- file: docs/pages/blitz/military/armies.mdx meta: {} import { RealmDefenseSlotsTable, WorldStructureDefenseSlotsTable } from "@/components/DefendingArmies"; import { ETERNUM_CONFIG } from "@/utils/config"; import { formatNumberWithCommas } from "@/utils/formatting"; # ⚔️ Armies Blitz World Map

Individual armies consist of a single troop type and tier. Each hex can host only one army, so Lords must carefully manage their positioning and engagement opportunities. Each Realm has a limited number of guard and field armies. The number of armies can be increased by upgrading the Realm level as explained in the [Realms](/blitz/realms/realm) section. Each military building constructed also increases total field armies by 1 (up to a maximum of **+{ETERNUM_CONFIG().troop.limit.explorerMaxPartyCount-4}**). Lords can deploy armies from the Military tab in the Local view. The maximum size of an army is **{formatNumberWithCommas(ETERNUM_CONFIG().troop.limit.explorerAndGuardMaxTroopCount)}**. ## Field Armies Field armies are used to project force on the world map, explore unknown territories, claim hyperstructures, defeat bandit forces, and engage in combat with other players. These armies are deployed onto one of the six hexes surrounding their parent Realm on the world map. If all hexes adjacent to the Realm are occupied, a field army cannot be deployed. Once deployed, these armies occupy a hex and traverse the world map based on the conditions outlined in the [World Map & Movement](/blitz/worldmap-movement/movement) section. Lords may direct their field armies to attack another army or structure on any adjacent hex by selecting the army with left-click, then right-clicking the target hex. When attacking a structure, the field army will engage in combat against any guard armies present.

Flow to create field army in the client

## Guard Armies Guard armies do not appear on the world map; instead, they occupy defense slots visible in the Military tab of the Local view. When in the World view, Lords can observe the defensive capabilities of any structure by selecting a hex and opening the Details tab. Unlike Realms, world structures have a static number of defence slots: DRAFTING NOTE: Review table.

Flow to create guard in the client

DRAFTING NOTE: Review reinforcement delay to 10 minutes. When attacked, guard armies are targeted sequentially starting from the outermost occupied slot. If a guard army is destroyed, the slot that it occupied becomes unavailable for reinforcement for **{Math.floor(ETERNUM_CONFIG().troop.limit.guardResurrectionDelay / 3600)} minutes**. Once all guard armies are defeated, the structure becomes vulnerable to being claimed by an adjacent field army. Lords can also direct their guard armies to launch attacks against adjacent hexes by selecting their structure on the worldmap, then right-clicking the target hex.

Attack field army with structure

--- file: docs/pages/blitz/military/damage.mdx meta: {} # 💥 Damage import { DamageCalculation } from "@/components/DamageCalculation"; ## Damage Overview Damage is defined as the number of casualties dealt by one army against the other in an instance of combat. When combat is initiated (i.e. one army attacks another), damage for both the attacking and defending army is calculated based on the number of troops, troop tier, stamina, and biome bonuses. Damage is then simultaneously inflicted by both sides. Battles can last multiple rounds (requiring multiple combat instances) depending on the relative strength and number of troops involved. Armies with higher-tier troops deal significantly more damage. However, careful management of troop numbers, stamina, and biome positioning can enable lower-tier armies to overcome stronger opponents. DRAFTING NOTE: Review the damage calculation. Likely to reduce damage for Blitz. --- file: docs/pages/blitz/military/raiding.mdx meta: {} # 💰 Raiding DRAFTING NOTE: Suggest we just remove raiding from Blitz, there's no point in it. --- file: docs/pages/blitz/military/stamina-and-biomes.mdx meta: {} import { Biomes } from "@/components/Biomes"; import { BiomeCombat } from "@/components/BiomeCombat"; # 🌪️ Stamina & Biomes ## Stamina Stamina is a vital resource governing the mobility and effectiveness of armies. Each deployed army possesses a maximum stamina value determined by its troop type and tier. Field armies expend stamina when moving, exploring unknown hexes, or engaging in combat against other armies and structures. Guard armies only expend stamina when attacking armies in hexes adjacent to their structure. During combat, stamina impacts army combat effectiveness: ### Attacking Army The attacking army is the army initiating an instance of combat. Attacks require a minimum of **30 stamina**, so armies with less than 30 stamina cannot initiate an attack. Each additional stamina point above this threshold grants a **1%** damage bonus, up to a maximum of **+30%** damage at **60 stamina**. Additional stamina spend is not optional, so attacking armies will use all available stamina up to a maximum of **60** for any one attack. If the attacking army destroys the defending army, they gain **+30 stamina**. ### Defending Army The defending army is the army being attacked in an instance of combat. Defending armies rely on having stamina available to maintain full combat effectiveness. When attacked, defending armies incur a **1%** damage reduction for every stamina point below **30**. For example, if an army is attacked while they have **10 stamina**, they would deal **-20%** damage to the attacking army. The maximum penalty is **-30%** damage if stamina is completely depleted. Successfully defending an attack does not deplete stamina. Lords should manage their armies' stamina carefully, ensuring they retain enough reserves to remain effective against unexpected attacks. ## Biomes (Combat Effects) The combat effectiveness of different troop types is impacted by the biome on which the defending army is located when the combat instance is started. Armies can gain either a combat advantage (**+30%** damage), disadvantage (**-30%** damage), or no effect, depending on their affinity with a particular biome. To summarise these combat modifiers for each troop type: ⚔️️ ️️️**Knights** excel in forests, leveraging cover and mobility, but suffer reduced effectiveness in deserts, beaches, and snow-covered regions where their heavy armour and weapons can make it difficult to move on the soft ground cover. Knights are equally advantaged, disadvantaged or not affected across all biome types. 🏹 **Crossbowmen** benefit from open seas and unstable terrains (such as beaches and snow), where they can remain static and make the most of their ranged capabilities. However, they will be disadvantaged in flat, open terrain with no cover or opportunity for concealment. Crossbowmen are the least advantaged, but also the least disadvantaged by biome modifiers of the three troop types. 🛡 ️**Paladins** dominate open, flat terrain where mounted units thrive, but are hindered in dense forests and on open water where their mounted capabilities are negated. They are the most advantaged, but also the most disadvantaged troop type. In combination with the biome effects on stamina use, Paladins are less versatile than other Knights or Crossbowmen, but are devastatingly effective in the right situations. **Note: The scorched biome applies +30% damage to all troop types, representing the additional casualties sustained from battling in an inhospitable environment.** --- file: docs/pages/blitz/military/troop-tiers.mdx meta: {} import { TroopTiers, TroopTierDamageStats } from "@/components/TroopTiers"; import { MaxStaminaTable } from "@/components/TroopMovementTable"; # 🛡️ Troop Tiers Troops come in three distinct tiers: T1, T2, and T3. Tier 1 (T1) represents basic troops, while T2 and T3 troops are more advanced, offering significantly increased combat strength and stamina. T1 troops have the lowest cost and can be produced in simple mode. Higher-tier troops require rare resources, essence and lower-tier troops as inputs: * Two T1 troops combine to produce one T2 troop * Two T2 troops combine to produce one T3 troop Each troop tier provides escalating advantages in terms of damage output and stamina. --- file: docs/pages/blitz/realms/buildings.mdx meta: {} import BuildingCard from "../../../components/BuildingCard"; import { formatNumberWithCommas } from "@/utils/formatting"; import { CapacityConfig } from "@bibliothecadao/types"; import { ETERNUM_CONFIG } from "@/utils/config"; # 🪓 Buildings ## Standard vs. Simple Blitz offers two building systems. Lords can switch between standard and simple building modes at any time by clicking the toggle at the top of the construction tab. ![Simple Mode Production](/gifs/simple-mode.gif) *Note: Some buildings only require labor to construct. Farms and Wood Mills have the same construction cost in both standard and simple building modes.* ### Standard Mode This is the classic building experience. Construction requires a combination of labor and a particular set of resources as building materials. Standard mode is more complex as it involves a greater variety and amount of materials in storage, however it is far more efficient overall. ### Simple Mode This mode allows players to utilize labor as the singular input for construction. Simple mode greatly improves accessibility and simplifies gameplay overall, but is much less efficient in both time and materials. ## Placement & Population ### Placement The construction tab can be accessed in the Local view. Buildings can be constructed on any buildable hex of a Realm, provided the owner has the requisite materials and population capacity. Buildable hexes are defined by the upgrade level (i.e. Settlement, City, Kingdom, or Empire) and are visible as hexes with patches of bare, prepared earth. ![Building Placement](/gifs/construction.gif) ### Population **Population** is the total population used to construct the current buildings on a Realm, while the **population capacity** is the maximum available population with which to construct buildings. Worker Huts can be built to increase population capacity, while all other buildings require population capacity to be available in order to construct. Lords must balance their construction to ensure there is enough population capacity available to construct their desired production buildings. ## Building Types ### The Keep All Realms start the game with a structure in the centre of the buildable hexes, known as the Keep. This structure represents the central point of governance of the Realm, and facilitates key functions such as Realm upgrades and labor production. This building cannot be destroyed and provides a baseline population capacity of 5. ### Resource Buildings There is a specific resource building for each of the 9 resources in Blitz, so Lords will require separate resource buildings if they wish to produce more than one type of resource.

### Economic Buildings These buildings define the utility of a Realm, including food production, donkey production, population capacity, and storage capacity. All of these buildings can be constructed in either standard or simple mode, but have varying costs and population requirements:

### Military Buildings Military buildings are essential for developing armies to defend territories and project might. There are three 'tiers' of each of the three troop types, but a different building is required to produce each troop tier. As such, there are a total of 9 military buildings in the game. Note: Only T1 troop buildings can be constructed in both standard and simple mode. T2 and T3 military buildings are only available for construction in standard mode.

### Same Building Cost Increase Building multiple buildings of the same type on a single Realm will cost progressively more each time. The cost increase is calculated using the following formula: ``` Cost = Base Cost + (Base Cost × 0.1 × (N-1)²) ``` Where: * **Base Cost** is the initial cost of the building (from the tables above) * **N** is the number of the same buildings already constructed For example, if you build a second building of the same type (N=2), the cost will be: ``` Cost = Base Cost + (Base Cost × 0.1 × (2-1)²) = Base Cost + (Base Cost × 0.1 × 1) = Base Cost × 1.1 ``` Note: Buildings need to be exactly the same type for this rule to apply. For example, building a Coal Mine after a Wood Mill (both being resource buildings) would not be subject to this cost increase. --- file: docs/pages/blitz/realms/realm.mdx meta: {} import { StartingResources, StructureType } from "@/components/StartingResources"; import { StartingMilitary } from "@/components/StartingMilitary"; import { RealmDefenseSlotsTable } from "@/components/DefendingArmies"; import { BuildableHexes } from "@/components/BuildableHexes"; import { RealmLeveling } from "@/components/RealmLeveling"; import { importantNote } from "@/components/styles"; # 🏰 Realms In Blitz, each Lord starts the game commanding three Realms, evenly spaced in a triangular formation. These Realms are functionally identical and are not related to the 8,000 Realm NFTs that are the basis of Eternum. They can produce any of the nine resources available in Blitz and are equally capable in all aspects of the game, limited only by the skill and strategy of their Lord.

## Realm Details ### Settling Realms are settled at the start of the 30-minute 'Settling Phase' prior to the start of the game. Lords who are registered to play are drawn at random from the pool and assigned spawn positions sequentially according to the settling algorithm. Once assigned a map position, Lords are required to confirm their participation in the session by initiating a 'Settle' transaction, which will place their three Realms in their drawn position. This must be done in the 30-minute Settling Phase to ensure presence and readiness to play the game. Lords who fail to confirm settling during this phase will not have their Realms placed and will forfeit participation in the session. Their allocated spawn position will remain empty throughout the game. ### Starting Resources DRAFTING NOTE: Insert table. Include starting military units as they all start in inventory (none deployed). ### Realm Progression Realms can grow from a Settlement into a City, then to a Kingdom, and finally an Empire. Each upgrade level unlocks additional buildable hexes and defensive army slots, allowing for the expansion of your economy and strengthening of your defences. Each progression requires specific materials, outlined in the table below: DRAFTING NOTE: Review RealmLeveling table, to be aligned with scope. Others should be the same as Eternum. --- file: docs/pages/blitz/worldmap-movement/movement.mdx meta: {} import TroopMovementTable from "@/components/TroopMovementTable"; import { BiomeStamina } from "@/components/BiomeStamina"; # 🧭 Movement & Exploration Troops Moving Across Eternum

## Stamina Stamina is expended whenever an army moves between hexes, explores previously unrevealed areas, or launches an attack against enemy forces. Each of these actions has a specific stamina cost, making strategic planning essential to maximizing an army's effectiveness. Armies regenerate stamina at a consistent rate of +60 stamina per Eternum Day. Each troop type possesses different maximum stamina capacities, outlined in the table below: Lords should remain cautious about fully depleting the stamina of their armies, as forces with low stamina may find themselves severely disadvantaged if attacked by enemy forces. ## Movement

Moving armies in the client

Armies in Eternum can move freely into any adjacent, unoccupied hex. A hex is considered occupied if it contains a Realm, another army, or a world structure such as a Hyperstructure, Camp, or essence Rift. Armies may also move to more distant hexes, provided there is a continuous path of adjacent, unoccupied hexes leading to the destination, and the army has sufficient stamina available for the entire journey. The amount of stamina consumed when moving into a hex depends on both the biome of that hex and the type of troops within the army. The table below details biome-specific stamina costs for each troop type: ## Exploring Exploring your surroundings is a necessary part of Blitz as it allows Lords to reveal paths to objectives, find valuable essence or other bonuses, and uncover beneficial world structures. When an army is positioned adjacent to an unexplored hex, Lords may choose to send that army forth to uncover what lies hidden. Exploring an unknown hex always costs 30 stamina and will reveal that hex to all Lords. If the newly explored hex contains a world structure, the exploring army will automatically be pushed back to the hex from which they started without any additional stamina penalty. During exploration, armies gather any valuables they encounter, receiving the goods directly into their inventory. The reward chances for any explored hex are as follows: DRAFTING NOTE: Require table of materials that can be found and their stack size. If an army becomes overencumbered, they will not be able to collect any materials found when exploring. Instead, the materials will remain on that tile and will be able to be collected by another army with enough capacity. Armies can return to a structure to offload the materials, or drop them to free up space. Note that any materials discarded in the field will be permanently lost (burned).

Explore in the client

## Troop Transfers Lords may transfer troops from one army to another, provided that they are on adjacent hexes, the same troop type, and the same tier. To transfer troops from one army to another, or to a structure, the player first needs to select its army on the worldmap using left-click, then right-click on the target and select the Transfer -> Transfer Troops tab. Transferring troops from one army to another with lower stamina makes no change to the stamina of either army. Transferring from an army with lower stamina to an army with higher stamina will reduce the higher-stamina army to equal that of the lower stamina army.

Transfer troops in the client

--- file: docs/pages/blitz/worldmap-movement/worldmap.mdx meta: {} import { importantNote } from "@/components/styles"; # 🗺️ The World Map Eternum World Map

## An Unexplored World At the beginning of each Blitz game, the world lies largely unexplored. The only exceptions are the settled Realms and the array of Hyperstructures which can be seen in the World view, arranged in expanding rings around the center of the map. The six hexes adjacent to these structures are also revealed, but beyond these instances, the world remains cloaked by the mist, waiting for ambitious Lords to send forth their armies to explore. Once a hex is explored, the state of the hex (i.e. the biome and whether it contains a world structure) is permanently revealed to all Lords. ## Map Layout ### Hyperstructure Positioning The number of registered Lords for a game of Blitz determines the size of the map and the number of Hyperstructures available for Lords to compete over. A single Hyperstructure marks the center of the map, around which other concentric Hyperstructure 'rings' are spawned every 18 hexes until all players are accommodated. The number of Hyperstructure rings is determined by: ``` r = √(P/6) ``` Where: * **P** is the number of players (Lords) registered to play in the session * **r** is the number of Hyperstructure rings * If **r** is not an integer, then it is rounded up to the nearest integer The number of Hyperstructures in a ring is determined by: ``` H_r = 6r ``` Where: * **H_r** is the number of Hyperstructures in ring **r** * **r** is the ring number (1, 2, 3, etc.) ### Realm Positioning Once the size of the map and the number of Hyperstructures are determined, player positions are determined within the bounds of the Hyperstructure rings. While the order in which players are placed is randomised, the positioning is sequential and follows a rotational pattern to distribute Lords as evenly as possible and attempt to ensure equal opportunity in accessing the Hyperstructure objectives. The map structure and placement sequence is visualised below: DRAFTING NOTE: Insert gif of settling algorithm. The Realms of each participating Lord are positioned six hexes apart in a triangle formation. Each Realm is also located within eight hexes of a Hyperstructure, and eight hexes from the nearest Realm belonging to another Lord (assuming all available player positions are filled).

⚠️ IMPORTANT NOTE

There is no immunity period in Blitz. All Realms are able to be attacked and claimed from the moment the game begins.

## Biomes Each hex is assigned one of 16 biome types, each with unique aesthetics and strategic implications. These biomes are procedurally generated across the world map following specific rules that dictate their distribution, with certain biomes naturally occurring more or less frequently than others. Biomes impact both combat effectiveness and troop movement. Each troop type—Knights, Crossbowmen, and Paladins—can potentially be advantaged or disadvantaged in battle depending on the biome in which combat takes place; this is explained in more detail in the [Military](/blitz/military/stamina-and-biomes) section. Additionally, biomes have the potential to enhance or impede army maneuvers, as the various biomes impact the stamina consumption of each troop type differently as they move between hexes—this is explained further in the [Movement & Exploration](/blitz/worldmap-movement/movement) section below. --- file: docs/pages/eternum/military/armies.mdx meta: {} import { RealmDefenseSlotsTable, WorldStructureDefenseSlotsTable } from "@/components/DefendingArmies"; import { ETERNUM_CONFIG } from "@/utils/config"; import { formatNumberWithCommas } from "@/utils/formatting"; # ⚔️ Armies Eternum World Map

In Season 1, individual armies consist of a single troop type and tier—streamlining combat strategy and simplifying interactions on the world map. Each hex can host only one army, so Lords must carefully manage their positioning and engagement opportunities. Each Realm and Village has a limited number of guard and field armies The number of armies can be increased by upgrading the Realm / Village level as explained in the [Realms](/eternum/realm-and-villages/realm) section. Each military building constructed on a Realm or Village also increases total field armies by 1 (up to a maximum of **+{ETERNUM_CONFIG().troop.limit.explorerMaxPartyCount-4}**). Lords can deploy armies from the Military tab in the Local view. The maximum size of an army is **{formatNumberWithCommas(ETERNUM_CONFIG().troop.limit.explorerAndGuardMaxTroopCount)}**. ### Field Armies Field armies are used to project force on the world map, explore unknown territories, patrol borders, defend key areas, or march against your enemies. These armies are deployed onto one of the six hexes surrounding their parent Realm on the world map. If all hexes adjacent to the Realm are occupied, a field army cannot be deployed. Once deployed, these armies occupy a hex and traverse the world map based on the conditions outlined in the World Map & Movement section. Lords may direct their field armies to attack another army or structure on any adjacent hex by selecting the army with left-click, then right-clicking the target hex. When attacking a structure, the field army will engage in combat against any guard armies present.

Flow to create field army in the client

### Guard Armies Guard armies do not appear on the world map; instead, they occupy defense slots visible in the Military tab of the Local view. When in the World view, Lords can observe the defensive capabilities of any structure by selecting a hex and opening up the Details tab. Unlike Realms and Villages, world structures have a static number of defence slots:

Flow to create guard in the client

When attacked, guard armies are targeted sequentially starting from the outermost occupied slot. If a guard army is destroyed, the slot that it occupied becomes unavailable for reinforcement for **{Math.floor(ETERNUM_CONFIG().troop.limit.guardResurrectionDelay / 3600)} hours**. Once all guard armies are defeated, the structure becomes vulnerable to being claimed by an adjacent field army (with the exception of Villages, which cannot be claimed). Lords can also direct their guard armies to launch attacks against adjacent hexes by selecting their structure on the worldmap, then right-clicking the target hex.

Attack field army with structure

--- file: docs/pages/eternum/military/damage.mdx meta: {} # 💥 Damage import { DamageCalculation } from "@/components/DamageCalculation"; ## Damage Overview Damage is defined as the number of casualties dealt by one army against the other in an instance of combat. When combat is initiated (i.e. one army attacks another), damage for both the attacking and defending army is calculated based on the number of troops, troop tier, stamina, and biome bonuses. Damage is then simultaneously inflicted by both sides. Battles can last multiple rounds (requiring multiple combat instances) depending on the relative strength and number of troops involved. Armies with higher-tier troops deal significantly more damage. However, careful management of troop numbers, stamina, and biome positioning can enable lower-tier armies to overcome stronger opponents. --- file: docs/pages/eternum/military/raiding.mdx meta: {} import { ETERNUM_CONFIG } from "@/utils/config"; import { resource } from "@/components/styles"; import { RaidableResources } from "@/components/RaidableResources"; import { importantNote } from "@/components/styles"; # 💰 Raiding Raiding allows field armies to attempt theft of valuable resources directly from an adjacent target structure, without first having to battle through enemy guard armies. Lords can direct their armies to complete this action by selecting the 'raid' action when attacking an enemy structure. ![Raiding interface showing an army preparing to raid a structure](/screenshots/raiding.png) ## Raid Requirements Before attempting a raid, your army must meet the following requirements: * Have at least **{ETERNUM_CONFIG().troop.stamina.staminaAttackReq}** stamina * Be adjacent to the target structure * Structure must contain raidable resources ## Raidable Materials Raidable materials are stolen based on rarity, with the most valuable taken first. Rarer materials are prioritized during raids:

⚠️ IMPORTANT NOTE

No materials are safe from pillagers, $LORDS tokens can be raided as well

## Raid Success The success chance of a raid is determined by the following conditions: | Condition | Raid Success Chance | | -------------------------------------------------------------------------- | --------------------------------------------- | | Raiding army's total damage \< **50%** of combined guard armies' damage | **0%** | | Raiding army's total damage > **200%** of combined guard armies' damage | **100%** | | Raiding army's damage between **50%** and **200%** of guard armies' damage | Scales proportionally from **0%** to **100%** | | No guard armies present | **100%** (automatic success) | Upon a successful raid, resources are transferred directly to the raiding army's inventory up to its carrying capacity. It is only possible to steal food, resources, and ancient fragments from a raid, tokens such as $LORDS and $STRK can only be stolen from another player by claiming a Realm into which tokens have been bridged or transferred. ## Damage in Raids At the conclusion of a raid, regardless of whether it was successful or not, damage is calculated for both the raiding army and the guard armies. This damage is significantly reduced by a raid damage modifier, simulating the concept of a pillaging and looting event as opposed to a full-scale battle. The raid damage modifier reduces damage to **{ETERNUM_CONFIG().troop.damage.damageRaidPercentNum/100}%** of that which would be applied in an attack action. Damage from a raiding action is calculated according to the following rules: * The raiding army troop total is split evenly across each guard army. * A standard combat damage calculation is then applied to each combat instance. * Each damage number is multiplied by the raid damage modifier before casualties are applied. ### Example: Consider **1000** raiders attacking a structure with two occupied guard slots: * Slot 1: **400** troops * Slot 2: **600** troops The raiding army is split into two groups of **500** troops, each attacking one guard slot. Assume that the damage calculations result in the following: * Raiding army deals **180** damage to Slot 1 and **150** damage to Slot 2 = **330** total damage * Guard armies deal **120** damage from Slot 1 and **200** damage from Slot 2 = **320** total damage. Applying the raid damage modifier, actual losses become: * Guards: Slot 1 loses **36** troops (**{ETERNUM_CONFIG().troop.damage.damageRaidPercentNum/100}%** of 180), Slot 2 loses **30** troops (**{ETERNUM_CONFIG().troop.damage.damageRaidPercentNum/100}%** of 150). * Raiders: Lose **64** troops total (**{ETERNUM_CONFIG().troop.damage.damageRaidPercentNum/100}%** of 320). ## Raid Outcomes After a raid attempt, one of two outcomes will occur: 1. **Successful Raid** * Resources are transferred to your army's inventory * Resources are limited by your army's carrying capacity * Both armies suffer reduced casualties (**{ETERNUM_CONFIG().troop.damage.damageRaidPercentNum/100}%** of normal combat damage) * Your army's stamina is reduced by **{ETERNUM_CONFIG().troop.stamina.staminaAttackReq}** 2. **Failed Raid** * No resources are stolen * Both armies still suffer reduced casualties (**{ETERNUM_CONFIG().troop.damage.damageRaidPercentNum/100}%** of normal combat damage) * Your army's stamina is still reduced by **{ETERNUM_CONFIG().troop.stamina.staminaAttackReq}** The outcome is determined by comparing your army's total damage output against the combined damage output of all guard armies present. If no guard armies are present, the raid automatically succeeds. --- file: docs/pages/eternum/military/stamina-and-biomes.mdx meta: {} import { BiomeCombat } from "@/components/BiomeCombat"; # ⚡ Stamina & Biome Effects ## Stamina Stamina is a vital resource governing the mobility and effectiveness of armies. Each deployed army possesses a maximum stamina value determined by its troop type and tier as explained above. Field armies expend stamina when moving, exploring unknown hexes, or engaging in combat against other armies and structures. Guard armies only expend stamina when attacking armies in hexes adjacent to their structure. During combat, stamina impacts army combat effectiveness: ### Attacking Army (the army initiating combat) Attacks require a minimum of **30 stamina**, so armies with less than 30 stamina cannot initiate an attack. Each additional stamina point above this threshold grants a **1%** damage bonus, up to a maximum of **+30%** damage at **60 stamina**. Additional stamina spend is not optional, so attacking armies will use all available stamina up to a maximum of **60** for any one attack. If the attacking army destroys the defending army, they gain **+30 stamina**. ### Defending Army (the army being attacked) Defending armies rely on having stamina available to maintain full combat effectiveness. When attacked, defending armies incur a **1%** damage reduction for every stamina point below **30**. For example, if an army is attacked while they have **10 stamina**, they would deal **-20%** damage to the attacking army. The maximum penalty is **-30%** damage if stamina is completely depleted. Successfully defending an attack does not deplete stamina. Lords should manage their armies' stamina carefully, ensuring they retain enough reserves to remain effective against unexpected attacks. ## Biomes (Combat Effects) The combat effectiveness of different troop types is impacted by the biome on which the defending army is located when engaging in battle. Armies can gain either a combat advantage (**+30%** damage), disadvantage (**-30%** damage), or no effect, depending on their affinity with a particular biome. To summarise these combat modifiers for each troop type: ⚔️️ ️️️**Knights** excel in forests, leveraging cover and mobility, but suffer reduced effectiveness in deserts, beaches, and snow-covered regions where their heavy armour and weapons can make it difficult to move on the soft ground cover. Knights are equally advantaged, disadvantaged or not affected across all biome types. 🏹 **Crossbowmen** benefit from open seas and unstable terrains (such as beaches and snow), where they can remain static and make the most of their ranged capabilities. However, they will be disadvantaged in flat, open terrain with no cover or opportunity for concealment. Crossbowmen are the least advantaged, but also the least disadvantaged by biome modifiers of the three troop types. 🛡 ️**Paladins** dominate open, flat terrain where mounted units thrive, but are hindered in dense forests and on open water where their mounted capabilities are negated. They are the most advantaged, but also the most disadvantaged troop type. In combination with the biome effects on stamina use, Paladins are less versatile than other Knights or Crossbowmen, but are devastatingly effective in the right situations. **Note: The scorched biome applies +30% damage to all troop types, representing the additional casualties sustained from battling in an inhospitable environment.** --- file: docs/pages/eternum/military/troop-tiers.mdx meta: {} import { TroopTiers, TroopTierDamageStats } from "@/components/TroopTiers"; import { MaxStaminaTable } from "@/components/TroopMovementTable"; # 🛡️ Troop Tiers Troops in Eternum come in three distinct tiers: T1, T2, and T3. Tier 1 (T1) represents basic troops, while T2 and T3 troops are more advanced, offering significantly increased combat strength and stamina. Higher-tier troops are produced by constructing specialized buildings that require rare resources and lower-tier troops as inputs: * Two T1 troops combine to produce one T2 troop * Two T2 troops combine to produce one T3 troop Each troop tier provides escalating advantages in terms of damage output and stamina. --- file: docs/pages/eternum/realm-and-villages/buildings.mdx meta: {} import BuildingCard from "../../../components/BuildingCard"; import { formatNumberWithCommas } from "@/utils/formatting"; import { CapacityConfig } from "@bibliothecadao/types"; import { ETERNUM_CONFIG } from "@/utils/config"; # 🪓 Buildings ## Standard vs. Simple Season 1 offers two building systems. Lords can switch between standard and simple building modes at any time by clicking the toggle at the top of the construction tab. ![Simple Mode Production](/gifs/simple-mode.gif) Note: Some buildings only require food to construct. Farms, Fishing Villages and Resource Buildings have the same construction cost in both standard and simple building modes. ### Standard Mode This is the classic Eternum experience. Construction requires a combination of labor and a particular set of resources as building materials. Standard mode is more complex as it involves a greater number of materials in storage, however it is far more efficient overall. This building mode is generally designed for those with multiple Realms and/or Villages working with economies of scale. ### Simple Mode This mode allows players to utilize Labor, a new material for Season 1, as the singular input for construction. Simple mode greatly improves accessibility and simplifies gameplay overall, but is much less efficient in both time and materials. This would be the preferred system for players with smaller holdings and limited access to a variety of resources. ## Placement & Population ### Placement The construction tab can be accessed in the Local view. Buildings can be constructed on any buildable hex of a Realm or Village, provided the owner has the requisite materials and population capacity. Buildable hexes are defined by the upgrade level (i.e. Settlement, City, Kingdom, or Empire) and are visible as hexes with patches of bare, prepared earth. Most buildings can be constructed in either simple or standard mode, which toggled at the top of the construction tab. ![Building Placement](/gifs/construction.gif) ### Population Population is the total population utilised by the currently constructed production buildings on a Realm or Village, while the population capacity is the maximum available population with which to construct production buildings. Worker Huts can be built to increase population capacity, while all other buildings require population capacity to be available in order to construct. Lords must balance their construction to ensure there is enough population capacity available to construct their desired production buildings. ## Building Types ### The Keep Settling any Realm or Village will automatically construct a structure in the centre of your buildable hexes, known as the Keep. This structure represents your seat of power and the central point of governance, and facilitates key functions such as Realm/Village upgrades and Labor production. This building cannot be destroyed and provides a baseline population capacity of 5. ### Resource Buildings There is a specific resource building for each of the 22 resources in the game, so Lords will require separate resource buildings if they wish to produce more than one type of resource. These buildings only require food to construct and have the same requirements in simple and standard mode.

### Economic Buildings These buildings define the utility of a Realm or Village, including food production, donkey production, population capacity, and storage capacity. All of these buildings can be constructed in either standard or simple mode, but have varying costs and population requirements: \[economic building table, including population cost / population capacity increase (Worker Hut) / storage capacity increase (Storehouse)]

### Military Buildings Your military buildings are essential for training up armies to defend your territories and project your might. There are three 'tiers' of each of the three troop types, but a different building is required to produce each troop tier. As such, there are a total of 9 military buildings in the game. Note: Only T1 troop buildings can be constructed in both standard and simple mode. T2 and T3 military buildings are only available for construction in standard mode.

### Same Building Cost Increase Building multiple buildings of the same type will cost progressively more each time. The cost increase is calculated using the following formula: ``` Cost = Base Cost + (Base Cost × 0.5 × (N-1)²) ``` Where: * **Base Cost** is the initial cost of the building (from the tables above) * **N** is the number of the same buildings already constructed For example, if you build a second building of the same type (N=2), the cost will be: ``` Cost = Base Cost + (Base Cost × 0.5 × (2-1)²) = Base Cost + (Base Cost × 0.5 × 1) = Base Cost × 1.5 ``` Note: Buildings need to be exactly the same type for this rule to apply. For example, building a Stone Quarry after a Lumber Camp (both being resource buildings) would not be subject to this cost increase. --- file: docs/pages/eternum/realm-and-villages/realm.mdx meta: {} import { StartingResources, StructureType } from "@/components/StartingResources"; import { StartingMilitary } from "@/components/StartingMilitary"; import { RealmDefenseSlotsTable } from "@/components/DefendingArmies"; import { BuildableHexes } from "@/components/BuildableHexes"; import { RealmLeveling } from "@/components/RealmLeveling"; import { importantNote } from "@/components/styles"; # 🏰 Realms The 8,000 Realms are the foundation of Eternum, each uniquely destined to shape the fate of this vast continent. As limited and irreplaceable strongholds, these Realms serve as the primary playing pieces of the game. Each Realm settled in Eternum can produce between one and seven different resources, depending on the metadata of the original Realm NFT and its associated Season Pass. This metadata also aligns each Realm to one of sixteen ancient Orders, however the meaning of this alignment has been lost to the mist… for now.

### Settling To settle a Realm, Lords must first burn a Season Pass, which gives them the ability to select the location of their homeland from an array of locations scattered across the map. For Season 1, there is a seven-day settling period before the game starts, allowing players to organise and position themselves before a move can be made. Realms can still be settled after this period, however the earlier in the season that Lords can establish their holdings, the greater their production potential and overall experience. Settling a Realm

![Realm Settling Screen](/screenshots/settling.png)

⚠️ IMPORTANT NOTE

When the game starts, all structures are immune to attacks and raids for 24 hours. Once the first day of gameplay has concluded, there are no more instances of immunity, all Realms and Villages settling into the game after this time will need to rely on their starting defences and consider their starting locations carefully. Lords entering the game after the immunity period are advised to make use of the spectator mode to scout for relatively safe spawning locations before initiating a settling transaction.

### Starting Resources ### Starting Military Each Realm starts with the majority of the starting troops deployed to the first defense slot as a guard army. A small number of troops remain within the Realm's storage to be deployed as a field army should the Realm Lord wish to explore beyond their walls. Troops can be transferred from the guard army to the field army using the troop transfer process explained in the [Movement & Exploration](/eternum/worldmap-movement/movement) section. The specific type of military unit is determined by your Realm's biome, and is strategically chosen to have a combat advantage in that particular environment. ### Realm Progression Realms can grow from a Settlement into a City, then to a Kingdom, and finally an Empire. Each upgrade level unlocks additional buildable hexes and defensive army slots, allowing for the expansion of your economy and strengthening of your defences. Each progression requires specific materials, outlined in the table below: --- file: docs/pages/eternum/realm-and-villages/villages.mdx meta: {} import ResourceProbability from "@/components/ResourceProbability"; import { StartingResources, StructureType } from "@/components/StartingResources"; import { StartingMilitary } from "@/components/StartingMilitary"; # 🛖 Villages Beyond the limited number of sacred Realms lies the humble yet vital Village—small settlements established on hexes that surround a settled Realm. These modest outposts offer a more accessible entry into Eternum, serving as gateways for new settlers and loyal subjects. Additionally, they can act as supplementary playing pieces for more serious players who wish to maximise their potential. Each settled Realm can have up to six Villages surrounding it, allowing up to 48,000 Villages in Season 1!

### Settling Villages are settled by minting a Village token. Aspiring settlers can choose to place their Village next to a specific Realm by entering the asset ID of a settled Realm, or let fate guide them to a random Realm's outskirts - either way, the Realm that they spawn adjacent to becomes that Village's 'parent' Realm. Players may also choose which of the six possible hexes they spawn on by selecting a compass direction. Village Settling Screen

*Three villages settled next to a realm* ### Starting Resources ### Starting Military Each Village starts with the majority of the starting troops deployed to the first defense slot as a guard army. A small number of troops remain within the Village’s storage to be deployed as a field army should the Village Lord wish to explore beyond their walls. Troops can be transferred from the guard army to the field army using the troop transfer process explained in the [Movement & Exploration](/eternum/worldmap-movement/movement) section. The specific type of military unit is determined by your Village's biome, and is strategically chosen to have a combat advantage in that particular environment. ### Resource Roll When minting a Village, a random number is rolled to determine the single resource that it can produce. ### Limitations Villages produce food, resources, troops, donkeys, and labor at 50% the rate of Realms. They can receive and purchase food, labor, donkeys and resources without restriction, but can only receive troops from their parent Realm - this limitation is in place to prevent players from spawning a Village on their rival's Realm and 'teleporting' troops there by using the donkey network. ### Village Progression Villages have a limited progression path and may only upgrade once from Settlement to City. The cost and benefits of this progression is the same as that of a Realm. --- file: docs/pages/eternum/realm-and-villages/wonders.mdx meta: { "title": "Wonders", "description": "The Wonders of Realms Eternum" } # ✨ Wonders Of the 8,000 Realms, 50 are distinguished by the presence of Wonders—unique and magical places of power that confer special benefits, making them highly desirable playing pieces that may put a target on their owner's back. In Season 1, Wonder Realms grant a 20% production bonus not only to themselves but also to all Realms and Villages located within 12 tiles. This bonus means the Wonder Realm itself, the surrounding Realms (up to six), and all Villages settled around these seven Realms produce food, resources, troops, labor, and donkeys at 120% efficiency compared to standard Realms, using the same inputs. Key Notes: * Production rates are not increased by this bonus, more is produced overall for the same amount of input. * These bonuses do not stack. There is no benefit to settling multiple wonders in a limited range.

--- file: docs/pages/eternum/resources/automation.mdx meta: {} # Resource Automation Resource automation allows players to set up continuous production processes and automated transfers within their realms and between entities. This system helps manage resource generation and distribution efficiently without constant manual intervention. ## Overview The automation system works by processing two types of "orders" that you define: 1. **Production Orders**: Automate resource production within your realms 2. **Transfer Orders**: Automate resource transfers between your entities (realms, villages, hyperstructures, etc.) Both types of orders specify what you want to automate, the method or conditions, target amounts or schedules, and priorities. **Key Features:** * **Order-Based**: Define specific production and transfer tasks. * **Priority System**: Control the sequence of execution for multiple orders. * **Multiple Automation Types**: Choose between production automation and transfer automation. * **Entity-Specific**: Automation is configured on a per-entity basis. * **Browser Dependent**: Automation processes run in your browser; the game tab must remain open for automation to function. * **10-Minute Cycles**: All automation is processed every 10 minutes. ## How It Works The automation system periodically checks and processes active orders for each entity. 1. **Processing Interval**: All orders are evaluated every 10 minutes. 2. **Order Prioritization**: For each entity, orders are sorted by their priority number (1 being the highest). 3. **Pause Functionality**: You can pause all automation for any entity, which will skip all orders for that entity. 4. **Order Processing**: The system processes different order types: ### Production Order Processing * **Balance Check**: Before executing, the system checks if the realm has sufficient input resources or labor. * **Recipe-Based Production**: Production follows predefined recipes from the game's configuration. * **Cycle Calculation**: Determines the maximum number of production cycles possible based on available inputs. * **Transaction**: If conditions are met, a blockchain transaction is initiated to perform the production. ### Transfer Order Processing * **Schedule Check**: For recurring transfers, checks if enough time has passed since the last transfer. * **Threshold Check**: For conditional transfers, checks if resource levels meet the specified conditions. * **Resource Availability**: Verifies the source entity has sufficient resources for the transfer. * **Transaction**: If conditions are met, initiates a transfer transaction between entities. ## Production Types There are three types of production automation: 1. **Standard (Resource-to-Resource)**: * Converts one or more input resources into a different output resource. * Example: Using Wood and Stone to produce Tools. 2. **Simple (Labor-to-Resource)**: * Utilizes Labor from the realm to produce a specific resource. * Example: Using Labor to harvest Food. 3. **Resource-to-Labor**: * Converts a specified resource into Labor for the realm. * Example: Burning Food to generate Labor. ## Production Order Modes Production orders can operate in two different modes: 1. **Produce Once**: * Produces resources until the target amount is reached, then stops. * Shows progress as "Produced / Target" (e.g., "1,500 / 5,000"). * Can be set to "Infinite" to produce continuously without a limit. 2. **Maintain Balance**: * Keeps resource balance at the target level. * Production triggers when balance drops below target minus buffer percentage. * Example: Target 10,000 with 10% buffer = production starts when balance drops below 9,000. * Useful for maintaining steady resource levels. ## Transfer Types Transfer automation allows you to automatically move resources between your entities. There are three transfer modes: 1. **Recurring Transfers**: * Transfers resources at regular intervals. * Minimum interval: 10 minutes (due to automation cycle). * Example: Transfer 1,000 Food from Realm A to Village B every 2 hours. * *\[GIF placeholder: Setting up a recurring transfer]* 2. **Maintain Stock Transfers**: * Transfers when the destination entity falls below a threshold. * Example: Transfer 500 Wood to Village when it has less than 1,000 Wood. * Helps keep important entities well-supplied. * *\[GIF placeholder: Setting up a maintain stock transfer]* 3. **Depletion Transfers**: * Transfers when the source entity exceeds a threshold. * Example: Transfer excess Stone when Realm has more than 5,000 Stone. * Prevents resource overflow and distributes surplus. * *\[GIF placeholder: Setting up a depletion transfer]* ## Managing Automation Orders (UI) You can manage automation orders through the "Automation" tab within any entity's interface, or through the global "All Automations" view. ### Production Automation Production automation is managed within individual realm interfaces. *\[GIF placeholder: Navigating to realm automation tab]* #### Adding a New Production Order 1. Click the "Add New Automation" button. 2. Configure the following: * **Order Mode**: * `Produce Once`: Produce up to target amount then stop * `Maintain Balance`: Keep resource balance at target level * **Production Type**: * `Standard (Resource-based)` * `Simple (Labor-based)` * `Resource to Labor` * **Priority (1-9)**: * Set the execution priority. `1` is the highest priority, `9` is the lowest. * **Resource to Produce / Resource Input for Labor**: * Select the resource you want to produce or consume. * The UI shows required input resources for Resource-to-Resource recipes. * **Target Amount**: * For "Produce Once": Set total quantity to produce, or check "Infinite" for continuous production. * For "Maintain Balance": Set the balance level to maintain. * **Buffer Percentage** (Maintain Balance only): * Production starts when balance drops below target minus buffer percentage. 3. Click "Add Automation". *\[GIF placeholder: Creating a production automation order]* ### Transfer Automation Transfer automation allows you to move resources between any of your entities. *\[GIF placeholder: Accessing transfer automation]* #### Adding a New Transfer Order 1. **Select Source Entity**: * Choose entity type (Your Realms, Your Villages, etc.) * Search and select the specific source entity 2. **Configure Transfer**: * **Transfer Mode**: * `Recurring`: Transfer at regular intervals * `Maintain Stock`: Transfer when destination is low * `Depletion Transfer`: Transfer when source is high * **Destination Entity**: * Choose entity type and select specific destination * **Resources to Transfer**: * Add multiple resources with specific amounts * **Schedule/Conditions**: * For Recurring: Set interval in minutes (minimum 10 minutes) * For conditional transfers: Set threshold amounts 3. Click "Add Transfer Automation". *\[GIF placeholder: Creating a transfer automation order]* #### Transfer Interval Guidelines * **Minimum Interval**: 10 minutes (matches automation processing cycle) * **Common Intervals**: * 10m, 30m, 1h, 2h, 6h, 24h (preset buttons available) * Custom intervals can be set in minutes * **Effective Timing**: Transfers occur when automation cycles align with your interval ### Viewing and Managing Orders #### Individual Entity View Each entity shows its automation orders in a table with: * **Priority**: Order execution priority * **Mode**: "Once", "Maintain", or transfer mode ("Recurring", "Stock", "Depletion") * **Resource**: Visual representation of resource flow * **Target/Balance**: Target amounts or transfer schedules * **Produced**: Amount produced (production orders only) * **Type**: Order type (production or transfer) * **Actions**: Remove button *\[GIF placeholder: Viewing automation orders in entity interface]* #### Global Automation View The "All Automations" view shows orders from all entities: * **Realm Filter**: Filter by specific realm or view all * **Order Status**: Visual indicators for completed, paused, or active orders * **Countdown Timer**: Shows time until next automation cycle * **Bulk Actions**: Pause/resume or delete orders *\[GIF placeholder: Using the global automation view]* ### Pausing Automation You can pause automation at different levels: 1. **Individual Entity**: Pause all automation for a specific entity 2. **Individual Order**: Remove specific orders 3. **Global Control**: Manage all orders from the global view *\[GIF placeholder: Pausing and resuming automation]* ## Important Considerations ### General Requirements * **Browser Must Be Open**: Automation processing occurs in your browser. If you close the game tab or your browser, automation will stop. * **10-Minute Processing Cycle**: All automation is processed every 10 minutes. This affects timing for all orders. * **Transaction Costs**: Each successful automation cycle that results in production or transfer will involve a blockchain transaction, which incurs network transaction fees. * **Processing Time**: Due to the 10-minute processing interval and potential network conditions, there might be a delay before an order is executed or its results are visible. ### Production Automation Considerations * **Resource Availability**: Production orders will only execute if the required input resources are available in the realm at the time of processing. * **Recipe Dependencies**: Production follows predefined game recipes. You cannot produce resources that don't have valid recipes. * **Storage Limits**: Produced resources will increase your realm's balance and may cause resource loss if storage is full. ### Transfer Automation Considerations * **Entity Ownership**: You can only set up transfers between entities you own. * **Transfer Timing**: * Minimum effective interval is 10 minutes due to processing cycle * Intervals shorter than 10 minutes will effectively transfer every 10 minutes * Non-10-minute multiples may have irregular timing based on when transfers align with processing cycles * **Resource Availability**: Transfers will only execute if the source entity has sufficient resources at processing time. * **Multiple Resources**: You can transfer multiple different resources in a single transfer order. * **Conditional Logic**: Maintain Stock and Depletion transfers check conditions each cycle and only transfer when thresholds are met. ### Best Practices 1. **Start Simple**: Begin with basic production orders or simple recurring transfers to understand the system. 2. **Monitor Initially**: Watch your first few automation cycles to ensure orders work as expected. 3. **Use Priorities**: Set appropriate priorities when you have multiple orders to control execution sequence. 4. **Plan for Delays**: Account for the 10-minute processing cycle when planning time-sensitive operations. 5. **Check Resource Flows**: Regularly verify that your automated transfers are maintaining desired resource distributions. *\[GIF placeholder: Monitoring automation performance and adjusting orders]* --- file: docs/pages/eternum/resources/bridging.mdx meta: {} import { EfficiencyTable } from "@/components/EfficienyTable"; # 🌀 Bridging (Portals) Portals provide Lords with the ability to bridge materials into and out of Eternum, connecting the in-game economy with the Starknet infrastructure layer. Portals are mysterious and unstable devices, so they tend to burn up most of the materials sent through. However, there is evidence that the power of the Hyperstructures can increase the stability of Portals throughout Eternum. As Lords manage to reestablish these mighty structures throughout the land, the efficiency of bridging in and out of Eternum improves for all. Each Realm comes equipped with a Portal. Realm Lords are able to bridge materials both into and out of their Realms directly. Villages, however, have more limited bridging capabilities—they can bridge materials out of Eternum, but not in. This is in line with their existing restrictions on receiving troops from external sources. They are also limited to utilizing the Portal belonging to their parent Realm, for which the Realm owner collects a 5% fee on all materials and tokens bridged out of the game. --- file: docs/pages/eternum/resources/production.mdx meta: {} import { StandardTroopProduction, SimpleTroopProduction, SimpleResourceProduction, StandardResourceProduction, LaborProduction, DonkeyProduction, } from "@/components/ResourceProduction"; # ⚒️ Production ## Standard vs. Simple As is the case for building construction, Lords can choose between standard and simple production systems when deciding how they wish to produce their materials. This can be done by selecting the appropriate panel when making an order in the production screen. ![Simple Mode Production](/gifs/labor-production.gif) *Note: Production works a little differently in Season 1 compared to Season 0. Instead of streaming resources unit by unit and producing an output for as long as you have the requisite inputs, Lords must now commit the full material requirements to the production order upfront. The output is then produced at a given rate per second.* ### Standard Mode The classic Eternum system—every resource and troop production order requires food and a combination of other resources as inputs. As with buildings, standard mode is the more complex but efficient way to produce materials. ### Simple Mode Simple mode reduces the requirements for a production order to food and labor. This is, once again, less efficient in both time and resources—but it allows Lords to produce resources on their Realm or Village even if they don't have access to the input resources required in standard mode. ## Materials Production ### Food The rich and fertile lands of Eternum produce two staple food sources, Wheat and Fish. These are the only materials that can be produced without inputs, so once a Farm or Fishing Village has been constructed, they can produce food indefinitely. ### Resources The 22 resources found in Eternum are the backbone of the world economy. Producing one resource requires the input of two other resources (standard mode), or labor (simple mode). Resources are also the main components in building construction, troop production and Hyperstructure contributions - so mastery of these assets is key to success and security. ### Labor Labor is a new mechanic in Season 1 that has been introduced to simplify and supplement gameplay. It is the primary input for buildings and production in simple mode, but is also required in standard mode for building construction, Realm upgrades and Hyperstructure contribution. Labor is produced by permanently burning resources in the central structure of a Realm or Village. This creates a steady stream of Labor at a fixed rate. Each of the 22 resources can be burned to produce Labor at varying efficiency, dependent on rarity. The amount of resources burned per second to produce Labor at the fixed rate is as follows: ### Troops Troops are essential for exploration, defending your lands and conquering your enemies. Every Lord will be required to procure troops, either through production or purchase, to ensure they remain a relevant force throughout the game. In Season 1, two new troop tiers have been introduced, each requiring a combination of food, rare resources, and troops of the previous tier as input for production. Note: Only T1 troops can be produced in both standard and simple mode. T2 and T3 troops can only be produced in standard mode. ### Donkeys The humble steeds that move all materials around Eternum must themselves be produced in a market building. Donkeys are one-time-use and consumed after a single journey, so Lords will need to procure a steady supply of donkeys, either through production or purchase, to ensure that they can sustain their supply chains, trade with other players, and buy and sell from the Banks. Since donkeys are the 'gas' of this onchain world, they consume $LORDS - the native token of the ecosystem - during production. --- file: docs/pages/eternum/resources/resources.mdx meta: {} import RarityResourceTable from "@/components/RarityResourceTable"; import ResourceIcon from "@/components/ResourceIcon"; import TroopsLimitTable from "@/components/TroopsLimitTable"; import { ResourcesIds } from "@bibliothecadao/types"; # 🪵 Materials ## Materials Overview Materials encompass all transportable assets in Eternum, including: * **Food**: Essential wheat and fish that fuel production and troop movement * **Resources**: The 22 distinct resource types that can be produced on Realms based on their metadata * **Troops**: Military units (Knights, Crossbowmen, Paladins) that can be assigned to armies * **Donkeys**: One-time-use transport units required for moving materials across the world * **Labor**: A special material that enables "simple mode" construction and production * **Ancient Fragments**: Rare materials found in-game that are critical for Hyperstructure construction While all materials can be transported, only specific resources can be produced by Realms based on their inherent properties. Most materials (except Labor) can be bridged out as ERC20 tokens. ## Resources Resources are the foundation of **Eternum**'s economy. Each of the 22 resources plays a vital role in the game's ecosystem, from basic production to advanced military operations. All in-game resources can be traded freely and bridged out as ERC20 tokens. ![Produce from building](/gifs/produce-from-building-click.gif) ## Material Categories #### Material Tiers Resources are distributed across the 8,000 Realms based on rarity, creating natural scarcity and trade opportunities. ### Basic Materials #### Food

Food is the cornerstone of your realm's economy: * Produced without additional resource inputs * Required for most production chains * Essential for maintaining troops and construction

### Strategic Materials #### Military

Military units have unique properties: * They can be traded as resources * Cannot be converted back to tradeable form once deployed to an army * Once deployed, they can still be transferred between armies if they are located on adjacent hexes and are of the same type and tier

#### Transport (Donkeys)

Essential for logistics: * Required for transferring and trading materials * Consumed after a single use

### Special Materials #### **$LORDS** Currency

**$LORDS** is Eternum's economic backbone: * Used as the currency for all market transactions * Bridgeable to external networks * Required to produce donkeys #### Labor

Labor is a fundamental production material: * New Season 1 mechanic * Can be produced by any Realm or Village * Introduces ‘simple mode’ which reduces the complexity of resource and troop production * Required to construct most buildings * Produced by burning resources, with rarer resources yielding more labor #### Ancient Fragments

Strategic end-game material: * Only found in world map Fragment Mines * Required to commence the construction of Hyperstructures * Cannot be produced --- file: docs/pages/eternum/resources/storage.mdx meta: {} import { WeightTable } from "@/components/WeightTable"; import { formatNumberWithCommas } from "@/utils/formatting"; import { divideByPrecision } from "@/utils/resources"; import { CapacityConfig, ResourcesIds } from "@bibliothecadao/types"; import { ETERNUM_CONFIG } from "@/utils/config"; # 🏺 Storage System Your available storage limits the amount of materials your Realm or Village can hold. Effective management of your storage capacity is essential for successful development. Each Realm and Village begins with a base capacity of **{formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.Storehouse]/1000)} kg**. You'll need to construct storehouses to expand your storage capabilities. ## Material Weights Materials in Eternum have different weights that affect storage: ## Storehouses

Expand your storage capacity to support your growing realm: * **Capacity**: Each storehouse adds {formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.Storehouse]/1000 )}kg of storage capacity. * **Expansion**: Build additional storehouses to increase total storage. * **Danger**: When storage is full new production is wasted ## World Structure Storage All world structures have set storage capacities **(that cannot be expanded through the use of storehouses)**. These capacities are as follows: | Structure Type | Storage Capacity | | -------------- | ------------------------------------------------------------------------------------------------------------ | | Hyperstructure | {formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.HyperstructureStructure]/1000)} kg | | Bank | {formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.BankStructure]/1000)} kg | | Fragment Mine | {formatNumberWithCommas(ETERNUM_CONFIG().carryCapacityGram[CapacityConfig.FragmentMineStructure]/1000)} kg | ## Storage Management Tips > 💡 **Best Practices** > > * Check storage levels regularly > * Build new storehouses before reaching capacity > * Pause production when storage is nearly full > * Plan material usage to maximize storage efficiency --- file: docs/pages/eternum/resources/transfers-and-trade.mdx meta: {} import { importantNote } from "@/components/styles"; # 📜 Transfers & Trade ## Transport ### Transfers Throughout the season, Lords will face the need to transfer materials from place to place around the world map, whether it be to their own Realms and Villages, or other structures like Banks, Hyperstructures, and Fragment Mines. Lords have two primary options for initiating transfers: * **Detailed Transfer**: Players can use the comprehensive transfer menu accessible from the Trade tab. This allows transfers of multiple types of materials simultaneously, to any structure on the map—including those belonging to other players. ![Detailed Transfer](/gifs/transfer-all.gif) * **Quick Transfer**: Alternatively, Lords can swiftly transfer resources between their own structures using the resources sidebar, ideal for managing internal logistics and maintaining supply chains. ![Quick Transfer](/gifs/transfer-own.gif) ### The Donkey Network When a transfer is initiated, donkeys travel through the invisible and immutable donkey network. This is the key infrastructure upon which all material transport takes place, facilitating trade between players and Banks. One donkey is capable of carrying up to 500 kg of materials, so the number of donkeys required for a transfer depends on the total weight of the materials being moved. Once a transfer is initiated, it cannot be cancelled, and the journey will take some time depending on the distance to the destination structure. Upon arrival, transferred materials and donkeys must be manually claimed via the 'Resource Arrivals' tab before they become available for use.

⚠️ IMPORTANT NOTE

In Season 1, resource arrivals are restricted by 'gates' to assist in reducing the load that resource arrival entities have on the game. As donkeys arrive at their destination bearing their various goods, they need to wait until the start of a new Eternum Day for the structure's arrival gate to open before they can enter and be claimed by the owning Lord. For example, if a transfer arrives at 2:56 p.m. the owner of the structure will only need to wait until 3:00 p.m. for the transfer to become claimable, however if the transfer arrives at 3:02 p.m., the goods won't be claimable until the next Eternum Day starts (4 p.m.).

## Banks & Marketplaces ### Banks

Six ancient Banks stand evenly distributed around, and equidistant from, the centre of the map. At the start of the game, each Bank is occupied by powerful groups of bandits. Lords who conquer a Bank become the beneficiary of any fees from the Automated Market Maker (AMM) trades that they facilitate. Although Banks collect fees independently, they collectively share liquidity, ensuring consistent and stable trading conditions throughout Eternum. Realms and Villages automatically utilize their nearest Bank when trading through the AMM. ### AMM (Automated Market Maker) The Automated Market Maker (AMM) is a decentralized trading protocol facilitated by the six Banks, allowing for instantaneous and trustless trades 24/7—the DeFi of Eternum. Trades executed via the AMM automatically utilize the closest Bank, directing trade fees specifically to that Bank's owner. Lords can further benefit from the AMM by contributing materials and $LORDS to liquidity pools, earning a share of the fees generated from subsequent swaps. Lords should be aware of the relatively high fees for using the AMM and consider the Orderbook for other trading options first. ### Orderbook Complementing the AMM, the Orderbook is a peer-to-peer marketplace, allowing Lords to place precise buy or sell orders at chosen quantities and prices. This traditional method of trading incurs lower fees and offers Lords strategic control, enabling them to manage market conditions to their advantage and set OTC orders for friends and allies. --- file: docs/pages/eternum/worldmap-movement/movement.mdx meta: {} import TroopMovementTable from "@/components/TroopMovementTable"; import { BiomeStamina } from "@/components/BiomeStamina"; # 🧭 Movement & Exploration Troops Moving Across Eternum

## Stamina Troops in Eternum are deployed onto the world map as armies. Army movement and actions across the map are governed by stamina, a critical resource Lords must carefully manage. Stamina is expended whenever an army moves between hexes, explores previously unrevealed areas, or launches an attack against enemy forces. Each of these actions has a specific stamina cost, making strategic planning essential to maximizing an army's effectiveness. Armies regenerate stamina at a consistent rate of +20 stamina per Eternum Day. Each troop type possesses different maximum stamina capacities, outlined in the table below: Lords should remain cautious about fully depleting the stamina of their armies, as forces with low stamina may find themselves severely disadvantaged if attacked by enemy forces. ## Movement

Moving armies in the client

Armies in Eternum can move freely into any adjacent, unoccupied hex. A hex is considered occupied if it contains a Realm, Village, another army, or a world structure such as a Bank, Fragment Mine, or Hyperstructure. Armies may also move to more distant hexes, provided there is a continuous path of adjacent, unoccupied hexes leading to the destination, and the army has sufficient stamina available for the entire journey. The amount of stamina consumed when moving into a hex depends on both the biome of that hex and the type of troops within the army. The table below details biome-specific stamina costs for each troop type: ## Exploring When an army is positioned adjacent to an unexplored hex, Lords may choose to send that army forth to uncover what lies hidden. Exploring an unknown hex always costs 30 stamina and will reveal that hex to all Lords, permanently expanding the known boundaries of the world. If the newly explored hex contains a world structure or an agent army, the exploring army will automatically be pushed back to the hex from which they started without any additional stamina penalty. Additionally, during exploration, armies gather any valuables they encounter, receiving a stack of randomly selected resources directly into their inventory. If an army becomes overloaded, they will not be able to undertake further exploration, but can continue to travel on previously-explored hexes. Armies can return to a structure to offload the materials, or drop them to free up space. Note that any materials discarded in the field will be permanently lost (burned). Given the possibility of encountering hostile agent armies during exploration, Lords should ensure that their exploring armies are well-prepared and capable of defending themselves in unexpected combat situations.

Explore in the client

Transfer troops in the client

--- file: docs/pages/eternum/worldmap-movement/worldmap.mdx meta: {} # 🗺️ The World Map Eternum World Map

## An Unexplored World At the beginning of each season, Eternum lies entirely unexplored, shrouded in mystery and opportunity. The only exceptions are the six ancient Banks, whose location and surrounding hexes are known and visible from the outset. They can be seen when settling and when observing the world view, each equidistant from the centre of the map and from one another. When Lords settle a Realm, the six hexes directly adjacent to the Realm hex and the six possible village locations are automatically revealed if they haven't already been explored. Beyond these instances, the world remains cloaked by the mist, waiting for ambitious Lords to send forth their armies to explore. Once a hex is explored, the state of the hex (i.e. the biome and whether it contains a world structure or army) is permanently revealed to all Lords. ## Biomes Each hex is assigned one of 16 biome types, each with unique aesthetics and strategic implications. These biomes are procedurally generated across the world map following specific rules that dictate their distribution, ensuring a coherent yet varied world, with certain biomes naturally occurring more or less frequently than others. Biomes impact both combat effectiveness and troop movement. Each troop type—Knights, Crossbowmen, and Paladins—can potentially be advantaged or disadvantaged in battle depending on the biome in which combat takes place; this is explained in more detail in the [Military section](/eternum/military/stamina-and-biomes). Additionally, biomes have the potential to enhance or impede army maneuvers, as the various biomes impact the stamina consumption of each troop type differently as they move between hexes—this is explained further in the [Movement & Exploration](/eternum/worldmap-movement/movement) section below.