Recipe Fail Reason Display

[illuciaz23]

What

Add components to machines to show why recipes fail to setup, they are displayed in:

1. simple machine's sidebar
2. multiblock machine's UI
3. all machine's Jade Tooltip

recipe waiting reasons will also be displayed

Implementation Details

1. add failReasonMap field in RecipeLogic to memroize fail reasons, and failReasons that is used to synchronize components with the client.
2. add getFailReason() to ModifierFunction so recipeModifier can convey info about why recipes fail.
3. add fail reason component for some frequent occurrences.

Outcome

Players now can easily know why their machines do not work (in most cases).

Additional Information

Also add more info to AdjacentFluidCondition's tooltip to show specific fluid.
Add TODO about replacing ModifierFunction.NULL with cancel(reason).

Potential Compatibility Issues

This feature is all about info display, did not change the original logic or api. failReasonMap and failReasons are not persisted so
data errors will not occur.

[jurrejelle]

Can you also add docs to docs/content/modpack/changes/v7.5.0.md and the recipe modifiers page about this existing? the recipe modifiers page doesn't have java examples yet, up to you if you wanna add those too or just add it to the existing kjs examples

[jurrejelle]

Is this finished within this codebase?

[illuciaz23]

Not yet. There are still multiple usages of ModifierFunction.NULL in the codebase. Some of them were not replaced because I am not sure about reasons. I have only replaced the more common cases where the fail reason is explicit.

[illuciaz23]

I hava added docs to v7.5.0.md. I am not familiar with KubeJS, so I did not touch that part.

[screret]

I'd add failure_reason. to all of these keys:

Suggested change

	provider.add("gtceu.recipe_logic.insufficient_fuel", "Insufficient Fuel");
	provider.add("gtceu.recipe_logic.insufficient_in", "Insufficient Inputs");
	provider.add("gtceu.recipe_logic.insufficient_out", "Insufficient Outputs");
	provider.add("gtceu.recipe_logic.condition_fails", "Condition Fails");
	provider.add("gtceu.recipe_logic.no_contents", "Recipe has no Contents");
	provider.add("gtceu.recipe_logic.no_capabilities", "Machine has no Capabilities");
	provider.add("gtceu.recipe_logic.failure_reason.insufficient_fuel", "Insufficient fuel");
	provider.add("gtceu.recipe_logic.failure_reason.insufficient_in", "Insufficient inputs");
	provider.add("gtceu.recipe_logic.failure_reason.insufficient_out", "Insufficient outputs");
	provider.add("gtceu.recipe_logic.failure_reason.condition_fails", "Condition fails");
	provider.add("gtceu.recipe_logic.failure_reason.no_contents", "Recipe has no contents");
	provider.add("gtceu.recipe_logic.failure_reason.no_capabilities", "Machine has no I/O");

Do also edit all the uses of these

[screret]

also, most of these don't seem to be used anywhere?

[illuciaz23]

These were moved here from LangHandler, and have all been used in waiting reasons before (before this pr).

[screret]

Suggested change

	provider.add("gtceu.recipe_modifier.default_fail", "Recipe Modifier Fail");
	provider.add("gtceu.recipe_modifier.insufficient_voltage", "Voltage Tier Too Low");
	provider.add("gtceu.recipe_modifier.insufficient_eu_to_start_fusion",
	"Insufficient Energy to Initiate Fusion Reaction");
	provider.add("gtceu.recipe_modifier.coil_temperature_too_low", "Coil Temperature Too Low");
	provider.add("gtceu.recipe_modifier.failure_reason.default_fail", "Recipe modifier failure");
	provider.add("gtceu.recipe_modifier.failure_reason.insufficient_voltage", "Voltage too low");
	provider.add("gtceu.recipe_modifier.failure_reason.insufficient_eu_to_start_fusion",
	"Insufficient energy to initiate fusion reaction");
	provider.add("gtceu.recipe_modifier.failure_reason.coil_temperature_too_low", "Coil temperature too low");

[screret]

Suggested change

	provider.add("gtceu.recipe_logic.no_capabilities", "Machine has no Capabilities");
	provider.add("gtceu.recipe_logic.failure_reason.no_capabilities", "Machine has no %s capabilities");