From 7a099b30b80faec83999ef5e495d0b9bbc95f77c Mon Sep 17 00:00:00 2001
From: Huskydog9988 <39809509+Huskydog9988@users.noreply.github.com>
Date: Mon, 5 Aug 2019 22:29:19 -0400
Subject: [PATCH] Possible oversight

`newThreadCategoryId` is not needed if my understanding of how the config file is read as `categoryAutomation.newThread` and `categoryAutomation.newThreadFromGuild` exist. If this is an intended part of the README.md for backwards compatibility (even though I don't know why it would still be here,) please correct me.
---
 README.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/README.md b/README.md
index 31d22d6..36db6c3 100644
--- a/README.md
+++ b/README.md
@@ -94,7 +94,6 @@ These go in `config.json`. See also `config.example.json`.
 |timeOnServerDeniedMessage|"You haven't been a member of the server for long enough to contact modmail."|See `requiredTimeOnServer` below|
 |mentionRole|"here"|Role that is mentioned when new threads are created or the bot is mentioned. Accepted values are "here", "everyone", or a role id as a string. Set to null to disable these pings entirely. Multiple values in an array are supported.|
 |mentionUserInThreadHeader|false|If set to true, mentions the thread's user in the thread header|
-|newThreadCategoryId|None|ID of the category where new modmail thread channels should be placed|
 |pingOnBotMention|true|If enabled, the bot will mention staff (see mentionRole above) on the inbox server when the bot is mentioned on the main server.|
 |plugins|None|Array of plugins to load on startup. See [Plugins](#plugins) section below for more information.|
 |port|8890|Port from which to serve attachments and logs|