a3c43609ea
What i have is not much diffrent but its a start to allowing more liquid types without having to add them myself. The current method has 3 defualt liquids that are preset. The new system also uses String names to ID liquid instead of Enums. A new class Called LiquidData will keep track of the data need to ID, and use the Liquids. In the process i also fixed a few crafting recipes that were removed/messed up in a patch a while back. Plan for new system *Have default liquid type that come with textures/renders *Have several univeral pipes that can accept all Liquid types *Have a way of placeing a universal pipe and then converting to a regulated pipe, pipe that only take one liquid type *Have a tool for doing the above *Change the release Valve to be univeral with a GUI to restrict flow and Liquid type extracted
24 lines
675 B
Java
24 lines
675 B
Java
package liquidmechanics.api;
|
|
|
|
import liquidmechanics.common.handlers.LiquidData;
|
|
import net.minecraftforge.common.ForgeDirection;
|
|
import net.minecraftforge.liquids.ITankContainer;
|
|
|
|
public interface ITankOutputer extends ITankContainer
|
|
{
|
|
/**
|
|
* @param type - Liquid type
|
|
* @param dir - direction pressure is being request to output
|
|
* @return pressure if can output for the type or direction
|
|
*/
|
|
public int presureOutput(LiquidData type, ForgeDirection dir);
|
|
|
|
/**
|
|
* Quick way to check if the TE will output pressure
|
|
*
|
|
* @param type - Liquid type
|
|
* @param dir - direction
|
|
* @return
|
|
*/
|
|
public boolean canPressureToo(LiquidData type, ForgeDirection dir);
|
|
}
|