> For the complete documentation index, see [llms.txt](https://probacon-hub.gitbook.io/probaconhub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://probacon-hub.gitbook.io/probaconhub/about/q-and-a.md).

# Q\&A

### Is this illegal?

No, exploiting is completely legal. Many often conflate exploiting with hacking, questioning the legality and fairness of the former. It's crucial to understand that exploiting is legal, distinctly different from hacking, which involves attacking a server and bypassing its firewall. Exploiting, by contrast, doesn't engage with such malicious activities.&#x20;

### Is exploiting unfair?

Some argue that exploiting grants an unfair advantage to those who are not using it. However, I maintain that exploiting is fair; it's a choice available to all players. The real imbalance in gaming arises from pay-to-win (p2w) models, which undeniably skew the playing field.


---

# 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://probacon-hub.gitbook.io/probaconhub/about/q-and-a.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.
