• A Discord bot host (Locally or Remotely) for Node.js v18 (Required – NOTE: ServerStarter is my recommendation, you can host with whoever you want or locally!)
• Node.js v18 installed on your OS (Required)
• A Discord bot token (Required)
  
• Basic JSON knowledge for config editing (Required)
• A Battlemetrics token for steam account checks (Optional)
• A Steam API token for steam account checks (Game ban verification) (Optional)
• A Cheetos API key (Optional)
• A linking system for verifying users (Simple Link, Steamcord or Platform Sync) (Optional)

Windows

1. Download the zip and unpack it in your desired location.
2. Edit your config files to your liking (config.json, handler.json, options.json and all question files) and upload your bot token to the .env file in configs folder.
3. Run the start.bat file to automatically install all needed modules and start the bot up in its own instance.

Linux

1. Download the zip and unpack it in your desired location.
2. Install the modules by being in your ticket bot directory and running the “npm i” command. This will create a node_modules folder.
3. Set up your bot on a package like PM2. Installation can be found on their website.
4. Use the PM2 commands to start your bot!

Inviting your Bot

After you have created your bot application on the Discord Developer Portal, make sure you have enabled all of the Privileged Intents in the bot section on the sidebar!
You now need to invite it to your discord with the correct permissions!

https://discord.com/api/oauth2/authorize?client_id=APPLICATIONIDHERE&permissions=2147871824&scope=bot%20applications.commands

Replace the “APPLICATIONIDHERE” section with your bots ID found on the developer portal and then you can invite it to your discord!

Found in the config folder, this is the main bot config file and one of the main files you’ll be editing.

Found in the ‘content -> questions’ folder, this is the question file for each ticket type you want. All can be customized differently to each other to allow different actions for different tickets.

{

    “questions”: [

        “Question 1?”,

        “Question 2?”,

        “Question 3?”

    ], // “questions” are the questions that get asked to the user when they make a ticket, no limit on count, but be wary of character limits when receiving responses

    “pre-message”: “This message is sent once a button has been clicked by a user”, // A pre message that is sent to the user via DM once the user has clicked a ticket button

    “post-message”: “This message is sent once the questions have all been answered as a final message”, // Same as pre, but for after all the questions are answered

    “accept-message”: “This message is sent if the users ticket has been auto accepted”, // The auto accept button response message

    “deny-message”: “This message is sent if the users ticket has been auto denied”, // The auto deny button response message

    “post-channel”: “”, // This is your “holding channel” where all new tickets will come in for you to handle

    “transcript-channel”: “”, // This is where you want your transcripts for this ticket type to go once you’re done

    “ticket-category”: “”, // The channel category you want the open tickets to appear in, when you open a ticket with the user for conversation.

    “access-role-id”: [“”], // This allows extra roles to have access to this particular ticket type

    “role-pings-on-new-ticket”: true, // Determines whether the admin and access-role roles will be pinged when a new ticket is made by a user.

    “check-cheetos”: false, // Whether the bot should check for cheatcords with this ticket type

    “check-steamid”: true, // Whether the bot should check the users Steam account with this ticket type (needVerified MUST be true for this to work)

    “display-user-discord-info”: true, // Whether or not the bot should display basic user info like roles and creation dates.

    “needVerified”: true, // Whether the user needs to be verified to make a ticket of this type

    “allow_feedback”: true, // Allow users to send feedback once they recieve their final response from the team

    “open-as-ticket”: false, // Push the ticket to be opened instantly instead of going to the holding channel

    “max-active-tickets”: 1, // Number of queued tickets allowed in the holding channel for each user at the same time.

    // This will customize the embed that shows what servers the ticket creator has been on within your org.

    “check-server-activity”: {

        “enabled”: true,

        “show-only-online-server”: true,

        “show-online-status”: true,

        “show-hours”: true,

        “show-last-seen”: true

    },

    // The 4 buttons that show on every embed in the “holding channel”. Allows you to set custom messages and emojis

    “active_ticket_button_content”: {

        “accept”: {

            “title”: “”,

            “emoji”: “”,

            “enabled”: true

        },

        “deny”: {

            “title”: “”,

            “emoji”: “”,

            “enabled”: true

        },

        “custom_response_message”: {

            “title”: “”,

            “emoji”: “”,

            “enabled”: true

        },

        “make_a_ticket”: {

            “title”: “”,

            “emoji”: “”,

            “enabled”: true

        }

    },

    // If feedback is enabled, these are the questions they will get asked – NOTE: Questions can only be 45 characters long MAX

    “feedback_questions”: [

        “How was your experience in your ticket?”,

        “What would you recommend for improvements?”,

        “What you rate your experience out of 5?”,

        “Would you be happy to use our system again?”,

        “You can only have 5 questions in your forms.”

    ],

    “successful_feedback_message”: “Thanks for your feedback! It really helps us make our systems better for everyone.” // The response sent to the user once they successfully send a feedback form.

}

