# Community

{% hint style="success" %}

#### Like what your seeing?

Consider supporting us as a [GitHub Sponsor](/old-kb/where-to-buy/become-a-sponsor.md) and get instant access to all our Unity assets, exclusive tools and assets, escalated support and issue tracking and our gratitude.\
\
These articles are made possible by our [GitHub Sponsors](https://github.com/sponsors/heathen-engineering) ... become a sponsor today!
{% endhint %}

## Introduction

In the modern gaming landscape being an active dev or having a one sided relationship with your players just isn't good enough. If you expect to succeed as a game developer for any period of time your going to have to invest in your community.

A big challenge with community is the management aspect, as an indie your possibly a solo developer or at most a small team. Very likely you have 1 to 3 languages your team can understand and communicate in. Community management is a very time consuming task that when done properly requires multiple cultural views, multiple languages and multiple time zones of support. 

These articles will go over some considerations and options to keep in mind as you sort out your Community strategy as a project and as a business.


---

# Agent Instructions: 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:

```
GET https://kb.heathen.group/old-kb/guides/community.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.