This post will go over what commands are exclusively available to the staff team so that you, the user, know what you can expect from us. They are listed in order of utility for the user, and each commands provides a little explanation.
This section goes over commands users benefit from knowing the staff team can use.
The move command grants us the ability to move a thread between categories with different permissions. E.g. If a user requests so, we can move a thread to our Sensitive category, which only directors have access to. This is particularly useful if a user has a sensitive query they for whatever reason doesn’t want the whole staff team to see. It should be emphasised that every thread to the staff team regardless of who handles it is fully confidential.
The logs command allows us to easily pull up past threads made by the same user. This allows us to verify previous interactions with users. Every interaction, edit, message sent, deleted, etc. is stored securely.
The contact command allows the staff team to contact other users about issues. E.g. we can deliver the results of, say, an invocation of the harassment rule directly to the user in an official manner.
The block command allows the staff team to bar users from communicating through the only acceptable medium, rendering users helpless. This is the last resort.
The unblock command undoes the previous block command.
The sudo command allows mods to create webhooks that imitate users with custom text. The dead giveaways of a “users” post being a sudo’d webhook is that it has the tag next to its name and that upon clicking its name it does not reveal a profile.
The remove topic command can be used if and only if there is no other way to conclude a topic without adding more people to the room to conclude.
The private command mutes everyone in the room and prevents anyone from setting topics or becoming debaters. To be understood in conjunction with the unlock and public command.
The unlock command is used to allow specific users in private rooms to set topics and become debaters. To be understood in conjunction with the private and public command.
The public command is used to turn a room from private to public. To be understood in conjunction with the private and unlock command.
The repair elo command calculates someone’s elo again. Sometimes small breakups in our connection prevent the system from calculating someone’s elo. This command allows us to manually do that if the user e.g. does not have their rank role.
The lockdown command locks down the entire server from use. This is used when we roll out updates to the bot, but can also be used in our other moderation systems fail.
The bar command can be used to prevent a user from attaining citizenship. It is listed here so that users know that they can lose their citizenship if they abuse their permissions.
The unbar command allows barred users to attain citizenship again.
The isolation command detains the specified user to a room where neither public can see them, nor they see the public. If someone is engaging in mass spam in people’s DMs and using the sever as a member list we can block them from being able to do so.
The free command removes the specified user from isolation.
The supermute command is like isolation, except it removes the users’ ability to see any channel. Additionally, this command works on staff, so there is an effective way to handle rouge mods.
The unsupermute command removes the specified user from being supermuted. Can only be used by directors.
This section goes over what commands staff benefit from knowing how to use
This section will only list the most useful ones we commonly use.
The help command grants you a list of all commands. The help command can also be used like
>help commandname to tell you more about the specified command.
The reply command replies and reveals the user that replied.
anonymous reply (ar)
The anonymous reply command replies without revealing the replier’s specific identity, only their title. E.g. Director or Moderator.
The note command allows us to note and officially include evidence gathered by moderators in the thread itself, hidden from users. This shows up in logs.
The help command allows you to find out more about each command by typing
The purge command allows its user to remove multiple messages based upon specific parameters like who sent it, what it contains or how many messages.
The warn command adds a warning to the user’s server profile through Dyno. On our server, it is set to automute the user every three warns.
The warn id command allows us to fetch the warnings of a user and grab the warning ID for the delwarn command.
The delwarn command removes the specified warning from the user using the warnid.
The mute command applies the muted role to the specified individual for the specified time and reason. The muted role is a sticky one, and will be re-added upon server leave and rejoin.
The unmute command removed the muted role from a user. If a user has triggered CensorBot three times in an hour they will be muted indefinitely, and will upon request need to have it removed.
The modlogs command allows us to see all the cases noted on a user’s profile on our server. That means all mute, warning, and isolation cases.
The case command allows us to get a response with only the case mentioned.
The reason command allows us to change or add a reason to a specific case.
The note command allows us to make a note on a person’s profile without giving them a warning.
The notes command allows us to view the notes we’ve added.
The ban command bans a user from the server with possible time and reason. Only directors can use this command.