> For the complete documentation index, see [llms.txt](https://peculiar.gitbook.io/odystorm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peculiar.gitbook.io/odystorm/game-core/gameflow.md).

# Gameflow

The core gameplay of OdyStorm centers around **Ships** and **Shadow Stalkers**. These repeatable activities allow players to **earn** rewards and **strengthen** their clans.

Each player can attack another multiple ship per day, with difficulty based on **Energy cores and Ranks** — the player expends a certain amount of $ODY equal to their **strength**, which is subtracted from their $ODY balance. Defeating bosses earns loot for the player's clan, which is **divided among members** every day based on their contributions.

Group raids also reset daily at 00:00 UTC, initiated by the group leader against **rival groups**. Group members can join raids in **a six hour attack window** after initiation. Winning clan raids **grants resources** taken from the losing clan, who loses power but earns no rewards.

The gameplay focuses on repeatedly **raiding bosses** and **rival clans** to accumulate resources and progress clan power. Superior performance in these core activities enables players to **advance their clans** and **develop their characters**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://peculiar.gitbook.io/odystorm/game-core/gameflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.