SetConfig bugfixes

Just some silly mistakes. New methods weren't saving. Some portions of
the new methods also didn't return true, so you were getting the
successful message, as well as the error message (because it would
proceed to the end of the method, unchecked).

Should be fixed now. Can't find any more bugs, at the moment.

This release should lead up to an update, as I'm confident in the MySQL
version, as it is now. And SetConfig is where I want it to be, with the
new MySQL settings working.

src/main/java/io/github/ferusgrim/GrimList/Commands/SetConfig.java

@@ -104,8 +104,10 @@ public boolean run(CommandSender sender, String[] args) {
                     return true;
                 } else {
                     plugin.getConfig().set("MySQL." + s2, args[3]);
+                    plugin.saveConfig();
                     sender.sendMessage((sender instanceof Player ? plugin.mStart : "") + "MySQL " + WordUtils.capitalize(s2) + " was altered to : " + args[3]);
                 }
+                return true;
             }
             if (s2.equals("port")) {
                 int s3I;
@@ -119,8 +121,10 @@ public boolean run(CommandSender sender, String[] args) {
                         sender.sendMessage((sender instanceof Player ? plugin.mStart : "") + "MySQL Port is already set to : " + s3I);
                     } else {
                         plugin.getConfig().set("MySQL.port", s3I);
+                        plugin.saveConfig();
                         sender.sendMessage((sender instanceof Player ? plugin.mStart : "") + "MySQL Port altered to : " + s3I);
                     }
+                    return true;
                 }
             }
         }