> For the complete documentation index, see [llms.txt](https://docs.rivalryze.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rivalryze.com/for-guild-admins/hosting-guild-contests.md).

# Hosting Guild Contests

A **Guild Contest** is a Contest (Battle or Bounty) restricted to members of a specific Discord server. They're a great way to run friendly competitions inside your community without opening to the whole RivalRyze player base.

This page is the guild admin's view. For the general mechanics, see [Hosting Your Own Contest](/contests/hosting-a-contest.md).

## Who can host guild Contests

Any guild member can host a guild Contest — admin status isn't required by default. The bot will check that:

1. The host is a member of your guild on RivalRyze.
2. The host has connected at least one gaming platform compatible with the Contest's Objective Mode.

You can configure your Guild to **restrict hosting to admins only** under **Guild → Manage → Settings → Hosting**.

## Hosting from Discord (`/create-challenge`)

The fastest way to host is the `/create-challenge` slash command:

```
/create-challenge
```

The bot walks you through:

1. **Contest type** — Battle (leaderboard) or Bounty (objective).
2. **Objective Mode** — pick from the available modes for that type. See [Objective Modes](/contests/objective-modes.md).
3. **Game** — search and select the game (for game-specific Contests).
4. **Entry fee** — in gems.
5. **Duration** — how long the Contest runs.
6. **Access policy** — defaults to **Guild Members Only**; you can override.
7. **Optional settings** — min/max participants, host boost, scheduled start, reward distribution.

When you confirm, the Contest is created and announced in your Activity Feed channel automatically.

## Hosting from the website

1. **Contests → Create**.
2. Configure as described in [Hosting Your Own Contest](/contests/hosting-a-contest.md).
3. Under **Access Policy**, choose **Guild Members Only**.
4. Pick your guild from the dropdown.
5. Publish.

The Contest is announced in your Activity Feed automatically (assuming announcements are enabled — see [Guild Settings](/for-guild-admins/guild-settings.md)).

## Default access policy: Guild Members Only

When a guild member creates a Contest via `/create-challenge` in your server, the default access policy is **Guild Members Only**. This means:

* Only members of your Discord server (who are on RivalRyze) can join.
* The Contest is visible to your guild members on the website and via `/leaderboard` commands.
* Non-guild members on RivalRyze never see the Contest.

The host can override this to **Public**, **Allowlist**, **Password Protected**, or **Role-Based** when creating the Contest, but **Guild Members Only** is the sensible default for guild-organized Contests.

You can change the **default policy** for your guild under **Guild → Manage → Settings → Default Contest Policy**.

## Promoting guild Contests in Discord

Once a guild Contest is live, drive participation by:

* **Pinning the Contest announcement** in your Activity Feed channel.
* **Calling it out in `#general`** with `@everyone` and a link to the Contest.
* **Using `/contests`** to list current open Contests (members can browse without leaving Discord).
* **Watching the Activity Feed for live updates** as members join.

## Co-funding the prize pool

As an admin, you can boost guild Contest prize pools to encourage participation:

* **Host boost** — when you (or any member) create a Contest, the host can seed the prize pool from their wallet.
* **Donations from admins** — any admin can donate gems to any guild Contest as it runs. Donations show on the Contest page with your username.

This is a way to "sponsor" your community's Contests from your gem reserves.

## Role-based Contests

If your server has Discord roles like "Tournament Players," "VIPs," "Mods," etc., you can create Contests restricted to a specific role:

* Set the access policy to **Role-Based** when creating the Contest.
* Pick the eligible Discord role.

Only members with that role can join. Useful for:

* Exclusive tournaments for paid Discord members
* "Mods vs. Members" friendly events
* Skill-tier brackets ("Diamond+ only")

## After the Contest ends

When a guild Contest ends:

* Winners take their share of the prize pool — paid out automatically based on the reward distribution.
* The result is posted to the Activity Feed.
* The Contest moves to your guild's **Past Contests** tab on the website.

Past Contests are great for reviewing community activity, identifying top performers, or running seasonal awards.

## Disputes and Fair Play

If a member believes a Contest result is incorrect (e.g., their achievement didn't count due to a sync issue):

1. The member should first try a manual sync ([Troubleshooting](/connecting-gaming-platforms/troubleshooting-sync.md)).
2. If the issue is real, **the member contacts RivalRyze** [**support**](/help-and-faq/contact-support.md) — not the guild admin. We have the data needed to investigate.
3. Guild admins can't manually adjust Contest results, even for Contests in their own guild. This keeps results fair.

For Contests involving achievements or trophies, [Fair Play](/fair-play/auto-pop-and-fair-play.md) may classify some unlocks as auto-pops. Hosts of guild Contests receive notifications for any Auto-Pop Groups affecting unknown-source or suspicious classifications and can choose to include or exclude.

## Running tournaments

For larger events (brackets, multi-stage), the standard Contest structure isn't ideal — you'd chain Contests together manually. We're working on a dedicated Tournaments feature.

In the meantime, you can run a tournament by:

1. Creating multiple **Allowlist** Contests for each round.
2. Manually approving the winners of round 1 into round 2, etc.
3. Posting a bracket image in your Discord server to track progress visually.

This is manual but works.

## Related

* [What is a Contest](/contests/what-is-a-contest.md)
* [Battles](/contests/battles.md) and [Bounties](/contests/bounties.md)
* [Hosting Your Own Contest](/contests/hosting-a-contest.md) — general flow
* [Guild Settings & Activity Feed](/for-guild-admins/guild-settings.md)
* [Bot Commands Reference](/for-guild-admins/bot-commands-reference.md)
* [Fair Play](/fair-play/auto-pop-and-fair-play.md)


---

# 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.rivalryze.com/for-guild-admins/hosting-guild-contests.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.
