> For the complete documentation index, see [llms.txt](https://planetary-defense-guide.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://planetary-defense-guide.gitbook.io/guide/web-game/divisions-overview/create-a-division.md). # Create a Division Let's get to the heart of the game: **The Divisions**.
We've already mentioned that the Divisions are commanded by **Warlords** and that each Warlord has different slots. You can see the list of [NFT templates](/guide/getting-started/what-is-planetary-defense/nft-templates.md) in the appropriate section of this guide. However, we'll provide a summary table of the basic slots (for slots and ascension-related changes, refer to the dedicated table in the [links](/guide/getting-started/useful-links.md)). There are 6 Warlords, one for each rarity. The movement cost reduction has a base value of 0 on all Warlords and can vary if these NFTs are being Ascend, allowing us to have an improved movement cost reduction for our division.
**COMMON UNCOMMON RARE EPIC LEGENDARY MYTHIC**

The number of slots each Warlord has determines how many Mercenaries we can equip, regardless of their rarity. We remember that all NFTs can be of **6 rarities**. Divisions are used to participate in missions. So before building a Division, it's generally a good idea to determine which missions you want to focus on. As we'll look at missions in more detail later, they have attack requirements, defense requirements, or both. Depending on the mission you want to participate in, you'll build your division as fit to achieve that objective. This means you can build a division made up of all common troops rather than one made up of all mythical troops. The real difference will be the **Move Cost** and therefore the time it will take our Division to complete a mission. The Warlord itself doesn't have any move costs, while troops, and therefore our Mercenaries, do.

## ^{How is this move cost calculated and what impact does it have on a Division?} The move cost of each Mercenary contributes to the move cost of a Division. Let's say we want to create a Division that can complete a mission with a requirement of 5,000 ATK. Well, we prepare our division with all the Mercenaries and we've reached 5,000 ATK. Once the Division is complete, as we saw before, it will have a move cost that will be the total of the move costs of all the Mercenaries. The choice of NFT to include in a Division with their move cost has a significant impact on the Division itself. The move cost, thanks to a conversion, allows us to calculate the number of seconds that Mercenary will add to the the base cooldown of a mission. The number of seconds is calculated by taking the move cost value and multiplying it by **10**. Let's look at some examples: We want to build a **5,000 ATK** division and use Mythic Mercenaries like the one above, whose **attack power is 285**, **defense power is 285**, and **move cost is 81.**\ To build a 5,000 ATK Division, we'll need 18 units, which will give us a value of **5130 ATK** (285 x 18), **5130 DEF** (285 x 18), and **1458 MOVE COST** (18 x 81). We take the value of **1458** and multiply it by 10 (**14,580 secs**). We have the additional seconds to add to the mission cooldown to find the total time it will take your division to complete a mission. So let's take the base cooldown of a mission:

In this example, we've considered the cooldown time for a **6-hour mission**. We'll add the seconds converted to hours (14,580 / 3600 = **4.05 hours**) to this base cooldown. In total, with a Division constructed this way, our mission will last approximately **10 hours**. Remember that there are other NFTs you can assign to Mercenaries, some of which further reduce this cooldown, but we'll cover that later. Now that we have understood how the various values of a Division work, let's see how we can create it from an operational point of view. First of all, we said that to have a Division, we need a Warlord who gives us slots to add Mercenaries. Let's go to the Stake section and stake our Warlord.

Let's proceed with staking and go to My divisions section

All available Warlords will appear like this

We select the one we are interested in and click on the "create division" button (you will be asked to give some confirmation in the wallet and everything is normal)

At this point, our Warlord will appear at the bottom of the list of available Divisions. We haven't added any Mercenaries yet, so all the ATK, DEF, and MOVE COST values are **zero**. This is because the Warlord doesn't apply any values and only defines the number of available slots.

at this point we click on **View Mercenary** and then **Add a Mercenary**

If you've previously **staked Mercenaries**, you'll see them available in this section. Please note that in-game NFTs must be staked to work, and only certain NFT categories can be used in Divisions (e.g., Materials cannot be used). The usual requests for confirmation of the operations and your wallet will appear.

Once we've added our first Mercenary, we'll see the division update with the correct values. In this example, we see that the **ATK** has gone from **0 to 23**, the **DEF** from **0 to 23**, and the **MOVE** from **0 to 15**. We repeat this process for all the troops we want to add until the Division is complete and ready to be sent on a mission. {% hint style="info" %} Note: The information on this page reflects the current state of Planetary Defense's development. As new features are actually released and the game evolves, some details here may change, and this page will be updated to stay accurate. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://planetary-defense-guide.gitbook.io/guide/web-game/divisions-overview/create-a-division.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.