> For the complete documentation index, see [llms.txt](https://docs.2040world.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2040world.io/in-game-items/ammunition.md).

# Ammunition

Let's examine the connection between industries using ammunition production across three sectors as an example.

### Example 1

The game features cartridges that require casings. The casings are produced by the heavy industry sector. However, creating these casings requires ingots, which are smelted in light industry.

### Example 2

To produce shotgun shells, you'll need copper and lead (or other metal combinations). Copper comes from light industry, while lead is produced by heavy industry.

### Example 3

The game will include energy-based ammunition that doesn't require casings. However, producing high-quality energy ammo will still need components from the heavy industry sector

As you can see, the industries are interconnected - check the diagram below. Yes, the system might appear complex, but its in-game implementation will be maximally straightforward and intuitive!

<figure><img src="/files/a2qROYWJ42pp2ACApks3" alt=""><figcaption></figcaption></figure>


---

# 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://docs.2040world.io/in-game-items/ammunition.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.