expand_less TCN
Icon Teyvat Collective Network


arrow_downward Submitting Guide

link Overview

The lifecycle of a banshare is as follows.

upload Submit

A banshare is submitted to /banshare. It is posted to #ban-share-logs and reviewed by observers.

published_with_changes Publish

Once it is approved, an observer will publish it and it will be posted to all TCN servers that have banshares set up. The bot will also automatically ban the user(s) in servers where that is enabled.

unpublished Rescind

We strive to avoid this from happening, but if a banshare is found to be invalid, we will rescind it with a reason and perform a post-mortem to see why a faulty banshare was approved.

This may also happen if the user's behavior improves and we retroactively agree to un-banshare them.


When the bot performs automated actions, either through auto-ban or the ban button, it will log the action in your logging channel if you set it up. Here's what the log message looks like

example banshare bot log

This is probably most appropriate for whatever channel your mods use commands in instead of your mod action audit log, but you can put it wherever you want.

link Setup

To set up the banshare system, first invite the bot using this link.


You will need to grant the bot read+write access to your banshare channel, and if you want logging for automated actions, to that channel as well.

  1. Use /banshare post here in your banshare channel. To disable banshares, use /banshare post none.
  2. Use /banshare log here in your logging channel (optional). To disable this, use /banshare log none.
  3. The ban button is enabled by default and allows members with the Ban Members permission to execute the banshare more easily. If you want to disable this, use /banshare ban-button to turn it off (or back on).
  4. To enable auto-banning (the banshare will be executed on its own if it meets the threshold), use /banshare autoban (see below for what the severities mean).
  5. If you use Daedalus, you can use /banshare daedalus-integration to enable/disable the integration, which allows the banshare bot to automatically add auto-bans and button bans to the targets' user history.

link Severity

Banshares are categorized into three levels of severity plus an extra special category. These are not very strictly defined, and observers can adjust the severity before or after publication. Here are our guidelines. These do not matter for anything other than auto-banning, and do not reflect how "bad" we think the user is.

keyboard_arrow_up P0 (Critical)

The offense is extremely severe and all servers should immediately ban them for safety.

For example, a user spamming NSFW/NSFL content should be P0, as this not only violates all servers' rules but also Discord ToS and constitutes an immediate and grave threat to member safety.

Hacked raid accounts posting scam links should be P0, as the offense is not really that severe, and the potential harm is not as large, but it is because they are likely to become a nuisance in many other TCN servers.

remove P1 (Medium)

The offense is somewhat severe and the majority of, if not all, servers will likely want to ban them.

For example, a user using slurs enough times to be banned following a reasonable amount of warnings (i.e. they are aware that what they are saying is wrong, or it was clearly malicious from the beginning) will likely be P1, as this will violate all servers' rules and most will just immediately ban them unless the user has positive contributions in their server and they might be given a last chance there.

keyboard_arrow_down P2 (Low)

The offense is not extremely severe and some servers may not wish to ban the user for it. Do note that very minor offenses should not be banshared at all; this is mostly for more nuanced cases of user behavior that many servers will ban them for but some may have different rules/policies.

For example, a user repeatedly attacking different users and stirring up trouble in a server will likely be P2, as some servers may want to pre-emptively eliminate them and some other servers may want to give them a chance and ban them only if their behavior repeats there.

message DM SCAM

The offense is a DM scam. The reason these are a separate category is because some servers do not wish to receive these as some people believe it is futile to try to eliminate the problem by banning bot accounts since there will always be more. However, some servers would still like to receive and ban these cases, so they are not being eliminated entirely; rather, servers will be able to choose whether or not they receive DM scam banshares.

Note that scam spamming within a server would count as P0 and other DM offenses such as harassment would be evaluated separately. This only applies to an account attempting to scam users by DMing scams e.g. steam scams, fake nitro scam links, etc.

link Submitting

To post a banshare, go to this form. All fields should be fairly intuitive, but here is a usage guide for each:

  • IDs: The IDs of the offending users. Please post this as an actual list of IDs. If it is too long to fit in a message, it will be automatically uploaded as a document, but if you paste a link, auto-banning will not function. If it is so long that the form rejects it, then you may need to post a link instead.
    • Once you paste in your IDs, click the "Check IDs" button that appears to fetch all of the user tags to look them over and make sure you are bansharing the right people. If your banshare is very long, this will take a very long time, so you may wish to skip this step in that case.
  • Reason: Summarize why the users should be banned. This is used as the audit log reason for automated bans, so please keep that in mind when writing it and include full details and other notes in the evidence instead.
  • Evidence: Include enough evidence to prove that your reasons are valid and for other mods to make an informed decision on what to do.
  • Server: Choose what server you are bansharing it from. If the incident is not bound to a particular server or not one you staff, you should pick the server where you feel you have your "main/primary" or most prominent position.
  • Severity: This determines if a banshare is automatically executed. See above for information on what the severity levels mean.
  • Urgency: If you check the "urgent" box, this will ping all observers instead of just a few to review it.

If the ID list is very long, you may use Submit Without Validation. Do NOT use Submit Without Checking IDs unless you had to publish a banshare with a link for the ID field and there was no way around it. Skipping the check prevents auto-banning or the ban button from working.

The regular submit option will validate that your IDs all correspond to valid users. Submitting without validation will only verify that the IDs are in the right format, and will still parse them such that auto-banning works.

link Policy

link Purpose

The purpose of the banshare system is primarily pre-emptive safety measures. Banshares should be for users who constitute a risk to the TCN, which will be better defined later in this article.

link Banshare Requirements

The following are required of all banshares at a minimum, but meeting these requirements does not necessarily mean a banshare is good enough:

  • Demonstrable Threat: The offense must be severe enough that the user should be considered a threat to any other servers they join, and there must be sufficient reason to believe the user will join TCN servers.
    • A user who spammed NSFW in a TCN server has both committed a severe offense that makes them a threat anywhere (clear disregard for rules, terms of service, and common decency) and there is sufficient reason to believe they may threaten other TCN servers (spammers/raiders often jump between servers).
    • A user who insulted a member (without the use of slurs or harassing language) in a TCN server and was banned for repeat offenses against the same member, but participates in other TCN servers without problems, is likely not banshareable as they are already in other TCN servers but they do not constitute a threat to other servers. If their behavior repeats in other servers then the case is definitely banshareable.
    • A user who spammed NSFW in a random server that is completely unrelated to Genshincord and the TCN is not banshareable. The offense is severe, but there is no reason to believe the user will join TCN servers. If the user is already in several Genshincord/TCN servers, they may be banshareable.
  • Descriptive Reason: The provided reason must clearly explain what the offense was such that if present in a user's ban reason on its own, a moderator should roughly understand why they were banned.
    • "Spamming NSFW images in XYZ Mains" is a good reason.
    • "typical steam scammer" is an acceptable reason.
    • "troll" is not a good reason.
  • Sufficient Evidence: The provided evidence must prove that the offense happened and that all listed users were involved. An exception is provided in case of large raids where it is impractical to attach evidence for every single user. In those cases, trust is placed on the author to ensure that the list of users is correct.