1. Getting Started with PiBot!

To invite PiBot to your guild (server), you should refer to this link and then select your desired server and finally click "Authorize" as shown in the below image:

PiBot will now be in your server, you should now give relevant permissions to PiBot to perform certain actions - the following permissions are relevant to PiBot:

Read Messages - this is so PiBot can listen to message commands
Send Messages - this is so PiBot can send messages in response to commands
Embed Links - this is so PiBot can send embedded messages for a cleaner look and feel
Use External Emojis - this is so PiBot can make messages look cleaner with the use of custom emojis
Add Reactions - this is so PiBot can add reactions in the p.help command to navigate pages
Manage Messages - this is so PiBot can delete filtered messages in the p.filter command
Manage Channels - this is so PiBot has the ability to mute members upon use of the p.mute, p.unmute commands or auto mod
Kick Members - this is so PiBot has the ability to kick members upon use of the p.kick command
Ban Members - this is so PiBot has the ability to ban members upon use of the p.ban command or auto mod
View Audit Logs - this is so PiBot can read audit logs for the p.setauditlog, p.antiraid commands
Manage Roles - this is so PiBot can add roles to members for the p.autorole and remove roles if p.antiraid is triggered

2. Configuring Your Server with PiBot!

PiBot will only work however you want it to work, by default all configuration is disabled and you will need to enable it yourself. Here are details of the configuration commands and how you can set them up:

Anti-Raid - this is a function which detects if a server moderator or admin is performing abusive or repetitive actions such as mass banning, mass kicking, mass role deletion or mass channel deletion. Upon detecting this frequent activity, PiBot will remove ALL of their roles which is possible to remove depending on permissions. If you do setup this feature, we strongly advise you make the PiBot role the highest role to ensure maximum protection...

Anti-Raid comes in three different protection levels (1, 2 and 3), these are Minimal Protection, Regular Protection and Extreme Protection... We advise you use the 2nd setting naturally and the 3rd setting if you are extra protective although this may cause false positives.

You can enable Anti-Raid by typing p.antiraid 2 which will set this to Regular Protection. You can disable Anti-Raid at anytime by typing p.antiraid 0. Refer to the image below:

If and when Anti-Raid is triggered in your guild, you (the owner) will receive a direct message from PiBot looking similar to the below image:


Anti-Spam - this is a function which currently only detects for mass or spam mentions (a mention is a ping in slang), if your server members dislike being pinged often then this feature will help out a lot. If you enable this feature, PiBot will listen for mass / spam mentioning and take action by muting the member in which you can unmute the member anytime using the p.unmute command, for more information on unmuting, run the p.help unmute command.

Anti-Spam comes in three different protection levels (1, 2 and 3), these are Minimal Protection, Regular Protection and Extreme Protection... We advise you to use the 2nd setting naturally and the 3rd setting if members try bypassing the Anti-Spam feature although this may cause false positives.

You can enable Anti-Spam by typing p.antispam 2 which will set this to Regular Protection. You can disable Anti-Spam at anytime by typing p.antispam 0. Refer to the image below:

Anti-Alt - this is a function which detects new accounts joining your guild or fairly new accounts with default avatars, this is to prevent members bypassing a ban for example. If you enable this feature, PiBot will listen for new accounts and take action accordingly by either muting them or banning them (depending on the protection level and severity). If they are muted, you can unmute the member anytime using the p.unmute command, for more information on unmuting, run the p.help unmute command.

Anti-Alt comes in three different protection levels (1, 2 and 3), these are Minimal Protection, Regular Protection and Extreme Protection... We advise you to use the 2nd setting naturally and the 3rd setting if you believe your guild is going to get raided.

You can enable Anti-Alt by typing p.antialt 2 which will set this to Regular Protection. You can disable Anti-Alt at anytime by typing p.antialt 0. Refer to the image below:

3. Configuring your Server Logs with PiBot!

Logging will only work when you set it up, by default all logs are disabled. Here are details of the configuration commands you can use to set up your logs with:

Audit Logs - this is a function which will detect delete messages, edited messages, deleted channels, new channels, deleted roles and new roles. This can be good for moderation so you know when members are trying to be sly with breaking any rules.

You can enable Audit Logs by typing p.setauditlog and mentioning a channel with it. For example, p.setauditlog #audit-logs. You can remove your Audit Logs at anytime by typing p.setauditlog null. Refer to the image below:

If and when an event such as a deleted messages, edited message or added channel occurs, an audit log will be posted in the set channel as shown in the images below:




Member Logs - this is a function which will detect when members join and leave your server, it will also include the date the members account was created and how long they lasted in the server (if they leave). This can be good for moderation so you know some basic information about a member when they join.

You can enable Member Logs by typing p.setmemberlog and mentioning a channel with it. For example, p.setmemberlog #member-log. You can remove your Member Logs ay anytime by typing p.setmemberlog null. Refer to the image below:

If and when an event such as a member joining or leaving occurs, a member log will be posted in the set channel as shown in the images below:



Moderation Logs - this is a function which will send logs to a channel when you issue warns, kicks, bans, mutes and unmutes with PiBot. This is useful for knowing members previous infractions with reasons, case numbers and which moderator issued them.

You can enable Moderation Logs by typing p.setmodlog and mentioning a channel with it. For example, p.setmodlog #mod-log. You can remove your Moderation Logs at anytime by typing p.setmodlog null. Refer to the image below:

If and when an event such as a mute or warn happens, a moderation log will be posted in the set channel as shown in the images below:




4. Custom Commands

Custom Commands are a brand new feature on PiBot for you to make your own very basic commands in your guild. You can add commands with variables inside them, the variables available to you are as follows:

VARIABLE OUTPUT
{sender}

@Stefano#0001

{username}

Stefano

{discriminator}

0001

{guild}

another test guild

{mention}

@Algorithm#0001

{mentionusername}

Algorithm

{mentiondiscriminator}

0001

{args}

some text after the p.command


Custom Commands come in the following syntax as shown in the image below:

To create a custom command, use the following syntax:

p.com -add exampleName example output

To remove a custom command, use the following syntax:

p.com -remove exampleName

To view all your custom commands, use the following syntax:

p.com -list

You can use a variable in your command output, for example, to post your server name, use the following syntax:

p.com -add serverName This is: {guild}

Here are some images to demonstrate the above command: