> For the complete documentation index, see [llms.txt](https://info.mortisian.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.mortisian.com/grandvitamortems-greed/grandvitamortem-halts-creator-payments-07-02-2023.md).
# GrandVitaMortem Halts Creator Payments 07/02/2023
It is to mention me and my team have never seen a single moment of proof he has paid his creators. Instead we have heard he "paid" people only without verification from himself or those "paid"
GrandVitaMortem, why did you halt these supposed payments to the Syndicate Team? Why have I seen you take $50.00 from LoHawke to fix his arm after he lost it within the Dungeon Floor 1. It was in a Movie and Chill world to purchase weed. You claim it isn't enough to even feed yourself but what about the people who put serious man hours into your projects you consistently promise will be paid eventually. You have constantly told Avatar Creators to talk to DemonLordDan about payments but we still haven't seen the receipts for anything.
I have personally seen you take cash to purchase things for yourself that was not food, why was that not put into the funding jar?
---
# 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://info.mortisian.com/grandvitamortems-greed/grandvitamortem-halts-creator-payments-07-02-2023.md?ask=&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.
