Setup Instructions

Getting started

    1.
    If you don't already have hosting for your bot, we recommend Pebble Host! Click here to get started with Pebble Host.
    2.
    Once your server is ready, make sure it is set to offline.
    3.
    Move the zipped bot file (bot.zip) into your server's file manager.
    4.
    Next you will need to extract the zip file within your server's file manager.
    5.
    Do not press start on the bot hosting yet.

Discord Developer

    1.
    Navigate to the Discord Developer Portal.
    2.
    Create a "New Application" and name it whatever you'd like (eg. "Ticket Bot")
    3.
    Click on the "Bot" button in the sidebar, and click "Add Bot".
    4.
    Feel free to upload your bot's icon. You can come back to this later if you'd like.
    5.
    Next click on the "OAuth2" button in the sidebar.
    6.
    Click "Add Redirect", and you can put anything here (eg. "https://oneticketbot.com")
    7.
    Make sure to save your changes.
    8.
    Then scroll to the "OAuth2 URL Generator" section.
    9.
    Select your redirect link, and check "bot".
    10.
    Once you've done that copy the link and paste it in your browser.
    11.
    Select the server you'd like the bot to join.
    12.
    Make sure the bot connected to the server.

Connecting the bot to hosting

    1.
    In the Discord Developer Portal, navigate to "Bot" in the sidebar, and copy the token.
    2.
    Navigate to your bot server's file manager and open "config.json"
    3.
    Paste the token in the config file.
    4.
    Save the file.

Setting up server IDs

    1.
    You will need to enable "Developer Mode" within Discord.
    2.
    Go to User Settings > Advance > Enable Developer Mode.
    3.
    Navigate to your server.
    4.
    Create a category that you want the tickets to go under.
    5.
    Right click on the category and click "Copy ID".
    6.
    Paste the ID in your bot's config.json file in the line that says "ticket-category".
    7.
    Next create a text channel for your ticket logs (eg. "ticket-logs")
    8.
    Right click and copy the text channel's ID.
    9.
    Paste the ID in the line that says "loggingchannel"
    10.
    On your server create a staff role that can see the tickets.
    11.
    Copy the role's ID and paste it in the line that says "ticketRoles"

Creating your Mongo URL

    1.
    Navigate to Mongo Atlas and click "Get started now" or "Try Free". Don't worry its free.
    2.
    Create an account and navigate to the dashboard
    3.
    Create a "New Project" and name your project (eg. "Ticket Bot")
    4.
    Create your project and then click "Build a Database".
    5.
    Next click on the Shared option and click "Create"
    6.
    Select a preferred region (don't change cloud provider)
    7.
    Click "Create Cluster" and wait for the cluster to be created (1-3 minutes)
    8.
    Once it's ready, click "Connect".
    9.
    Click "Add current IP address" and enter your server's IP address
    10.
    Next you will enter a username (we recommend using your Discord server name)
    11.
    Do not enter a password, instead click "Autogenerate a Secure Password" and copy the password
    12.
    Paste the password somewhere so you can reference it later.
    13.
    Click "Create Database User" and then "Choose a connection method".
    14.
    Next click "Connect using MongoDB Compass" and copy the connection string.
    15.
    Navigate to your bot server's config.json file
    16.
    And find the line that says "mongourl" and paste your connection string.
    17.
    After you paste, where it says <password> paste in the password you saved earlier. Don't include < >
    18.
    Save the file and close out of MongoDB.

Final Steps

    1.
    You can now start your bot server. Check to see if your bot has come online on Discord.
    2.
    In the text channel you'd like the create ticket embed to go, type /system
    3.
    Once the embed reaction message appears, right click on the message and click "Copy ID"
    4.
    Paste the ID in your bot's config.json file on the line that says "message-id"
Last modified 1mo ago