Skip to content

Commit

Permalink
fire common client init during FML client setup
Browse files Browse the repository at this point in the history
  • Loading branch information
UpcraftLP committed Jan 13, 2024
1 parent 75a6f12 commit fa7cda2
Showing 1 changed file with 8 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -18,21 +18,28 @@
import net.minecraftforge.eventbus.api.SubscribeEvent;
import net.minecraftforge.fml.ModLoadingContext;
import net.minecraftforge.fml.common.Mod;
import net.minecraftforge.fml.event.lifecycle.FMLClientSetupEvent;
import net.minecraftforge.fml.javafmlmod.FMLJavaModLoadingContext;
import net.minecraftforge.registries.ForgeRegistries;

@OnlyIn(Dist.CLIENT)
@Mod.EventBusSubscriber(modid = CamsBackpacks.MOD_ID, value = Dist.CLIENT, bus = Mod.EventBusSubscriber.Bus.FORGE)
public class Client {

public static void init() {
CamsBackpacksClient.init();

//FIXME this is handled by resourcefulconfig in 1.20.4+
ModLoadingContext.get().registerExtensionPoint(ConfigScreenHandler.ConfigScreenFactory.class,
() -> new ConfigScreenHandler.ConfigScreenFactory(
(minecraft, parent) -> new ConfigScreen(parent, null, CamsBackpacks.CONFIGURATOR.getConfig(BackpacksConfig.class))
)
);

FMLJavaModLoadingContext.get().getModEventBus().addListener(Client::clientSetup);
}

private static void clientSetup(FMLClientSetupEvent event) {
event.enqueueWork(CamsBackpacksClient::init);
}

@SubscribeEvent
Expand Down

0 comments on commit fa7cda2

Please sign in to comment.