Dashkal

Note: Switching from *> to ~> also avoids the stack overflow.

My use case is a pair of closely related state objects. We'll call them ActiveState and PersistState. PersistState is a subset of ActiveState. Three invariants - Both conversions are defined...

``` scala case class Request(...) case class Active(pendingRequests: Seq[Request], state: Long) { def toPersist = Persist(state) } case class Persist(state: Long) { def toActive = Active(Seq.empty, state) } object Persist...

This hit my radar again so I checked the API myself. The file in question doesn't have version tags when queried through the API. They show fine in the web...

Indeed not. Hence the actual request. Being told which flags would have allowed the command to succeed provides a work-around.

I did some digging and made some progress figuring out what's going on. The short of it is you added flax and fluffy plants as individual worldgen features. However, vanilla...

For comparison I looked into how Botania does it. Botania adds the feature using a standard forge registry pattern on `net.minecraft.core.Registry.FEATURE_REGISTRY`: https://github.com/VazkiiMods/Botania/blob/1.19.x/Forge/src/main/java/vazkii/botania/forge/ForgeCommonInitializer.java#L203 https://github.com/VazkiiMods/Botania/blob/1.19.x/Xplat/src/main/java/vazkii/botania/common/world/BotaniaFeatures.java#L26 https://github.com/VazkiiMods/Botania/blob/1.19.x/Xplat/src/main/java/vazkii/botania/common/world/MysticalFlowerFeature.java By contrast, you're adding it directly...

This does seem very likely, yes. I fear, however, that this will be a very common error on the part of other mods. Might be worth some mitigation somehow.

Alas. While fair enough that it's not on you, I can't make all other inventories behave either. As this bug appears to be tracking the associated invalidation of the Router's...