> For the complete documentation index, see [llms.txt](https://wiki.download.fo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.download.fo/disabling-mods.md).
# How to disable mods
## Using Mod Menu in-game
Many features can already be disabled in-game.
1. With the game open, click `Mods`
2. Scroll down to the specific mod you want to disable
3. Look at the third row with the ⚒️ (tools) or ✏️ (pencil) icon. What does that icon look like?
{% tabs %}
{% tab title="Icon is blue" %}
Click the config button  and see if you can disable the mod or its specific feature.
{% endtab %}
{% tab title="Icon is gray" %}
There is no config option to disable the mod or it is difficult to do. Follow the launcher instructions below to disable the mod.
{% endtab %}
{% tab title="No icon on the row" %}
You've added the mod yourself.
Check if there are config options , otherwise follow the launcher instructions below to disable the mod.
{% endtab %}
{% tab title="No icons on any row" %}
You don't have the *Mod Menu Helper* resource pack enabled for some reason. Here's how to fix it:
1. Click `Done`
2. Click `Options...`
3. Click `Resource Packs...`
4. Click `⏵` on "Mod Menu Helper.zip"
5. Click `Done`
6. Click `Mods`
7. Now check again to see which icons you see.
{% endtab %}
{% endtabs %}
## Disabling mods entirely
Here are instructions to disable mods entirely, for example due to incompatibilities.
{% hint style="info" %}
You can also delete the mod(s), but that will make it harder to [use them later](/adding-more-mods.md), unless you remember the mod's name exactly.
{% 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://wiki.download.fo/disabling-mods.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.