> 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/edit-a-division.md).
# Edit a Division
Editing a Division is very similar to creating it. In fact, when you create a Division and attach Mercenaries, you can also perform modification operations. However, if you want to make changes to an existing Division or one under development, the first thing to keep in mind is that changes can only be made if the Division is not currently undertaking any missions and only if the previously completed mission has been "closed" with the **Claim**. Otherwise, the Division will appear with an alert stating that it is on a mission and therefore cannot be modified.
If the Division is unlocked, proceed by performing this operation using the "**View Mercenary**" button.
The Division will look very similar to the following and you can notice that each Mercenary has 4 additional slots.
From here you can remove equipment from the 4 additional slots and you can remove Mercenaries (each Mercenary slot must be empty to remove the Mercenary).
To remove the Mercenary, just click on the red button.
The usual confirmation prompts will appear and the Mercenary will be returned to the staked assets section. If you want it return to the WAX wallet, you need to unstake the NFT.
At this point you will see the updated values of the division which will no longer be counting that NFT.
{% 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/edit-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.
.png)
.png)
.png)
.png)