> For the complete documentation index, see [llms.txt](https://docs.sefiraat.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sefiraat.dev/readme/buy-me-a-coffee.md).

# Throw me a sponsor, get some stuff!

I'll keep working on my addons no matter what, but if you fancy helping me out with development by throwing some coffee money my way, it would be more than welcome and so very appreciated.

In return you will get a few minor perks within my addons like:

* You name will be added to a list of names used as Easter eggs within most of my addons, appearing on summoned armour stands, the names for spawns, in Crystamae's Easter egg spell and more. Whenever I need a random name to be applied to something, I will draw it from this pool of names.
* You can request a custom Crystamae Historia story to be made, it needs to be relatively thematic and unclaimed - you will be noted as the sponsor for that story.
* You can have a custom metal/material with a custom trait added to SlimeTinker

Additional details and other perks are all listed on my sponsorship page below <3

{% embed url="<https://github.com/sponsors/Sefiraat?o=esb>" %}


---

# 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://docs.sefiraat.dev/readme/buy-me-a-coffee.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.