> For the complete documentation index, see [llms.txt](https://southside.gitbook.io/ssc-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://southside.gitbook.io/ssc-whitepaper/gameplay/style-support.md).

# Style Support

{% hint style="info" %}
The vast majority of video games (and especially anything metaverse-esque or play to earn) are built in a way to encourage a specific playstyle. For example, most FPS games revolve around a certain "meta." Or, some play to earn games simply force the user on an never ending quest to upgrade their characters to deal more damage or what-not.
{% endhint %}

Southside City is designed in a way to allow a vast multitude of play-styles. In order to create the true web3 metaverse, we need to ensure that the drug smuggler and the lofi-cafe shop owner both feel as though they are an integral part of the game's social aspects and ecosystem.

Each occupation, gameplay element, and so forth are designed to ensure a co-dependance. Of course this will require further fine tuning as game development progresses, but we're building one of the few video games that you can truly do anything you want without fear of missing out. 


---

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

```
GET https://southside.gitbook.io/ssc-whitepaper/gameplay/style-support.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.