Package dev.architectury.event.events.client

Interface ClientLifecycleEvent

@Environment(CLIENT)
public interface ClientLifecycleEvent

Nested Class Summary

Nested Classes

Modifier and Type	Interface	Description
static interface	ClientLifecycleEvent.ClientLevelState
static interface	ClientLifecycleEvent.ClientState

Field Summary

Fields

Modifier and Type	Field	Description
static final Event<ClientLifecycleEvent.ClientLevelState>	CLIENT_LEVEL_LOAD	Invoked after a level is loaded only on the client-side.
static final Event<ClientLifecycleEvent.ClientState>	CLIENT_SETUP	Invoked once client setup has begun.
static final Event<ClientLifecycleEvent.ClientState>	CLIENT_STARTED	Invoked when client has been initialised.
static final Event<ClientLifecycleEvent.ClientState>	CLIENT_STOPPING	Invoked when client is stopping.

Field Details

CLIENT_STARTED

static final Event<ClientLifecycleEvent.ClientState> CLIENT_STARTED

Invoked when client has been initialised. Equivalent to Fabric's ClientLifecycleEvents.CLIENT_STARTING.

CLIENT_STOPPING

static final Event<ClientLifecycleEvent.ClientState> CLIENT_STOPPING

Invoked when client is stopping. Equivalent to Fabric's ClientLifecycleEvents.CLIENT_STOPPING.

CLIENT_LEVEL_LOAD

static final Event<ClientLifecycleEvent.ClientLevelState> CLIENT_LEVEL_LOAD

Invoked after a level is loaded only on the client-side. Equivalent to Forge's WorldEvent.Load event (on client).

CLIENT_SETUP

static final Event<ClientLifecycleEvent.ClientState> CLIENT_SETUP

Invoked once client setup has begun.

This happens during FMLClientSetupEvent on Forge, or when Architectury API's client entrypoint initialises on Fabric.

Registries should have been initialised by this point, but there are no such guarantees, as you can modify the registry beyond this point on non-Forge environments.