Feature Order Guard

Two worldgen mods, or a mod and a datapack, list the same placed features in a different order, and the game dies with Feature order cycle found. Feature Order Guard turns that crash into a working world and a report you can actually read.

Features

• No more crash: when vanilla finds a feature order cycle, the mod breaks it and loading continues.
• Smallest possible change: removes the cheapest set of "A before B" rules, measured in biomes affected. Exact for knots of up to 16 features (practically every real case), deterministic greedy beyond.
• Vanilla order everywhere else: the final order is built the same way vanilla builds it, so features outside the conflict are untouched. No feature is added, removed or moved to another step.
• Deterministic: same mods and datapacks always give the same order and the same report (with a fingerprint to compare).
• Clear report: logs/feature_order_guard-report.txt lists the step, the features, which biomes asked for which order, the mods involved (namespaces) and exactly which rule was dropped.
• Pin what matters: #feature_order_guard:pinned protects features whose order must not change.
• Your choice: RESOLVE, REPORT_ONLY (write the report, then crash like vanilla) or CRASH (pure vanilla).
• Zero cost when nothing is wrong: one tiny mixin around the vanilla sorter, no ticking, no packets. Server side only.

Config

config/feature_order_guard-startup.toml (read at game start, also in Mods → Feature Order Guard → Config):

Tags

• #feature_order_guard:pinned (placed features): ordering rules touching these are only dropped if there is no other way out (the report then warns).

Commands

• /featureorderguard report (game master): short summary in chat.

Compatibility

• Minecraft 26.1.2, NeoForge 26.1.2.107+, Java 25.
• Server side. Single player works out of the box. Clients joining a server do not need it.
• Works with any worldgen mod or datapack; it only changes the order inside a conflict.
• Written from scratch, no code from other mods.