Hello, welcome to InCaptcha! This bot is designed to prevents automated raiders by requiring them to complete a Captcha in their DMs before accessing the rest of the server's activity/content. This bot helps your server from raiders and unwanting activity
Powered By: Eris
This Bot Currently Inspired From Server Captcha Bot
||Sends a new Captcha incase users failed to attempt, DMs are locked, or errors occured|
||Gives the help message|
||Gives the stats of the bot. Currently showing the total servers and users count.|
||Give the list of the remaining required actions to configure.|
||Configure the bot and display the current configuration.|
1st. Invite InCaptcha
!setuplist and check the required actions for you to fully configured the bot.
!config and configure the things that are needed to be set such as the
verifiedRole within the
4th Edit each channels Permissions to denying the
@everyone role or the
unverifiedRole if you had configured one and allowing the
verifiedRole to view and send messages in the channels. You can also did the same thing but instead on the category and sync all channels based with the category.
Firstly, Invite InCaptcha
Ban MembersPermissions as it will mainly be needed in the configuration.
When you first invited InCaptcha, it should look like this when you run
This will display the remaining required actions for you to configure the bot before InCaptcha bot is ready to be used.
You'll need to configure the bot by using
!config and includes with either
verifiedRole. Those 2 are required actions for configuration. The bot also supports additional features which are most recommended and helpful.
Thirdly, Configuring The Bot
InCaptcha completely, it sets up the bot to run automatically on your server.
||Display The Current Configuration|
||The Verification Channel|
||Given The Role When User Has Completed The Captcha|
||Given The Role When User Has NOT Completed The Captcha Yet|
||The Captcha Logs Channel|
||Whether The Bot Will Send The Captcha To User's DMs When They First Joined Or Manually By The User Itself|
||Action For The Bot To Do To Users When They Failed (Ran Out Of Time) The Captcha|
Currently, if you wanted to set up the
waitingRoom, you can type
!config waitingRoom [Channel], replace
[Channel] with the channel's name, and not included with the bracket. So as the role.
And always sure that the
waitingRoom channel is used only a verification channel for unverified users.
To ensure that you configured the bot properly, type
!config to see the current configuration and check the remaining actions with
Lastly, Editing The Permissions
Below method to edit the permissions correctly is the most recommended method from us. Or you can use your own possible way.
Method 1: Within the
waitingRoom and the rest of the channels, you'll need to allow the permissions for
@everyone or the
unverifiedRole to read & send messages and deny the permissions for
verifiedRole. You'll also need to deny the permissions for
unverifiedRole to read & send messages for other channels to keep separate from the unverified users. To do this, you can edit the permissions in each channel or edit the category and sync all channels with the based category.
waitingRoomand not going to involve other users.
!configand mention a channel so InCaptcha can analyze the log channel.
!config logsRoom #captcha-logs
FAQ. Please read these below before you take some actions to report any issues.
This is when the
waitingRoom is helpful. They'll get pinged by the bot there and temporarily requesting for the user to turn on their DMs.
Go back & scroll up at the Configuration Setup section for a full-guide.
Whenever a user failed a Captcha, they are told to run & obtain a new one by running
!verify at the
waitingRoom channel. As the bot has a new feature whether to kick, ban or ask the user to obtain a new captcha (default settings) without being kicked or banned users, this can be different in each different server.
Nope, all users will get a unique Captcha generated by the bot randomly. Sending the same Captcha will just ruin the security.