Found in the ‘content -> handler’ folder, this is the content that will be shown on your “create-a-ticket” channel embed. The initial post where people will make their tickets. You can add up to 10 different buttons here, by simply copying and pasting a object block. Always check your code with a JSON checker if you run into issues.

{

    “options”: {

        “Player Report”: {

            “abbreviation”: “PRPT”, // The abbreviation used in the database and in your unique ticket IDs for each ticket made, custom to this ticket type

            “question_file”: “playerreport.json”, // The file name of your question file

            “unique_button_identifier”: “button1”, // The UNIQUE id of this button (It can not be the same as another button)

            “button_type”: “SECONDARY”, // The Button type (PRIMARY, SECONDARY, SUCCESS or DANGER)

            “button_emoji”: “🛑”  // The Emoji you want on the button (this can be blank)

        },

        “VIP Related”: {

            “abbreviation”: “VIP”, // The abbreviation used in the database and in your unique ticket IDs for each ticket made, custom to this ticket type

            “question_file”: “VIP.json”, // The file name of your question file

            “unique_button_identifier”: “button2”, // The UNIQUE id of this button (It can not be the same as another button)

            “button_type”: “PRIMARY”, // The Button type (PRIMARY, SECONDARY, SUCCESS or DANGER)

            “button_emoji”: “👑”  // The Emoji you want on the button (this can be blank)

        },

        “Ban or Mute Appeal”: {

            “abbreviation”: “BMAPL”, // The abbreviation used in the database and in your unique ticket IDs for each ticket made, custom to this ticket type

            “question_file”: “appeal.json”, // The file name of your question file

            “unique_button_identifier”: “button3”, // The UNIQUE id of this button (It can not be the same as another button)

            “button_type”: “DANGER”, // The Button type (PRIMARY, SECONDARY, SUCCESS or DANGER)

            “button_emoji”: “ℹ️”  // The Emoji you want on the button (this can be blank)

        },

        “Staff Application”: {

            “abbreviation”: “STFAPP”, // The abbreviation used in the database and in your unique ticket IDs for each ticket made, custom to this ticket type

            “question_file”: “application.json”, // The file name of your question file

            “unique_button_identifier”: “button4”, // The UNIQUE id of this button (It can not be the same as another button)

            “button_type”: “SUCCESS”, // The Button type (PRIMARY, SECONDARY, SUCCESS or DANGER)

            “button_emoji”: “🗝️”  // The Emoji you want on the button (this can be blank)

        }

    }

}

Currently the Lang file description isn’t available, but a brief run through can be found below;

All of the default common phrases used through out the bot are found in this file (the content -> handler folder and then lang.json). This allows you to edit all of the phrases used, to match your servers wordings and feel across the tool.

Some phrases utilize different keywords, such as {{ADMIN}}, {{TICKETTYPE}} and {{USER}}. If these are used, the variable is added in place of these place holders to make your phrases more dynamic. You can only use the place holders used in the default phrase for each one. Other place holders WILL NOT work.

NOTE: Just make sure you transfer this across versions!

Cheetos.gg is an advanced Rust cheat detection tool. It is private, and all usage must be on an acceptance basis. In order to obtain access or a key you must make a ticket through the Cheetos Discord where we will manage your application, investigate, and possibly issue a key.

https://discord.gg/2Nay6YaUk5

Q: What do the button types mean in the settings?

A: This basically just sets the color of the button. Here are the different types with their values: https://discordjs.guide/interactions/buttons.html#button-styles (LINK will not work in this setup)

Q: How do I add more buttons to my “create-a-ticket” embed?

A: You need to add a new object into your options.json file found in the content -> handler folder, simply copy one of the existing button layouts and edit it for the new one! You will also need to make a new question file in the content -> questions folder and fill out all the necessary content within. I recommend you use a JSON Validator to make sure you did it correctly.

Q: Can I edit the text and title in the “create-a-ticket” embed to my liking?

A: Yes! It’s the handler.json file in the content -> handler folder. If you want to make a new line, use /n.

Q: I’m verified but the SteamID showing in the embed is wrong?

A: If you are using Simple Link, please make sure you are on the latest version as there was a bug fix for this issue.

The best form of contact is to direct message me on Discord!

Metzey#8740 | https://discord.gg/TVuaAVrFup