Add config options to blacklist the different power systems.

This should help people avoid IC2 problems with console spam, but such a "solution" only relieves the most obvious symptom of chunk-thrashing, it doesn't stop the thrashing itself.
This commit is contained in:
Ben Spiers 2014-09-30 20:40:18 +01:00
parent 417b072c66
commit 5d08726880
3 changed files with 11 additions and 3 deletions

View file

@ -234,6 +234,10 @@ public class CommonProxy
Mekanism.TO_TE = Mekanism.TO_BC*10;
Mekanism.FROM_TE = Mekanism.FROM_BC/10;
Mekanism.blacklistBC = Mekanism.configuration.get(Configuration.CATEGORY_GENERAL, "BlacklistBuildCraftPower", false).getBoolean();
Mekanism.blacklistIC2 = Mekanism.configuration.get(Configuration.CATEGORY_GENERAL, "BlacklistIC2Power", false).getBoolean();
Mekanism.blacklistRF = Mekanism.configuration.get(Configuration.CATEGORY_GENERAL, "BlacklistRFPower", false).getBoolean();
if(Mekanism.cardboardSpawners)
{
MekanismAPI.removeBoxBlacklist(Blocks.mob_spawner, 0);

View file

@ -333,6 +333,10 @@ public class Mekanism
public static double FROM_TE;
public static double FROM_UE = 1/TO_UE;
public static boolean blacklistBC;
public static boolean blacklistIC2;
public static boolean blacklistRF;
//Usage Configuration
public static double enrichmentChamberUsage;
public static double osmiumCompressorUsage;

View file

@ -1198,7 +1198,7 @@ public final class MekanismUtils
*/
public static boolean useBuildCraft()
{
return Mekanism.hooks.BuildCraftPowerLoaded;
return Mekanism.hooks.BuildCraftPowerLoaded && !Mekanism.blacklistBC;
}
/**
@ -1208,7 +1208,7 @@ public final class MekanismUtils
*/
public static boolean useIC2()
{
return Mekanism.hooks.IC2Loaded;
return Mekanism.hooks.IC2Loaded && !Mekanism.blacklistIC2;
}
/**
@ -1218,7 +1218,7 @@ public final class MekanismUtils
*/
public static boolean useRF()
{
return Mekanism.hooks.RedstoneFluxLoaded;
return Mekanism.hooks.RedstoneFluxLoaded && !Mekanism.blacklistRF;
}
/**