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/net/server/guild/MapleAlliance.java

@@ -208,7 +208,7 @@ public class MapleAlliance {
             ps.close();
             rs.close();
             
-            ps = con.prepareStatement("SELECT * FROM allianceguilds WHERE allianceid = ?");
+            ps = con.prepareStatement("SELECT guildid FROM allianceguilds WHERE allianceid = ?");
             ps.setInt(1, id);
             rs = ps.executeQuery();