I hate having to do this, but I need to make the GUI nice this run about, time to get to know swing better.

I have to actually make the main GUI.

Planned events:

• UserJoinEvent
• UserPartEvent
• UserChatEvent

The listener system will be usable by plugins to listen for these events then execute code when they happen.

This is to allow plugins to easily register commands in their onEnable() method they would call Bot.getInstance().getCommandManager().registerCommand(Command command)

There might be memory leaks that I've been unable to find. If others find them please consider forking and fixing it then making a PR.

Currently the connection constructors are goldilocks'd to my needs, I need to make them cover all possible occurrences so that people will be happy with it's writing.

All important data will be stored here.

name - The bot's twitch username.
oauth - The auth key connected to said twitch username.
channel - Which channel to write into the text field as the default.
console - Wether or not to display the developer console.
disabled commands - A list of the disabled commands (listed via name)

Allow developers to make their own configuration files with ease just by using an object called Config or something.

currently it is horribly coded and probably eats tons of CPU as a result, need to make it less garbage

Currently the user needs to enter an auth key into the config.yml file manually, this is an issue considering the fact that the user is never told this, and they are left to attempt to figure out why the bot won't let them connect. On top of this addition there needs to be something that alerts users to the absence of an account for the bot to use.

occurred to me that some people might want to help out, and know what the code does without spending much time looking through it and getting to know it, time to comment everything.

In the options menu the twitch account setting panel isn't working as intended, it says success when there wasn't a success and sometimes it doesn't even log in.

Yet another UI overhaul, was thinking of making it with HTML, that might prove to be difficult.

Having users check for updates can be a hassle, so have the bot check for updates + automatically download the latest version and then relaunch.

I have literally no clue as to why I made versioning the way it is currently, I'll get to work on fixing that.

• Plugin annotation requires a string array component called "dependancies"
• Have the loader parse the array and chose to load the dependancies before that plugin.

this is caused by premature shutdown, makes it impossible to close the bot.
Attempt to close the bot while it's loading plugins.

Due to windows file locking the jar file cannot be deleted an in turn cannot be overwritten by the updater. I need to make a separate updater.jar for windows users.

Just a rehash of #22 using nicer wording in title

When I begin to add more and more to the main configuration file I'm going to need to make a way to update the configuration without losing all of the user's saved data.

Users should be able to change which directory will be used as the home directory for all Dragon Bot purposes. Make sure that once you change the directory it copies all dragon bot related files to the new destination, then deletes them in the old destination.

Make sure that this plugin loader takes advantage of class-level annotations for loading the plugins instead of just reading a .yml file for the main.

Allow the bot to connect to the twitch IRC chat room.

com.amazonaws.SdkClientException: Unable to find a region via the region provider chain. Must provide an explicit region in the builder or setup environment to supply a region.

Allow developers to use a provided scheduler to schedule repeating tasks and delayed tasks to run.