So I was making a core mod, I wanted to add something to simplify forge's furnace handling as I find it a bit bad as beginner modders seem to muck it up with if() statements making it a slight bit laggy when you put fuel with a lot of mods that add fuel installed. So I made this lightweight and easy to use FuelHandler that can accept blocks and items and output a fuel.

 

I think this should be implemented into forge so beginning modders can have a more lightweight method of adding fuel, but I still think the fuel handler should stay for when modders want to experiment with NBT and metadata.

 

Without further to do here it is:

public class VinillaFurnaceFuelHandler implements IFuelHandler{

 

public static HashMap<Item, Integer> FurnaceFuel = new HashMap<Item, Integer>();

 

public class VinillaFurnaceFuelHandler implements IFuelHandler{

public static HashMap<Item, Integer> FurnaceFuel = new HashMap<Item, Integer>();


public static void RegisterFurnaceFuel(Item fuel, Integer burnTime){

	FurnaceFuel.put(fuel, burnTime);
}
@Override
public int getBurnTime(ItemStack fuel) {

	Item ItemInFuelSlot = fuel.getItem();
	Integer BurnTime = FurnaceFuel.get(ItemInFuelSlot);

	if (BurnTime == null) return 0; else return BurnTime;	
}
}

 

And to add blocks you need this (I did the same for items just for consistency):

public static void addItemFurnaceFuel(Item fuel, Integer burnTime){

	VinillaFurnaceFuelHandler.RegisterFurnaceFuel(fuel, burnTime);

}

public static void addBlockFurnaceFuel (Block fuel, Integer burnTime){

	VinillaFurnaceFuelHandler.RegisterFurnaceFuel(Item.getItemFromBlock(fuel), burnTime);

}

 

I hope this can be added to forge.

 

Thanks for reading!

CarbonBasedGhost

Do you have any profiling information?

Anything with poorly programmed handlers will cause issues.

I'm not opposed to this {if written correctly which yours has issues, mainly the map}