From edbd49f8fcc82ab6e4ce91766d0d6a4c4bef3378 Mon Sep 17 00:00:00 2001 From: KernelPanic Date: Fri, 7 Aug 2026 09:47:15 -0400 Subject: [PATCH] docs: fix wrong Catalogue-is-broken claim in config.md Catalogue still gets Archie's config screens - MrCrayfish's MenuLogue (a Fabric dev dependency, modLocalRuntime(libs.menulogue.fabric)) bridges Mod Menu's registered screens into Catalogue automatically. The previous wording (from the earlier docs-sync pass) incorrectly claimed Catalogue had no working integration path at all. Co-Authored-By: Claude Sonnet 5 --- Archie/docs/config.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Archie/docs/config.md b/Archie/docs/config.md index 8acbe8e2e..9ea28157f 100644 --- a/Archie/docs/config.md +++ b/Archie/docs/config.md @@ -184,7 +184,10 @@ category per enabled entry. Saving routes through `ConfigSpec.save()` for `Commo `ConfigContainer.init()` registers the resulting screen via Architectury's `Mod.registerConfigurationScreen`, which surfaces it wherever the platform normally exposes a mod's config screen — Mod Menu's mod list on Fabric, the vanilla mod list's "Config" button on NeoForge. -There's no more Archie-specific Mod Menu/Catalogue entrypoint to register yourself; the dedicated +There's no more Archie-specific Mod Menu/Catalogue entrypoint to register yourself — the dedicated `ArchieModMenu`/`ArchieCatalogue` bridge classes were retired along with the old -`AConfigPlatform.registerScreenHandler` mechanism they depended on, and Catalogue no longer has a -working integration path as a result. +`AConfigPlatform.registerScreenHandler` mechanism they depended on. Catalogue still works, though: +MrCrayfish's [MenuLogue](https://www.curseforge.com/minecraft/mc-mods/menulogue) (a +`modLocalRuntime` dev dependency on Fabric) bridges Mod Menu's registered config screens into +Catalogue automatically, so registering via `Mod.registerConfigurationScreen` is enough to reach +both.