WorldGuard integration is now disabled, since it has been broken for quite some time now and nobody who used it has been interested enough to actually fix it.

The code is left in though, just in case somebody finally decides to fix it. We'll probably strip the code out eventually if it remains unfixed.
This commit is contained in:
Brettflan 2012-02-02 15:20:40 -06:00
parent 487a3457f2
commit 5e14a4b1c7
1 changed files with 6 additions and 2 deletions

View File

@ -2,6 +2,7 @@ package com.massivecraft.factions;
import java.lang.reflect.Modifier;
import java.lang.reflect.Type;
import java.util.logging.Level;
import java.util.HashSet;
import java.util.Map;
import java.util.Set;
@ -20,7 +21,7 @@ import com.massivecraft.factions.integration.Econ;
import com.massivecraft.factions.integration.EssentialsFeatures;
import com.massivecraft.factions.integration.LWCFeatures;
import com.massivecraft.factions.integration.SpoutFeatures;
import com.massivecraft.factions.integration.Worldguard;
//import com.massivecraft.factions.integration.Worldguard;
import com.massivecraft.factions.integration.capi.CapiFeatures;
import com.massivecraft.factions.listeners.FactionsBlockListener;
import com.massivecraft.factions.listeners.FactionsChatEarlyListener;
@ -37,6 +38,7 @@ import com.google.gson.GsonBuilder;
import com.google.gson.reflect.TypeToken;
import com.griefcraft.lwc.LWCPlugin;
public class P extends MPlugin
{
// Our single plugin instance
@ -99,7 +101,9 @@ public class P extends MPlugin
if(Conf.worldGuardChecking)
{
Worldguard.init(this);
this.log(Level.WARNING, "Our WorldGuard integration is broken with current versions of WorldGuard, so it is disabled. If you are a plugin dev and want to try your hand at fixing it, be our guest.");
Conf.worldGuardChecking = false;
// Worldguard.init(this);
}
// Register Event Handlers