Recipe Fail Reason Display #4487

illuciaz23 · 2026-01-20T15:27:47Z

What

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

simple machine's sidebar
multiblock machine's UI
all machine's Jade Tooltip

recipe waiting reasons will also be displayed

Implementation Details

add failReasonMap field in RecipeLogic to memroize fail reasons, and failReasons that is used to synchronize components with the client.
add getFailReason() to ModifierFunction so recipeModifier can convey info about why recipes fail.
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.

fix AdjacentFluidCondition tooltip not display fluid info

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

src/main/java/com/gregtechceu/gtceu/api/recipe/modifier/RecipeModifierList.java

src/main/java/com/gregtechceu/gtceu/api/machine/trait/RecipeLogic.java

jurrejelle · 2026-01-21T10:43:59Z

src/main/java/com/gregtechceu/gtceu/api/recipe/modifier/ModifierFunction.java

 @FunctionalInterface
 public interface ModifierFunction {

+    // TODO: Add reasons for any NULL ModifierFunction (replace them with cancel)


Is this finished within this codebase?

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 · 2026-01-23T04:26:39Z

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

screret · 2026-01-23T14:02:25Z

docs/content/Modpacks/Changes/v7.5.0.md

+You are supposed to replace `ModifierFunction.NULL` with `ModifierFunction.cancel(reason)` to tell the machine why the recipe fail to start.
+```patch
+- return ModifierFunction.NULL;
+ return ModifierFunction.cancel(Component.translate("gtceu.recipe_modifier.xxx"));


isn't it Component.translateable and not Component.translate?

screret · 2026-01-23T14:04:04Z

src/main/java/com/gregtechceu/gtceu/data/lang/RecipeLogicLang.java

+        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");


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

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

screret · 2026-01-23T14:05:00Z

src/main/java/com/gregtechceu/gtceu/data/lang/RecipeLogicLang.java

+        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");


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 · 2026-01-23T14:08:17Z

src/main/java/com/gregtechceu/gtceu/data/lang/RecipeLogicLang.java

+        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");


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");

screret · 2026-01-23T14:08:50Z

src/main/java/com/gregtechceu/gtceu/api/recipe/RecipeRunner.java

+                    Component.translatable("gtceu.recipe_logic.no_capabilities")
+                            .append(Component.literal(": "))
+                            .append(Component.translatable(io.tooltip)),


To match my suggested change in RecipeLogicLang:

Suggested change

Component.translatable("gtceu.recipe_logic.no_capabilities")

.append(Component.literal(": "))

.append(Component.translatable(io.tooltip)),

Component.translatable("gtceu.recipe_logic.failure_reason.no_capabilities", Component.translatable(io.tooltip)),

screret · 2026-01-23T14:10:00Z

src/main/java/com/gregtechceu/gtceu/api/machine/multiblock/MultiblockDisplayText.java

+            if (!reasons.isEmpty()) {
+                textList.add(Component.translatable("gtceu.recipe_logic.setup_fail").withStyle(ChatFormatting.RED));
+                for (var reason : reasons) {
+                    textList.add(Component.literal(" - " + reason.getString()));


You shouldn't use getString and string concatenation to join components, as you'll lose all formatting information by doing that.

Suggested change

textList.add(Component.literal(" - " + reason.getString()));

textList.add(Component.literal(" - ").append(reason));

illuciaz23 added 2 commits January 20, 2026 15:30

add recipe fail reason display in both UI and jade;

c751d7b

fix AdjacentFluidCondition tooltip not display fluid info

add fail reason tooltip for some Modifiers

667947a

illuciaz23 requested a review from a team as a code owner January 20, 2026 15:27

github-actions bot added the 1.20.1 label Jan 20, 2026

Merge branch '1.20.1' into luckyblock/recipe-fail-reason

cee5381

illuciaz23 force-pushed the luckyblock/recipe-fail-reason branch from 551eabe to cee5381 Compare January 20, 2026 15:43

jurrejelle added type: feature New feature or request bundled for a 0.X.0 Update Release: Major - 0.X.0 Releases focused on Content, changes to gameplay; While maintaining mostly API stability. labels Jan 21, 2026

jurrejelle requested changes Jan 21, 2026

View reviewed changes

Add docs to v7.5.0.md.

1a4ab22

illuciaz23 force-pushed the luckyblock/recipe-fail-reason branch from b1d184a to 1a4ab22 Compare January 23, 2026 04:28

screret reviewed Jan 23, 2026

View reviewed changes

screret suggested changes Jan 23, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Recipe Fail Reason Display #4487

Recipe Fail Reason Display #4487

Uh oh!

illuciaz23 commented Jan 20, 2026

Uh oh!

jurrejelle left a comment

Uh oh!

Uh oh!

Uh oh!

jurrejelle Jan 21, 2026

Uh oh!

illuciaz23 Jan 23, 2026

Uh oh!

illuciaz23 commented Jan 23, 2026

Uh oh!

screret Jan 23, 2026

Uh oh!

screret Jan 23, 2026

Uh oh!

screret Jan 23, 2026

Uh oh!

screret Jan 23, 2026

Uh oh!

screret Jan 23, 2026

Uh oh!

screret Jan 23, 2026

Uh oh!

screret Jan 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	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");

	textList.add(Component.literal(" - " + reason.getString()));
	textList.add(Component.literal(" - ").append(reason));

Recipe Fail Reason Display #4487

Are you sure you want to change the base?

Recipe Fail Reason Display #4487

Uh oh!

Conversation

illuciaz23 commented Jan 20, 2026

What

Implementation Details

Outcome

Additional Information

Potential Compatibility Issues

Uh oh!

jurrejelle left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

illuciaz23 commented Jan 23, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants