Antibanish mechanics + Limited drops on map + SQL tidy-up

Added antibanish mechanics: as like other "diseases" that can be treated
with some useable items, banish will be able to be recovered as well.
Fixed some SQL issues introduced on the last commit, as well as
lingering inexistent ids on drop data. Fixed some concurrency issues
with MapleMapFactory. Set a ceiling for simultaneous items available per
map, where old ones are promptly discarded. Patched MWLB attack block
for higher level GMs.

src/net/server/channel/handlers/UseItemHandler.java

@@ -66,12 +66,21 @@ public final class UseItemHandler extends AbstractMaplePacketHandler {
                 remove(c, slot);
                 return;
             }
-            if (isTownScroll(itemId)) {
+            else if (isTownScroll(itemId)) {
                 if (ii.getItemEffect(toUse.getItemId()).applyTo(c.getPlayer())) {
                     remove(c, slot);
                 }
                 return;
             }
+            else if (isAntibanishScroll(itemId)) {
+                if (ii.getItemEffect(toUse.getItemId()).applyTo(c.getPlayer())) {
+                    remove(c, slot);
+                } else {
+                    c.getPlayer().dropMessage(5, "You cannot recover from a banish state at the moment.");
+                }
+                return;
+            }
+            
             remove(c, slot);
             
             ii.getItemEffect(toUse.getItemId()).applyTo(c.getPlayer());
@@ -84,7 +93,11 @@ public final class UseItemHandler extends AbstractMaplePacketHandler {
         c.announce(MaplePacketCreator.enableActions());
     }
 
-    private boolean isTownScroll(int itemId) {
+    private static boolean isTownScroll(int itemId) {
         return itemId >= 2030000 && itemId < 2030021;
     }
+    
+    private static boolean isAntibanishScroll(int itemId) {
+        return itemId == 2030100;
+    }
 }