Major schedules & DB refactor

Refactored many calls for TimerManager's schedules throughout the source.
Switched all tables using MyISAM to InnoDB: on a multi-threaded environment such as this, table-locking is an instant no-no, and other gains MyISAM would have over InnoDB are minimal.
Altered getConnection() to properly throw an exception (good practice!) in case of no available connection instead of a mere null.

src/server/life/MapleMonsterInformationProvider.java

@@ -111,7 +111,7 @@ public class MapleMonsterInformationProvider {
                 Connection con = null;
 		try {
                         con = DatabaseConnection.getConnection();
-			ps = con.prepareStatement("SELECT * FROM drop_data WHERE dropperid = ?");
+			ps = con.prepareStatement("SELECT itemid, chance, minimum_quantity, maximum_quantity, questid FROM drop_data WHERE dropperid = ?");
 			ps.setInt(1, monsterId);
 			rs = ps.executeQuery();