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

# Getting updates

Products bought through Updatr update themselves. You don't re-download anything.

## How it works

When your game starts, the product asks Updatr whether a newer version exists. If one does, it fetches and applies it in place.

That means:

* You get fixes without doing anything
* You're never running an outdated copy by accident
* Sellers can patch a bug for everyone at once

## If a product stops updating

Check, in this order:

1. **Your license is active.** A paused or revoked license blocks updates. See [Your library](/merithic-docs/buying/library.md).
2. **The key is intact.** If the product's key was edited or removed, it can't authenticate.
3. **Updatr isn't in maintenance.** Check [status.merithic.com](https://status.merithic.com).

If all three look fine, contact the seller. They can see alerts and license state for their own products.

## Updates you didn't want

Updatr doesn't offer per-buyer version pinning; you receive what the seller publishes. If an update broke something, tell the seller. They can roll back by publishing the previous build.


---

# 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://merithic.gitbook.io/merithic-docs/buying/updates.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.