Events/Launch/minified-launch
ConfigureX11EnvironmentEvent
Gets fired when the X11 Environment gets configured, only on Linux when using Wayland
Fields
displayStringThe display that has been resolved
When it fires
This fires from X11Helper.configureGraphicsEnvironment(...), called right before the Minecraft process is started, only when all of the following are true:
- The launcher is running on Linux (
os.namecontainslinux). - The child process environment doesn't already have a
DISPLAYvariable set (i.e. you haven't already configured one yourself). - Minified can find an active X11 socket in
/tmp/.X11-unix(e.g.X0,X1, …) and derive a display string like:0from it.
If any of those conditions fail - most commonly on Windows/macOS, or on a pure Wayland session with no Xwayland socket available - this event simply never fires and DISPLAY is left untouched.
When it does fire, Minified also sets DISPLAY on the child process environment to the resolved display value and, if WAYLAND_DISPLAY was set, removes it and sets XDG_SESSION_TYPE=x11 so Minecraft's LWJGL/GLFW windowing picks X11 instead of trying (and often failing) to use Wayland directly.
Listening
Subscribe on the EventBus the event is posted to, see Events for which bus that is.
eventBus.subscribe(ConfigureX11EnvironmentEvent.class, event -> {
String display = event.display();
});eventBus.subscribe(ConfigureX11EnvironmentEvent::class.java) { event ->
val display = event.display()
}Posted by
API reference: com.dervarex.minified.launch.events.environment.ConfigureX11EnvironmentEvent