Rogue threads are completely obliterated now

Added better logic for thread sleeping, better rogue thread stopping, and finally, the shutdown thread stops the scheduler and any remaining tasks. Planning to add a graceful shutdown for scheduling later. (where it stops any new tasks from being created, then waits for any current tasks to be completed for a second or two, and then forcefully shuts down now)
kill the whitespace
actually obliterate rogue threads

Probably not optimal, but it works!
whoops, fixed some stuff

I accidentally included some stuff from when I was testing, and I formatted my code to fit the code styling requirements.
remove whitespace and fix comments

Removed whitespace on line 54, and added space before comment words on lines 48 and 51.
update system.exit to report a success
wait for rogue threads to die using thread.join

Wait 1000 miliseconds for the thread to die if the thread is still alive
cancel all tasks when shutting down

That should reduce the number of rogue threads. Plus, it is safe since we've already disabled plugins, and saved worlds, so there should be any tasks left.
check to see if the thread is alive

Threads may be stopped because of thread.interrupt, so we need to check before going further to thread.join.
scheduler.stop takes care of cancelalltasks
cleaning up unused imports

logging imports are unneeded
remove unecessary toStrings
Merge pull request #6 from CircuitSoftGroup/master

fix shutdownmonitor