Forge Config Screens [Forge & Fabric]

Forge Config Screens [Forge & Fabric]

13M Downloads

[Bug]: Inconsistent mod config screen provider registration

Exopandora opened this issue ยท 0 comments

commented

Mod Loader (Required)

Fabric

Minecraft Version (Required)

1.20.1

Mod Version (Required)

v8.0.2-1.20.1-Fabric

Notes (Required)

My mod uses forge config api port (thanks for creating that mod!), and I tried to use forge config screens to have an auto-generated config gui. But the registration of config screen providers seems to be inconsistent. I never got it to work in the official minecraft launcher using the following mods:

  • fabric-loader-0.15.7-1.20.1
  • fabric-api-0.92.1+1.20.1 (also tried fabric-api-0.83.1+1.20.1)
  • ForgeConfigAPIPort-v8.0.0-1.20.1-Fabric
  • ForgeConfigScreens-v8.0.2-1.20.1-Fabric
  • modmenu-7.2.2 (also tried modmenu-7.1.0)
  • ShoulderSurfing-Fabric-1.20.1-3.0.0

Renaming the jar of my mod to 00ShoulderSurfing-Fabric-1.20.1-3.0.0 did not make a difference.

However, I got it working in a dev environment, but only it only worked sometimes. I suspect this is a loading/sorting issue. I register my config in the first line of onInitializeClient in my client mod initializer class.

I am using Windows 10.

latest.log (Optional)

No response