Skip to main content

Using TMRV Reforged

Mod version shipped with FlammiCraft: 9.9.0+mc.21.1

Deutsch

TMRV maps supported JEI plugins into EMI; use EMI's normal search, recipe/uses views and supported menu transfers. It adds no separate machine interface.

Use builds matching Minecraft/loader and install EMI 1.1.24 or newer. TMRV 9.9.0 requires NeoForge 21.1.250 or newer and Java 21 on Minecraft 1.21.1; Minecraft 1.20.1 with LexForge and Java 17 remains supported. This client setup replaces the JEI API rather than requiring the full JEI mod. After joining a world, allow asynchronous registration to finish before judging missing categories. Respect the fork's explicit licence-assent and matching-source distribution requirements.

Compatibility is not universal. Plugins can add, hide and restore ingredients of registered types after onRuntimeAvailable. Once EMI registration finishes, the client tick applies changes to the index and active search while preserving personal EMI hiding settings. New ingredient types and other structural registrations still require the registration phase. Recipe Manager plugins have limited support and extended brewing may fall back to normal brewing. Only config/jei/blacklist.json is read as a transitional JEI configuration; prefer EMI's hiding settings. Other JEI configuration files do not control this UI.

Plugin settings and migration

TMRV's own settings are in config/toomanyrecipeviewers-client.toml. Restart Minecraft after editing. They control plugin selection and registration phases; use EMI's settings for normal search and recipe controls.

If no TOML file exists, TMRV imports valid settings from config/tmrv_plugins.json5 and retains the original unchanged. An existing TOML file takes precedence and is never automatically rewritten. Unreadable or invalid files are preserved, and the client log identifies the problem and asks you to repair the file and restart. A failed JSON5 import creates no TOML file. Defaults remain active until the configuration is repaired.

Existing setting names are retained:

  • allowDefaultAsync: Asynchronous registration is allowed when omitted. false changes the default ASYNC strategy to SYNC_EMI; explicit phase overrides take precedence.
  • defaultDisableDuplicatePlugins: When true, disables JEI plugins whose category namespaces already exist in EMI. Native EMI plugins already suppress their JEI counterparts unless a type override explicitly selects them.
  • typeOverrides: Maps plugin IDs to NORMAL, DISABLED or FORCE_PARTIAL_LOAD.
  • defaultPhaseOverrides and pluginPhaseOverrides: Select ASYNC, SYNC_EMI, SYNC_MAIN or SKIP for registration phases. Per-plugin entries take precedence. SYNC_MAIN runs the phase on Minecraft's main thread and can pause the interface while it runs.
  • blockedEMIPluginModIDs: Prevents native EMI plugins for these mod IDs from loading, allowing the JEI fallback to be selected.

Example of a targeted registration override; replace the plugin ID with the affected integration's ID:

[pluginPhaseOverrides."example:plugin"]
registerRecipes = "SYNC_EMI"

Imported recipe displays receive widget ticks and updates as ingredient alternatives cycle. Deliberately blank alternatives remain blank. Automated checks exercise these bridge functions for both targets; rendering and individual plugin compatibility still require separate in-game acceptance.

For missing categories inspect the client log's first plugin error after registration. For transfer failures check the open menu, inputs and plugin support. Working native EMI pages do not prove every imported JEI integration works. Historical upstream benchmarks are not measurements of this fork or pack; actual startup, memory and plugin acceptance require separate runtime checks.