> For the complete documentation index, see [llms.txt](https://mode-development.gitbook.io/atomcombat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mode-development.gitbook.io/atomcombat/modules/announcements.md).

# Announcements

Config file: `modules/announcements.yml`

A simple recurring broadcaster for store links, rule reminders, or tips — the kind of thing you'd otherwise need a separate plugin for. Disabled by default.

```yaml
interval-seconds: 900
random-order: true
messages:
  - '&8[&cAtomCombat&8] &7Use &f/bounty gui &7to browse active bounties.'
  - '&8[&cAtomCombat&8] &7Use &f/ability gui &7to check your combat abilities.'
  - '&8[&cAtomCombat&8] &7Check the leaderboard with &f/combatstats top'
```

* `interval-seconds` — time between broadcasts (minimum `10`).
* `random-order` — `true` picks a random message each time; `false` cycles through them in order.
* `messages` — the raw list of messages, with legacy `&` colour codes. These are **not** part of the [language files](/atomcombat/getting-started/language.md) — they're your own server-specific text, edited directly here.

Leave `messages` empty to effectively disable broadcasting even if the module is enabled.


---

# 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://mode-development.gitbook.io/atomcombat/modules/announcements.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.