Skip to content

[Bug] Factory gauge cannot connect when recipe has 10 or more ingredient types #114

Description

@bulletproof-system

Describe the bug

When a recipe uses 10 or more distinct ingredient types, the factory gauge fails to connect to the mechanical crafter to register the recipe.
A concrete example is the Create Ore Excavation drilling machine (createoreexcavation:drilling_machine), which requires 10+ distinct item types in a large mechanical crafter grid. The factory gauge simply cannot link to this recipe, making it impossible to automate drilling machine production via factory gauges.

Steps to Reproduce

  1. Install Create Ore Excavation (COE) alongside Create and Extra Gauges.
  2. Place a factory gauge for the drilling machine (the output gauge).
  3. Place separate factory gauges for each ingredient and connect them to the output gauge one by one (e.g., via right-clicking with the gauge linker).
  4. When attempting to connect the 10th ingredient gauge, the connection fails — the 10th material gauge cannot be linked to the output gauge.

Expected Behavior

The factory gauge should connect to and fully recognize the drilling machine recipe with all 10+ ingredient types, allowing automated crafting via stock links / requesters.

Actual Behavior

The factory gauge cannot connect at all. The connection either fails silently, or only a subset of the recipe slots are recognized. The recipe is effectively un-automatable through factory gauges.

Recipe Details

  • Item: createoreexcavation:drilling_machine
  • Grid size: 5×5
  • Mod providing recipe: Create Ore Excavation

Environment

  • Minecraft Version: 1.21.1
  • Mod Loader: NeoForge
  • Mod Loader Version: 21.1.235
  • Create Version: 6.0.10
  • Extra Gauges Version: 2.1.2
  • Create Ore Excavation Version: 1.6.8

Additional Context

This is likely related to the factory gauge being designed around the vanilla 3×3 crafting grid (max 9 slots). With mods like Create Ore Excavation introducing large-grid recipes with 10+ ingredient types, lifting this restriction would significantly improve automation capabilities.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions