Skip to content

Allow anonymous analytics?

Our cookieless analytics show us which features get used and store nothing on your device. We never sell your data or use it for advertising.

Privacy choices

Choose what ModDex may collect. You can change this anytime from Privacy choices in the footer.

Read the full privacy policy

Strictly necessary Required for the site to work: login sessions, security tokens, and abuse prevention. Always on and cannot be disabled. Always on
Analytics Cookieless analytics through PostHog's EU servers, used only to see which features get used. Nothing is stored on your device, and the anonymous visitor ID resets every day. Needs your consent because usage data goes to a third party. Never used for advertising or profiling. Off by default in the EU and UK.

Feature Order Guard

Quick rating

Community listing page, reviews may not be monitored by the author.

How listings work Are you the author?

Feature Order Guard

By Rainy228

No reviews yet

Fixes the "Feature order cycle found" worldgen crash

Mod Loaders
Minecraft
Shockbyte server hosting: 35% off your first server with code MODDEX35 (opens in a new tab)

About

Description

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):

Option Default Meaning
strategy RESOLVE RESOLVE, REPORT_ONLY or CRASH
write_report_file true Write the report file (the log always gets a summary)

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.