+.
There are ways to assign an alternate call character,
but + will always work.This is how commands are displayed inside help commands and responses.
42 has a set of automatic functions that do not require a command to trigger.
These are all optional and can be set with the correct command, such as using +ayy to disable the bot responding to mentions.
A full list of automatic functionality can be found here.
Bug reports:
Every command within 42 will send a reply, whether that reply is a successful response or an error message.
If a response isn't sent, it means one of two things have happened:
If it is the latter, then it would be greatly appreciated if you could send it to @RocketLanterns
either in DMs or Kiwi Hangout. #reeds-station is designed specifically for reporting bugs.
Alternatively, you could email bugs@rockett.space
And I know 42 has some bugs...
Suggestions:
Is there something you need but don't have or don't know how to do? Head over to the server linked above and ask in #heinrichs-workshop.
If we have a solution, we can tell you there and then, if not, we can suggest a bot or Lan may be able to implement a solution into 42 for you.
42 implements a suite of authority checks to help curb abuse and help server moderators combat spam. There are currently 6 checks:
When a check is failed, 42 will alert the user as to what went wrong and will then start ignoring any more permission errors caused by that user for one minute.
This is to stop botbanned members from spamming "You are botbanned" messages.
Permission levels are non-changable and are defined on a command by command basis.
They exist to stop people using the bot to bypass certain safety features within discord,
such as preventing users without Manage Roles from creating giveme roles so that they can grant themselves roles.
Each command will have its permission level displayed next to the name
Any command not marked with a permission level can be used by anyone.
Rate limits are also fixed by the bot. This stops both spam in servers and stress on the bot herself.
If a command is rate limited, it will be marked so on its help article next to the permission check.
If no indication exists, then the command is not rate limited.
THIS IS NOT AN INVITATION TO START SPAMMING THE BOT. All spamming like this will do is get you or your server sanctioned.
This is the first check that can be set by the server managers via a command.
It enforces a limit to the amount of lines the bot can send to a single non-bot channel within a timeframe, but this is explained in the command's page.
This is the largest amount of control servers have over the bot's usage as it allows them to completely disable commands.
Commands that are toggled will have a [Disabled by server] tag applied to the end of the built in help command.
Users who have any server related permissions are not affected by disabled commands.
Botbans are a servers last level of control, or rather defence. It allows them to stop a given user from accessing any of the bot's commands.
Botbans applied in one server are not respected in any other servers, and unlike her predecessor, 42 will not automatically globalban people with too many botbans.
You cannot botban the server owner or other bots and you cannot botban squas.
In general, botbans only affect command calls, not automatic functions.
Global bans are the absolute last resort for cleaning up a mess. They can only be applied and removed by squaswin and can affect either single users or entire servers.
If a user is global banned, they will not be able to use 42's commands in any server or private channel.
If a server is global blocked, the bot will refuse to join the server and if she does get on the server, she will leave at the first opportunity.
While 42 has a lot of functionality that can be sustained with only Read Messages, Send Messages and Embed Links,
she also has a lot of features that require elevated server permissions.
Here I'll list each elevated permission that 42 requests, and the commands and/or reasons why they are requested.
Not strictly required, as no functions make any write requests to server configuration.
+info server [Optional] Used to populate page regarding to guild partnership status and features, which are only readable with the Manage Server permission.+giveme Required to assign roles.+giveyou Required to assign roles.+colourme Required to assign roles.+voicerole Required to assign roles.+welcome Required to assign roles.+modlog Used to create new modlog channels and populate the channel topic with default modlog configs.+remove Required to delete messages from other users.+blacklist Required to delete messages from other users.+cleanme Required to delete messages from other users.+cleanup [Optional] Used to access the bulk message delete mode. Required to delete invocation messages from other users.+tag [Optional] Enables use of the +tag hidden subcommand.+kick Required to kick members.+ban Required to ban members.+unban Required to unban members.+softban Required to ban and unban members.+modlog [Optional] Detects and distinguishes kicks from leaves.+modlog [Optional] Attaches an acting moderator and a reason to kick/ban/unban logs.+archive Required to upload chat archive into channel.+cleanme Required to upload chat archive into channel.+tag Required to output content (calculated or raw) of tag when it exceeds 2000 characters or 12 lines of text.+solstice Required to upload output of image command.+entify Required to upload output of image command.+imtb Required to upload output of image command.+schedule [Optional] Uploads image displaying current schedule instead of text-dump.+archive Required to fetch chat messages.+cleanme Required to fetch chat messages.+remove Required to use bulk message delete tools.+cleanup Required to use bulk message delete tools, or to fetch chat messages.+blacklist [Optional] Attaches previous message to blacklist modlog output as context.'user' or 'member' are what is affected.
[command][<whitespace>command<whitespace>]{command}{<whitespace>command<whitespace>}//command//<whitespace>command+remove and +modlog