Ban sync

Link your servers so a ban in one is applied in all of them. Each server keeps its own settings.

Setting it up

Only server owners can create, join or leave a group, because another server's bans will reach their members.

,bansync create My Network
,bansync join ABCD-EFGH-JKLM

The first line, run by one server's owner, starts a group. Gim sends the owner the join code in DMs (open your DMs if it can't). ,bansync code sends it again and ,bansync code reset makes a new one.
The second line, run by another server's owner, joins it. Gim deletes that message so the code doesn't stay in the channel.
A group holds up to 10 servers, and a server can be in one group.
Bans each server already has stay where they are: only new bans are shared.

Each server's own settings

Setting	Default	When it's on
`,bansync share`	on	Bans in this server reach the others
`,bansync receive`	on	Bans from the other servers are applied here
`,bansync unbans`	off	Unbans go out, and an unban in the server a ban came from lifts it here too

Each one takes on or off and only changes this server. You can also switch them on the dashboard under Moderation; only the server owner can change them. ,bansync shows the group, its servers and this server's settings to anyone with Manage Server.

What gets shared

Every ban: through Gim (,ban, antinuke, filters…) and done directly in Discord.
Tempbans stay tempbans, for the time the original has left.
A shared ban is a normal ban in each server, made by Gim: it gets a case and a mod log entry with the reason Ban sync from <server>: <reason>.
A ban that came from the group isn't shared again, so nothing bounces around.
Unbans only travel between servers that both have unbans on, and only lift bans that came from the server that unbanned. A hardban is never lifted by ban sync.

If Gim was offline

Bans and unbans made while Gim was restarting or offline are caught up when it comes back: it reads each server's audit log from where it left off (up to 200 of each per server) and shares them in the order they happened. That needs Gim to have View Audit Log in the sharing server; ,bansync marks servers where it doesn't.

Stats

,bansync (and the dashboard) shows how many bans this server shared and received, all time and in the last 30 days, how many synced bans are still in place here, and how many bans the whole group synced in the last 30 days.

Managing the group

Command	Does
,bansync leave	Stops sharing. If the owning server leaves, the next server to have joined takes over
,bansync kick	The owning server removes another server by its ID (shown in bansync)

If one server bans a lot of people in a few minutes (more than 30 in 10 minutes), its newest bans stop being shared for a while and the group owner gets a DM. That stops a hacked or rogue server from banning everyone everywhere; remove it with ,bansync kick if it isn't expected.

Common problems

A ban didn't reach a server. Gim needs Ban Members there, and it can never ban the owner or anyone with a role above Gim's. Check that server has receive on and the original has share on.
An unban didn't travel. Both servers need unbans on, and only the server the ban came from can lift it elsewhere.