> For the complete documentation index, see [llms.txt](https://docs.playtavern.com/tavern/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playtavern.com/tavern/faq.md).

# FAQ

## Do I need to know how to code to use Tavern?

No! Tavern is designed for a no-code experience. You can create engaging games by submitting transactions. If you do know how to code, you can add custom components by using the provided interfaces.

## What types of NFTs and Tokens can I use with Tavern?

Tavern (can be) compatible with any ERC-20, ERC-721, or ERC-1155 token. While these components don't exist yet, with user demand it is very straightforward to use token ownership as a requirement to join a game, as a reward for winning, as a resource ingame, or even as an RPG character.

## What are the benefits of using Tavern for my community?

Tavern offers a fun and interactive way to engage your community members. It allows you to create shared experiences centered around your NFTs and foster stronger connections.

## What are the monetization options for Tavern games?

We're still figuring this out! Of course your NFT projects are yours to monetize, but that has nothing to do with Tavern.

## Where can I learn more about building games with Tavern?

We're just getting started! [Reach out on warpcast](https://warpcast.com/~/channel/playtavern)!


---

# 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://docs.playtavern.com/tavern/faq.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.