> For the complete documentation index, see [llms.txt](https://communityone.gitbook.io/communityone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://communityone.gitbook.io/communityone/feature-deepdive/hype-engine/customizations.md).

# Customizations

> **Click** [**here**](https://discord.com/oauth2/authorize?client_id=1069423090225918082\&permissions=275146722545\&integration_type=0\&scope=applications.commands+bot\&redirect_uri=https%3A%2F%2Fcommunityone.io%2Fdashboard%2Fbot-auth-complete%2F%3Fsource%3Dgitbook\&response_type=code) **to introduce our bot to your server.**

### Custom Reward

By default, Hype Engine includes an item shop, and we automatically stock raffle tickets for nitros, steams, and game of the month selections (such as Monster Hunter Wilds, Baldur's Gate 3, etc.). 

You can stock your items, such as custom roles, merch, and physical items. 

<figure><img src="/files/lRAkhaLPJgSnQ90S7tuQ" alt=""><figcaption></figcaption></figure>

### Customize Rewards

Head to our configuration dashboard Hype Engine page & Click on **Rewards -> + Add Item**

<figure><img src="/files/UCaB2FY5HG3UYlA63RUd" alt=""><figcaption></figcaption></figure>

Here's what you will see:

<figure><img src="/files/NwIq2eUgFwYXCLXMtj3N" alt=""><figcaption></figcaption></figure>

* **Item Type:**&#x20;

  * Manually Fullfilled: It is anything that requires manual work, such as merch. Users will request to redeem the item, we will automatically open up a ticket with detailed requests. Once you have fulfilled it, you can then close the ticket manually.&#x20;

  <figure><img src="/files/3EXkOitfkg3bmHwi1Atu" alt=""><figcaption></figcaption></figure>

  <figure><img src="/files/Lv0orcd4eBPtZcdkHHgt" alt=""><figcaption></figcaption></figure>

  * Role: Once a user redeems for the role, they will automatically be granted the role, and points will be deducted.&#x20;

  <figure><img src="/files/Jh4cPHlfvLs2ddIWqcCS" alt=""><figcaption></figcaption></figure>

  Once you specify the role as the custom item, you can configure the role that we should issue

<figure><img src="/files/CIvx0btg0ueSbogWoq2U" alt=""><figcaption></figcaption></figure>

* **Prices**:  We recommend 30-40 points for your first custom role item. You can then add a different role that requires significantly more points for the superfans.&#x20;
* **Required Role to Purchase:** If there is a precondition.&#x20;
* **Stock: Suitable for physical items such as merchandise.**&#x20;

While you can customize the price for all your custom items, you can't customize the price for existing raffle tickets provided by CommunityOne. Your members might see a different cost per raffle ticket depending on the server. Typically, users may see a lower price if the server is using our premium package or is highly active and unlocked to level 2.&#x20;

### Tracking your item shops:

You can track who bought what directly on your analytics dashboard.&#x20;

<figure><img src="/files/1xqojWVI6EjH8rZtCchn" alt=""><figcaption></figcaption></figure>

### Conversation Guide

If you want your member to talk about specific topics, or if you don't want your members to chat in certain channels, this is where you can customize.&#x20;

#### Channel Selections

You can specify which channels Hype Engine should reward users when they are chatting. If you leave it blank, we will track a memeber's chatting behavior everywhere.

Usually, you want to specify where users can get points by chatting to prevent Spam. For example, a developer server might want to "fend-off" technical support channels so that they don't get overwhelmed by the amount of messages.&#x20;

<figure><img src="/files/QPaHk0dssuHm4fSYXAH6" alt=""><figcaption></figcaption></figure>

#### AI Topic Guide (Premium):

If you want users to talk about particular topics, for example, at Communityone, we like it when users talk about our bot features, then you can give some guildlines to members on what topics they should focus on.&#x20;

<figure><img src="/files/HUB3XlIHi7utXBFdX4FB" alt=""><figcaption></figcaption></figure>

Hype Engine uses AI to track members' chat content and will reward them with extra points if they mention these topics.&#x20;

<figure><img src="/files/gaotLGBbuSVBUMs0Zrye" alt=""><figcaption></figcaption></figure>

### Customizations (Appearance)&#x20;

You can change the color, the point name (communityone by default), and even the emoji for the points here.

<figure><img src="/files/LNFcgB1BjNzThiStWqRv" alt=""><figcaption></figcaption></figure>

Here's a different look from another server

<figure><img src="/files/4eXluFtmIfRpMiOqOuix" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Join [Discord](https://discord.gg/nVqt3z78Mw) for questions, comments, and a little gift <img src="https://fonts.gstatic.com/s/e/notoemoji/latest/1f381/512.gif" alt="🎁" data-size="line"> or back to [CommunityOne Home](https://communityone.io/)
{% endhint %}


---

# 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://communityone.gitbook.io/communityone/feature-deepdive/hype-engine/customizations.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.