# Moderator Role #### Welcome to the Moderator Team! First off, congratulations on joining the team! We know starting out can feel overwhelming, especially after going through the onboarding process and your first test ticket but don’t worry, we’ve got you covered. This guide will walk you through everything you need to know about handling tickets, monitoring the Discord, and understanding logs. **Your Role as a ****Moderator**** Team Member** Your main responsibility is to assist with **tickets**. This means: * Being the **first point of contact** for players needing support. * Greeting players as soon as a ticket is opened. * Renaming tickets using the command: `$rename ticketissue-ticketnumber`. * Watching clips of reported rule breaks and providing the Admin team with a clear and accurate summary of what happened. In addition to tickets, you’ll also play a crucial role in **keeping our Discord community positive and welcoming** by ensuring that all channels remain clean, respectful, and non-toxic. If you ever have questions about a ticket, feel free to tag a Senior Moderator or Admin in **#ticket-discussion** for guidance. For a step-by-step breakdown of how to handle tickets, be sure to check out **Ticketing How-To’s**. We’re here to support you every step of the way, and we’re excited to have you on board! #### HANDLING REPORTS AND REVIEWING LOGS When handling reports, it's important that we have clear and valid evidence. **All submitted clips must be at least two minutes long and include sound for context.** The only exceptions to this rule are reports involving **F8 quitting, exploiting, or slurs**. **Step 1: Requesting a Clip & Renaming the Ticket** Once a player submits a report, start by politely asking them to provide a clip. At the same time, rename the ticket using the `$rename` command. For example, if the report is for **VDM**, you would type: ``` $rename vdm 0012 ``` Make sure the numbers at the end remain unchanged. The renamed ticket will now appear under the **Support and Reports** category. **Step 2: Reviewing the Player’s Response** At this point, the player will typically respond in one of two ways: * **If they don’t have a clip:** Politely inform them that per policy, a two-minute clip is required for all rule break reports. Without proper evidence, we are unable to take further action. * **If they provide a clip:** First, check that the clip meets the required two-minute length and includes both in city and mic audio. If it does, watch the clip carefully to confirm that the reported rule break actually occurred. **Step 3: Identifying the Rule Break & Player Involved** As you review the clip, focus on two key things: 1. **Confirming the rule break** – If VDM is evident, type **“Confirmed VDM”** in the ticket. 2. **Identifying the player responsible** – Look for their **in-game ID** within the clip. For example, if the clip shows the ID **147**, you’ll need to find out who this player is. To do this, go to the **Platinum Logs Discord** and search: ``` in: joinleave-logs 147 ``` The most recent log entry will tell you if the player is currently in the city: * **A green “Loaded” bar** means they are connected. * **A red “Dropped” bar** means they have disconnected. Once you've identified the player, copy their license and paste it into the ticket. Next, ping an Admin to review and move the ticket to the Admin section. From there, the Admin team will take over and handle the final steps. *** #### **Understanding & Reading Logs** A key part of your role as moderator is learning how to read logs. Logs track almost everything a player does within the server, from **joining or leaving**, to **deaths, item usage, and inventory transactions**. In some cases, you may need a **Moderator or higher** to check TX Admin logs for specific details, such as **death logs**. To search logs, use the format: ``` in: [log-channel] [search-term] ``` **Example: Investigating a Missing Item Report** A player submits a ticket stating their **oxy disappeared from their trunk** after parking their car in a garage. Since this isn’t something that can be clipped, we’ll need to check logs. 1. **Find their Citizen ID** * Search for their **Discord ID** in: `joinleave-logs` 2. **Check Trunk Logs** * Copy their **Citizen ID** and search in: `trunk-glovebox-logs` 3. **Analyze the logs** * If the last recorded log shows the oxy was **placed into the trunk but never removed**, then it should still be there. In this case, we can assume the item was lost due to a server issue. If reimbursement is necessary, ping an **Admin,** after moving the ticket to their section and request them to **reimburse 10 oxy**. *** #### **Log Breakdown & Common Scenarios** Logs can sometimes be tricky to interpret, but with practice, they’ll become second nature. Below, you’ll find a guide to help break down common log entries and what they mean. If you ever feel stuck or need guidance, don’t hesitate to reach out to a **Moderator or Admin** for help. Your role is essential in keeping things fair and organized, and we appreciate everything you do! #### Log Example Logs can sometimes be tricky to interpret, so here’s a guide to help you navigate them. Below are some of the most common log examples you’ll encounter.