Package net.neoforged.neoforge.fluids
Class FluidActionResult
java.lang.Object
net.neoforged.neoforge.fluids.FluidActionResult
Deprecated, for removal: This API element is subject to removal in a future version.
Holds the result of a fluid action from
FluidUtil.
Failed actions will always have isSuccess() == false and an empty ItemStack result. See FAILURE.
Successful actions will always have isSuccess() == true.
Successful actions may have an empty ItemStack result in some cases,
for example the action succeeded and the resulting item was consumed.-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final FluidActionResultDeprecated, for removal: This API element is subject to removal in a future version.final ItemStackDeprecated, for removal: This API element is subject to removal in a future version.final booleanDeprecated, for removal: This API element is subject to removal in a future version. -
Constructor Summary
ConstructorsModifierConstructorDescriptionprivateFluidActionResult(boolean success, ItemStack result) Deprecated, for removal: This API element is subject to removal in a future version.FluidActionResult(ItemStack result) Deprecated, for removal: This API element is subject to removal in a future version. -
Method Summary
-
Field Details
-
FAILURE
Deprecated, for removal: This API element is subject to removal in a future version. -
success
public final boolean successDeprecated, for removal: This API element is subject to removal in a future version. -
result
Deprecated, for removal: This API element is subject to removal in a future version.
-
-
Constructor Details
-
FluidActionResult
Deprecated, for removal: This API element is subject to removal in a future version. -
FluidActionResult
Deprecated, for removal: This API element is subject to removal in a future version.
-
-
Method Details
-
isSuccess
public boolean isSuccess()Deprecated, for removal: This API element is subject to removal in a future version. -
getResult
Deprecated, for removal: This API element is subject to removal in a future version.
-
ItemAccess-backed handler implementations will directly mutate the underlying item access, thus there is no need to represent the resulting item stack anymore.