+- No Cancer RP (https://www.nocancerrp.com/Forums)
+-- Forum: Official Documents (https://www.nocancerrp.com/Forums/forumdisplay.php?fid=3)
+--- Forum: Staff Applications (https://www.nocancerrp.com/Forums/forumdisplay.php?fid=8)
+--- Thread: Mod application (/showthread.php?tid=3263)
Pages:
1
2
Mod application - Nemi - 07-27-2024
What is your steamid?(this can be found here: https://steamid.xyz/)
STEAM_0:1:220689336
What is your discord @ ?
ariesthecryptid
How many hours do you have on No Cancer RP?
2 days
Do you have a working mic in-game?
Yes
How old are you?
24
Have you ever been staff on a gmod server before?
no
If you answered yes to the last one, which server and what rank?
What special skills do you posses that will make you more qualified than the other applicants?
I'm really good at communication
Do you have experience with SAM?
no
Do you have any other significant commitments? (such as a job or school)
Work
What times EST(server time) can you be active on an average day?
Anytime after 6:30 PM EST
Scenario
Player A, a new player RDM's a returning player, Player B. Player B calls for a sit. After teleporting them to a sit room, what do you do?
[*]Identify the Issue: Begin by asking Player B to explain what happened. They should provide details on the incident, including the location, time, and any relevant context.
[*]Gather Evidence: Check if Player B has any evidence, such as screenshots or video recordings, that show the RDM incident. If not, you may need to rely on their description and witness statements.
[*]Speak to Player A: Teleport Player A to the sit room and ask for their side of the story. Player A may not fully understand the rules yet, so it's essential to be clear and patient.
[*]Assess the Situation: Determine whether Player A’s actions constituted RDM according to the server rules. If Player A is genuinely new, they might not know the rules thoroughly, which can be taken into account.
[*]Explain the Rules: If Player A did RDM, explain to them why their actions were against the server rules. Provide a clear explanation of what RDM is and why it’s important to follow the rules to ensure fair gameplay.
[*]Apply Consequences: Based on the server’s policies and the severity of the RDM, decide on an appropriate punishment. New players might receive a warning or a minor penalty, while more severe cases might warrant a temporary ban or other disciplinary action. Make sure the punishment is proportional and educational.
[*]Educate and Prevent: Use this opportunity to educate Player A about the server rules and the importance of following them. Encourage them to read the server rules and offer resources or guidance if available.
[*]Follow Up: Once the sit is resolved, make sure to document the incident and any actions taken. This helps maintain transparency and track repeat offenders or issues.
[*]Reassure Player B: Thank Player B for reporting the issue and reassure them that the situation has been handled according to the rules. This helps maintain trust in the server's moderation.
Player A claims Player B is propblocking, but you do not see any props. What do you do?
[*]Verify the Claim: Ask Player A for specific details about the propblocking incident. Find out when and where it happened, and request any evidence they might have, such as screenshots or video recordings.
[*]Check the Location: Go to the location where Player A reported the propblocking occurred. Sometimes props might be removed before you arrive, so inspect the area thoroughly.
[*]Review Player Actions: Ask both Player A and Player B to explain their actions around the time of the reported incident. It’s possible that Player A might have misunderstood the situation or that there was a temporary issue with props not rendering correctly.
[*]Look for Patterns: Determine if there are any other reports or patterns of behavior involving Player B. If Player B has a history of propblocking, it might provide context for the current situation.
[*]Check Server Logs or Tools: Check logging tools or administrative commands to track prop usage, use them to check for any recent prop activity that might not be visible in the current state.
[*]Investigate Context: Sometimes, players might accuse others of propblocking due to misunderstandings or in-game conflicts. Assess whether the claim might be related to another issue, such as a disagreement or roleplay scenario.
[*]Educate Both Players: Regardless of whether propblocking is confirmed, remind both players of the server rules about prop usage. Explain how propblocking can impact gameplay and encourage fair play.
[*]Document the Incident: Record the details of the sit, including the claims made, the evidence reviewed, and any actions taken. This helps maintain a clear record of the incident in case of future disputes.
[*]Take Appropriate Action: If no evidence of propblocking is found and it appears to be a misunderstanding, explain this to Player A and advise them to provide more substantial evidence if they encounter similar issues in the future. If Player B has behaved inappropriately or there’s a pattern of behavior, address it according to your server’s rules.
10+ People are all saying the same person is massrdming, but in the logs you only see he killed one person. What do you do?
[*]Investigate Reports Thoroughly:
- Gather Detailed Information: Ask the players who reported the mass RDM to provide detailed accounts of the incidents. Request the exact times, locations, and any evidence they might have, such as screenshots or videos.
- Review Extended Logs: Sometimes the initial logs might not show the full picture. Use server tools to check for any additional logs or historical data that might show more kills or incidents by the accused player.
- Corroborate Reports: Cross-reference the reports from different players to identify any patterns. If multiple players are reporting similar behavior, there may be a common factor or time period during which the RDM occurred.
- Check for Other Players: Sometimes victims of mass RDM might not have reported every incident. Verify if there are additional victims who haven't come forward.
- Get Their Side: Ask the accused player to explain their actions. They might have a different perspective or might admit to other incidents not yet logged.
- Look for Bugs or Glitches: Ensure there aren’t any server issues causing discrepancies in the logs. Sometimes, server bugs can result in incomplete logging of events.
- Review Recent Play: Look at recent activity and interactions around the time of the reported mass RDM. This can help identify if the player was involved in any unusual or disruptive behavior.
- Increase Surveillance: Temporarily monitor the accused player more closely for any further violations. This can help catch any ongoing issues that might not have been captured in the logs.
- Keep Records: Document all the reports, evidence, and your investigative process. This helps ensure transparency and provides a clear record in case the situation escalates or if further action is needed.
- Issue Warnings or Penalties: Based on the investigation, take appropriate action. If there is sufficient evidence of mass RDM, apply the necessary punishment according to your server’s rules. If evidence is lacking but suspicion remains, consider a warning or increased monitoring.
- Inform Both Parties: Update both the reporting players and the accused player on the outcome of the investigation. Clear communication helps maintain trust in the moderation process.`
A player calls you a shit admin, he also claims he has proof against you and threatens to report you on the forums. What do you do?
[*]Stay Calm and Professional:
- Do Not Engage in Hostility: Avoid responding with anger or defensiveness. Maintaining a calm and professional demeanor is crucial in resolving the situation effectively.
- Listen and Record: Acknowledge the player’s concerns and take note of their specific grievances. Let them know you take their feedback seriously and will review the situation.
- Ask for Proof: If the player claims to have evidence against you, request that they provide it. This could be screenshots, recordings, or any other documentation related to their complaint.
- Examine the Claims: If evidence is provided, review it thoroughly. Check if there is any validity to the claims and if any actions you took might have been inappropriate or misunderstood.
- Evaluate Your Actions: Reflect on your actions in the context of the server rules and guidelines. Ensure that your conduct aligns with the server’s standards and policies.
- Respond Appropriately: If the investigation reveals that there were issues with your behavior or decisions, address them constructively. Apologize if necessary and explain how you will correct the situation.
- Update the Player: Inform the player about the outcome of your review. If no wrongdoing is found, explain your findings and how you handle such complaints. If mistakes were made, outline the steps you’re taking to improve.
- Follow Server Protocol: If the player decides to report you on the forums or through other official channels, follow your server’s protocol for handling formal complaints. Provide any relevant information or evidence to support your case.
- Keep Records: Maintain detailed records of the interaction, including the player’s complaint, the evidence provided, your investigation, and your response. This documentation can be useful if the complaint escalates.
- Consult with Senior Admins: If the situation is complex or you feel it could escalate, consult with senior admins or moderators. They can provide guidance and assist with resolving the issue.
- Reflect and Improve: Use the feedback as an opportunity for self-improvement. Ensure that you continue to adhere to server rules and standards, and take any constructive criticism to heart.
By handling the situation with professionalism and transparency, you help maintain trust and credibility within the community, and ensure that any issues are addressed fairly and effectively.
RE: Mod application - Unc Freaky - 07-27-2024
+Rep W application
+Rep W Funny
RE: Mod application - ItsAus10 - 07-28-2024
+rep Cool guy
+rep active on the server
+rep detailed app
RE: Mod application - Mr Meanie - 07-28-2024
-rep Look like AI did a good job.
RE: Mod application - yoog ☆ - 07-28-2024
+active
+mature and pretty chill in game
is this fucking AI generated though? lmao
RE: Mod application - Darp - 07-28-2024
+rep no bad interactions with this guy
-rep this shit do look AI generated ngl chief
RE: Mod application - Oreo - 07-29-2024
+Rep Nemi is cool asf
-Rep Ai generated?????
+Rep Very Active
+Rep Never had a bad interaction with this dude
RE: Mod application - Spectre - 07-30-2024
+rep Active
+rep Positive interactions, and great overall player
-rep LLM/AI
Don't submit applications written mostly by a generative model. We are here to see if you are ready, not if text scraped from the internet and predicted by code is. Using these applications for help writing things you already know or as a reference is one thing, but just pasting from AI is another.
RE: Mod application - Bradysgaming - 08-06-2024
ban this guy from mod apps NOW!!!!
(-rep goofy ass pfp -rep def fucking ai)
RE: Mod application - JJuce - 08-06-2024
