Find a way to Check time without needing a message.
Possible Solution:

• Store time stamped commands/actions in a JSON file
• Create a new thread or process to check each command/action (maybe not every tick)
• Run command/action when time stamp is reached
• Remove command/action from JSON file

Permit users with a specific role to execute a command.
Basic solution:

• Save command permissions in a JSON file or hard code permission
• Check users role
• Run command or return "Insufficient permissions"

Spaghetti gets messy, lets not go to far with keeping it this way.

I have found that there is an easier way to doing this. See here for the code that made me realize this

We want to be able to save settings and other things that were modified while the bot was running, so that when it boots back up, it returns to the same state as the one it was shut down in.

current format for ending polls looks bad, let's clean it up to be more user friendly

discord.py is currently going through a rewrite to make the library conform more to the official API; this may mean that official support for the async branch will go out after the rewrite is complete. I would like to see this bot continue to become more useful and featured.

https://discordpy.readthedocs.io/en/rewrite/migrating.html
https://github.com/Rapptz/discord.py/tree/rewrite

calculates time it will be when X amount of ticks have passed
relevant issues:
#4, #17, #1, #3, #5

To solve #26 the bot must know which server the poll, announcement, etc channel is on is the one to respond to. Started findServer(name)
EDIT: Wrong issue

The wiki disagrees with reality, particularly on versioning and branch structure. The problem might be with reality, and not the wiki. Or maybe not. Either way, we should probably fix it.

implement a way to restrict or trigger pings from S.C.S.I. based on server activity/state (i.e. ping me when X is online, do not ping me from X to Y o'clock)

Because a tick is variable and because its nature being quite small, ticks are unreliable for use. If some one want to set a poll that ends in a day the amount of ticks would be ridiculous. And if someone set a tick to represent a time different from another, one may input the incorrect amount of ticks for a desired among of time. I suggest using system to input the desired time, be it elapsed or time until, and have it calculate the amount of ticks; this would however, render !timeto obsolete.

By using quotation marks we can make it easier for users to separate arguments. Commands like !poll and !echo can benefit from this.
E.g. !echo 3 + 6 would output 9 where as !echo "3 + 6" would output 3 + 6

by notating commands with @bot.group we can easily note subcommands with @bot.command

Create a poll system to streamline voting
Basic Solution:

• Create a new poll in a vote/poll channel (or in a temp/inactive channel)
• Track votes according to poll settings (1 vote each user, Yes, No, Abstain by default)
• Tally votes, enact according to vote result and settings
• Log poll and actions to admin/poll log

"!echo XXX" usually returns "<discord.message.Message object at 0xXXXXXXXX>" not "XXX"

References:
#14 #13

relates to #9
should generate a json file with things like filename, poster, comment (text posted with), time/date, and link (to source).

Create commands to add a Temporary channel.
Basic solution:

• Add channel
• Add a poll create command for one hour later that lasts a day (by default)
• Make channel permanent/protected if vote passes, archive and delete if vote fails

Have S.C.S.I. automatically announce channel creation/removal, user promotion, S.C.S.I. updates, events, etc

Discord.py 0.10.0 will happen eventually. We need to ensure scuzzy is compatible with it, or at least that it won't break everything.

have scsi detect any forms of spam and punish the spammer

links, installation, maintenance, etc.

None of the commands log anything. Should we fix that? Probably.

There are a lot of things that will not work on multiple servers. Examples include: BOTMIN role, findChannel(), poll channel, among other things.

Scuzzy saves the backups to the local file system. So whoever initiated the backup will most likely have no way of accessing said backup. That may or may not be a slight problem.

Ok, now how the HECK do you use this? @onionsans

The solution to the multiple server problem broke all the events, and probably some other things as well.

while attempting to resurrect S.C.S.I. executing the main file returns this:

/usr/bin/python3.4 /XXX/S.C.S.I./main.py
  File "/XXX/S.C.S.I./main.py", line 93
    async def timer():
        ^
SyntaxError: invalid syntax

I am currently looking into this

Archive channels in a file or an archive channel

Mentions do not work properly. The person mentioned doesn't get notified about it.

"Sometimes, I can't help but think that I'm not that good. But whenever I look at S.C.S.I's code, it reminds me... that I'm even worse."

The code is a bit of a mess. Or a lot of a mess. Most of it is probably lack of comments. Some of it is undoubtedly comes from the fact that the code is written by 2 people with different ideas about how the code should look. The rest is probably because of said people not taking the time to make their code look exactly as they want it to.

We should probably work on some of that.

I'm thinking about changing the licence from MIT to GNU GPLv3.

Remove channels that are inactive for a preset amount of time
Basic Solution:

• Create a poll to remove the channel in question
• Protect channel if vote fails, archive and delete if vote passes

for funnies and giggles

Automatically log admin actions in an admin log

displays all commands and their syntax, etc.
should not be hard coded into the help function