> For the complete documentation index, see [llms.txt](https://cesium.gitbook.io/cesium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cesium.gitbook.io/cesium-docs/support/module-does-nothing.md).

# A module is enabled but does nothing in game

Most of the time the module is waiting for a key, an item, or a target.

{% hint style="info" %}
Most of the time the module is waiting for a key, an item, or a target.
{% endhint %}

## Run through this list

{% stepper %}
{% step %}
It needs a key. Several modules do nothing until a key is bound or held: Auto Safe Anchor, Crystal Macro, Key Pearl, Pearl Grapple, Pearl Catch, Diagonal Pearl Catch, Hotbar Refill, and others. Open the module's panel and check the Keybind field.
{% endstep %}

{% step %}
It needs an item. Totem modules need totems in your inventory. Auto Elytra needs an elytra and fireworks on the hotbar. Shield Disabler needs an axe. Auto Pot needs instant health splash potions.
{% endstep %}

{% step %}
It needs a target in range. Combat modules act only on a target inside their Range and FOV. Check both. AntiBot may also be filtering the target out.
{% endstep %}

{% step %}
It needs a weapon in hand. AimAssist, Silent Aim, and TriggerBot have a Require Weapon setting. With it on, they stay off while you hold anything else.
{% endstep %}

{% step %}
The config you applied turned it off. Applying a config replaces the module state. Check the switch is on after switching configs.
{% endstep %}

{% step %}
Reset the module. Open its panel and click Reset, then set it up again.
{% endstep %}
{% endstepper %}

## Confirm Cesium is actually loaded

Look at the launcher. Session info shows the instance and the module count. If it says No instance running, Cesium is not in the game. See [The launcher says no instance running](/cesium-docs/support/no-instance-running.md).

## Still nothing

Ask in [Discord](https://discord.gg/3QBFFwbbH) with the module name, its settings, and what you expected.


---

# 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://cesium.gitbook.io/cesium-docs/support/module-does-nothing.md?ask=<question>&goal=<user_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.