Farm Troubleshooter

作者：nav1gatorkmb

通过实测服务器诊断、证据和实用验证步骤，找出 Minecraft 农场停止运作的原因。

模组 Fabric 地图与信息

截图

A confirmed reason crops stopped growing

Measurements, suggested action and verification

介绍

中文介绍正在准备中，下面暂时显示原文。

Farm Troubleshooter — Fix Your Broken Minecraft Farms

Built a farm that doesn’t work? Farm Troubleshooter helps you find out why.

Diagnose iron farms, standard hostile mob farms, crop farms, sugar cane farms and cactus farms. Inspect measured spawning conditions, villager state, lighting, growth requirements and collection/storage evidence.

How it works

Press F and select the farm type and area.
Scan current conditions or observe events for 20–300 seconds.
Open a result to see its status, measurements, suggested action and verification steps.

You can assign optional production-stage regions, reopen the last saved report and export JSON on the server. The interface supports English and Russian. Server operators can also use /farmtroubleshooter commands without the client GUI.

Farm Troubleshooter diagnoses problems — it doesn’t automatically rebuild your farms.

Installation

Minecraft Java 1.21.1, Fabric Loader 0.16.14+, Java 21 and Fabric API for 1.21.1 are required. Tested with Fabric API 0.116.6+1.21.1.

Install the mod on the server for diagnostics. Install it on the client for the optional F interface. Singleplayer includes the server component. Diagnostic requests require operator level 2; enable commands in singleplayer. F also belongs to vanilla swap-offhand, so change the mod binding in Controls if needed.

Beta scope

This beta provides bounded, read-only checks for the five farm types above. Hostile checks cover zombie, skeleton and creeper conditions; biome spawn-pool membership, local density limits and complete throughput remain uncertain. Plant checks do not infer an automatic harvesting circuit. Collection checks do not reconstruct arbitrary transport graphs. Additional farm types remain unsupported.

Results distinguish confirmed findings, suspected problems, healthy individual checks, insufficient data and unsupported mechanics. A short interval without random events does not prove that a farm is broken. No missing chunk is force-loaded, and reports do not include inventory contents, seeds or player identities.

Full natural farm lifecycle and long-duration load validation are still ongoing. The build passed 60 JUnit tests and 22 actual Minecraft GameTests, plus native client checks. These tests do not guarantee compatibility with every farm design or mod combination.

Gallery example

The gameplay screenshots show a controlled test-world example: randomTickSpeed is set to 0. The first screenshot shows the confirmed growth blocker in the results; the second shows the actual measurement, suggested action and verification steps. The cover and project avatar are promotional illustrations.

Note: Supported farm types and diagnostic capabilities depend on the installed version of the mod.

Original code: MIT. This is an unofficial Minecraft mod and is not approved by Mojang or Microsoft.