Skip to content

Commit a28f775

Browse files
authored
Update README.md
edited ticket example, and added some final categories which may need to be added to at a later date
1 parent 0ff5a2f commit a28f775

File tree

1 file changed

+27
-5
lines changed

1 file changed

+27
-5
lines changed

README.md

Lines changed: 27 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -226,12 +226,15 @@ The bulk of the ticket will be case specific - that is to say, entirely dependen
226226

227227
Let us take an example of a user with an NSFW bio, thereby violating our Server Code for Conduct - §1.1. Your ticket body should be structured similarly to the following:
228228

229-
"It has come to my attention that your bio contains an NSFW element - this violates our server Code of Conduct - Rule 1.1. Our server contains a large minor contingent, and therefore we ask that members have bios appropriate for all ages. Please rectify this in order to remain a part of our community."
229+
`We've noticed that your bio contains an NSFW element - this violates our server Code of Conduct - Rule 1.1. Our server contains quite a lot of minors, and therefore we ask that members have bios appropriate for all ages. Please change this as soon as you can in order to remain a part of our community.`
230230

231231
As shown, your body should:
232-
a) Address what you're not happy with
233-
b) Reference which area of the Code of Conduct they are in violation of
234-
c) Point towards how they can rectify their actions, and subtly hint as to what could happen should they choose not to
232+
233+
a) *Address* what you're not happy with
234+
235+
b) *Reference* which area of the Code of Conduct they are in violation of
236+
237+
c) *Point* towards how they can rectify their actions, and subtly hint as to what could happen should they choose not to
235238

236239
### 3.2.3 Closing Your Opening Message
237240
With the conclusion of the body - rejoice! The hardest part is over. Wrapping up your opening statement, is simple.
@@ -282,8 +285,27 @@ Happy ticketing!!!
282285
# 4. Conclusion
283286

284287
### 4.1 Recap of Key Points
288+
To summarise, to be a successful Moderator on our team, it all boils down to this:
289+
290+
* Moderation is about fostering a positive, welcoming community. Your role is to maintain a positive environment, mediate conflicts and uphold our ethos without bias.
291+
292+
* Appreciate the chain of command. While everyone's voice matters, its alright to escalate issues to senior moderators or administrators and seek help from your colleagues!
293+
294+
* Use the Code of Conduct as your guide. Ensure consistency in enforcing rules and always reference the relevant rule when justfiying moderation actions.
295+
296+
* Handle issues professionally. Avoid using moderation actions as jokes or without proper context. Transparency and accountability are key.
297+
298+
Whether in chat or tickets, be clear, fair, and open to discussion. Stay adaptable, the community will evolve and so you need to be always ready to adapt on the fly.
299+
285300
### 4.2 Continuous Learning and Improvement
286-
### 4.3 Importance of Upholding Community Values
301+
Nobody is a complete package - and we never stop learning.
302+
Take it in your stride, and be the best that you can be.
303+
304+
### 4.3 End
305+
Moderation is challenging yes, there's no doubt about it.
306+
But, is it rewarding? Absolutely.
307+
308+
Enjoy your time as part of our family, and we hope you take the lessons you experience throughout your time here and continue to grow not only as a moderator, but as an individual too.
287309

288310
---
289311

0 commit comments

Comments
 (0)