public class ComponentFluid
extends java.lang.Object
implements vazkii.patchouli.api.ICustomComponent
| Modifier and Type | Field and Description |
|---|---|
vazkii.patchouli.api.IVariable |
fluid |
vazkii.patchouli.api.IVariable |
scale |
| Constructor and Description |
|---|
ComponentFluid() |
| Modifier and Type | Method and Description |
|---|---|
void |
build(int componentX,
int componentY,
int pageNum)
Called when this component is built, after variables have been resolved with
IVariablesAvailableCallback.onVariablesAvailable(java.util.function.UnaryOperator<vazkii.patchouli.api.IVariable>). |
void |
onVariablesAvailable(java.util.function.UnaryOperator<vazkii.patchouli.api.IVariable> lookup)
Called when variables are available, before the template component is built
|
void |
render(com.mojang.blaze3d.matrix.MatrixStack matrixStack,
vazkii.patchouli.api.IComponentRenderContext ctx,
float pticks,
int mouseX,
int mouseY)
Called every render tick.
|
public vazkii.patchouli.api.IVariable fluid
public vazkii.patchouli.api.IVariable scale
public void build(int componentX,
int componentY,
int pageNum)
vazkii.patchouli.api.ICustomComponentIVariablesAvailableCallback.onVariablesAvailable(java.util.function.UnaryOperator<vazkii.patchouli.api.IVariable>).
Take the chance to parse String variables into game objects, perform error checking, and setup any local
positions here.build in interface vazkii.patchouli.api.ICustomComponentpublic void render(com.mojang.blaze3d.matrix.MatrixStack matrixStack,
vazkii.patchouli.api.IComponentRenderContext ctx,
float pticks,
int mouseX,
int mouseY)
vazkii.patchouli.api.ICustomComponentrender in interface vazkii.patchouli.api.ICustomComponentpublic void onVariablesAvailable(java.util.function.UnaryOperator<vazkii.patchouli.api.IVariable> lookup)
vazkii.patchouli.api.IVariablesAvailableCallbackonVariablesAvailable in interface vazkii.patchouli.api.IVariablesAvailableCallbacklookup - Call with arbitrary text, and it will be expanded:
first expanding all inline variables,
then attempting to apply "->" derivations if possible, otherwise looking up the string as a
plain variable from the template environment