Posted November 21, 20231 yr I made a config in my 1.16.5 minecraft mod, and I register it by doing: ModLoadingContext.get().registerExtensionPoint( ExtensionPoint.CONFIGGUIFACTORY, () -> (mc, screen) -> new ModConfig() ); but when I try to run the mod with a server I get: Attempted to load class net/minecraft/client/gui/screen/Screen for invalid dist DEDICATED_SERVER I tried to add: DistExecutor.safeRunWhenOn(Dist.CLIENT, () -> () -> { ModLoadingContext.get().registerExtensionPoint( ExtensionPoint.CONFIGGUIFACTORY, () -> (mc, screen) -> new ModConfig() ); }); or even: if (FMLLoader.getDist() == Dist.CLIENT) { DistExecutor.safeRunWhenOn(Dist.CLIENT, () -> () -> { ModLoadingContext.get().registerExtensionPoint( ExtensionPoint.CONFIGGUIFACTORY, () -> (mc, screen) -> new ModConfig() ); }); } but that still gives me the error. also, for some reason, if I do this: private static void method() { if (FMLLoader.getDist() == Dist.CLIENT) { ModLoadingContext.get().registerExtensionPoint( ExtensionPoint.CONFIGGUIFACTORY, () -> (mc, screen) -> new ModConfig() ); } } without calling the "method" method, it still gives me the error. Thanks.
November 22, 20231 yr You have to move the method call #registerExtensionPoint into a separate class, because the Function within the Supplier accepts a Screen object, whereby you load the Screen class, which then causes the error. ModLoadingContext.get().registerExtensionPoint(ExtensionPoint.CONFIGGUIFACTORY, () -> (mc, screen) -> new ModConfig());
December 7, 20231 yr On 11/22/2023 at 11:26 AM, Luis_ST said: You have to move the method call #registerExtensionPoint into a separate class, because the Function within the Supplier accepts a Screen object, whereby you load the Screen class, which then causes the error. ModLoadingContext.get().registerExtensionPoint(ExtensionPoint.CONFIGGUIFACTORY, () -> (mc, screen) -> new ModConfig()); The latest version of Forge has removed ExtensionPoint.CONFIGGUIFACTORY. Is it still possible to create a GUI config screen for a mod using Forge?
December 7, 20231 yr 5 hours ago, afunu said: Yes... that what I did I'm targetting Minecraft 1.20.x with Forge 48.1. ModLoadingContext.get().registerExtensionPoint(ExtensionPoint.CONFIGGUIFACTORY, () -> (mc, screen) -> new ModConfig()); worked in Minecraft 1.16 with the older version of Forge, but no longer works becase ExtensionPoint.CONFIGGUIFACTORY has been removed in the version of Forge for Minecraft 1.20.x. Thus, I'm wondering if it is still possible to create a GUI config screen for a mod using Forge 48.1 or newer. Edited December 7, 20231 yr by Hankinsohl
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.