Documentation updates.

Pushing changes and merging branch for a v3.0.1 patch.
Not updating further this time as call-backs won't work.

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## Minor Updates in Version 3.1
+## Minor Updates in Version 3.0.1
 
 - Re-builds the Docker image to use a `python:slim` base instead of `python:buster`, reducing the footprint of the image to a quarter of its previous size.
 

README.md

@@ -219,5 +219,6 @@ Programming around this will need a further layer of complexity, involving flags
 
 I have set the member verification prompt to use a global listener to avoid a situation where it creates several backlogged processes when multiple people post sign-ups at the same time.
 This should also mean that the sign-up prompts should persist over reboots.
-The best possible way of setting this up is probably using functions to dynamically set up and remove component call-backs.
-Also components do not need to all have unique names, just unique names in the message they are part of.
+Other developers for Discord Components recommended the use of dynamic call-backs, however these do not persist after reboots so are not suitable for this purpose.
+Discord will need to make substantial API updates in the future for rolling out the Threads feature.
+The bot will need updating again then.

TODO.md

@@ -8,4 +8,4 @@
 
 - [ ] Add support for Discord Threads following Discord Py library update
   - [ ] Update permission settings for GMs on game channels to support threads
-- [ ] Change component response architecture to use dynamic callback functions instead of global listeners.
+- [ ] ~~Change component response architecture to use dynamic callback functions instead of global listeners.~~ Not suitable because it does not provide persistence across reboots.