Understanding Filters and Configurations

This page goes over the adjustable filters and configuration settings.

Configuration Settings

Changing Configuration Settings REQUIRES Permit 4.

You can change some of the core aspects of Timmy with +filter modify <number> <boolean>.

Replacing boolean with either True or False

Diagram:

This diagram shows how Timmy operates on the default values.

• If a condition has been met, it'll proceed to return the value you've set for this parameter. Eg; if a user runs a command in CheckDB.guildNone and you've set that value to False, the parameter will return False and the user will not be able to run the command.

• All Checks may not have the right conditions to meet/act upon, for example, if the user is running a command in the main server, CheckDB.externalGuild will pass the context and invoke it to the next check that's in line as the context is not originating from any external guilds.

• If there is no check that fits the command invoke's request, it will automatically return CheckDB.elseSituation which should be set to True.

• Available Options to Change

  • 1

    • Passing in 1 will change CheckDB.MasterMaintenance.

    • When MasterMaintenance is enabled, it locks down the bot and prevents any commands from running (if they are below Permit 4) unless the value has been set back to False.

  • 2

    • Passing in 2 will change CheckDB.guildNone.

    • When guildNone is enabled, it ignores any invocation of commands that originate from Direct Messages. (Eg; Running ping in the bot's DM's while this parameter is set to True will not bring back any results)

  • 3

    • Passing in 3 will change CheckDB.externalGuild.

    • When externalGuild is enabled, it ignores any invocation of commands that originate out of the main server, School Simplified. (Eg; Running ping in the Technical Server while this parameter is set to True will not bring back any results)

  • 4

    • Passing in 4 will change CheckDB.ModRoleBypass.

    • When ModRoleBypass is enabled, it bypass's the public category check and allows Moderators to use any command in public channels. (aka; general chats)

  • 5

    • Passing in 5 will change CheckDB.ruleBypass.

    • When ruleBypass is enabled, it allows NORMAL users to run the command rule in general and public categories.

  • 6

    • Passing in 6 will change CheckDB.publicCategories.

    • When publicCategories is enabled, it strictly ignores any command invoked in a general category.

      • Public Category ID's:

        • PublicCategories = [763121170324783146, 800163651805773824, 774847738239385650, 805299289604620328, 796909060707319838, 787841402381139979, 830992617491529758, 763857608964046899, 808020719530410014]

  • 7

    • Passing in 7 will change CheckDB.elseSituation.

    • When elseSituation is enabled, any other command invocation that gets passed into the bot which does not meet any requirements will be set to True. Consider this to be the final checkpoint for command invocations.

Whitelisted Bot Prefix's

This section will go over how you can add certain prefix's to be whitelisted in #mod-commands.

Changing Bot Prefix's REQUIRE Permit 3 or ABOVE.

This does not manage Timmy's own prefix's, just the one's allowed in the #mod-commands channel.

You can manage prefix's using +prefix add <prefix> or +prefix remove <prefix>and view them all by +prefix list.

Example of how the Whitelisted Bot Prefix System works.

Adding a Prefix

+prefix add %

Explanation: This adds % to the whitelisted prefix's and now any moderator who uses a command that starts with said prefix will not get their message deleted.

Removing a Prefix

+prefix remove %

Explanation: This removes % from the whitelisted prefix's and now any moderator who uses a command that starts with said prefix will get their message deleted.

Listing Prefixes

+prefix list

Explanation: This shows a list of all the whitelisted prefixes.