Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated last month
All versions
1.7.0+mc26.1.2-neoforge
Release
WebGUI 1.7.0 (26.1.2 NeoForge)2 months ago 13
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
1.7.0 - 2026-09-08
Changed
- The browser library is now Rinku, not MCEF. MCEF [Keksuccino's Fork] was renamed, and its mod id changed from
mceftorinku.- On Fabric there is nothing to do — Rinku ships inside the WebGUI jar, as MCEF did before it.
- On NeoForge, install Rinku alongside WebGUI and remove MCEF. WebGUI now declares Rinku as a required dependency, so launchers install it for you; if you copy jars by hand you need to add it yourself.
- Chromium is now version 151. The browser is no longer capped at 60 FPS, and browser windows can be muted.
- Minecraft 26.1 and 26.2 are out of beta. Both ship as regular releases now instead of beta builds.
- Updated NeoForge (26.2.0.82, 26.1.2.107, 21.11.45, 21.1.250), Fabric Loader 0.19.5, Fabric API, and Yarn for 1.21.11.
Fixed
- Fixed a client crash on Minecraft 26.2 that hit after opening a web GUI a handful of times:
Texture view Sampler0 (MCEF Browser Texture 1x1) has been closed!. If you worked around it by settingbrowser-preload-enabled=false, you can turn browser preloading back on. - Fixed the browser refusing to start against current Chromium. WebGUI passed
--use-gl=desktop, a switch Chromium removed years ago. It went unnoticed while the browser library still shipped an older Chromium, and would have broken on any Chromium update. - Fixed the game crashing on startup on NeoForge when the browser library was missing. WebGUI declared no dependency on it at all, so launchers installed nothing and the game died during mod loading with
NoClassDefFoundError: org/cef/handler/CefDisplayHandlerinstead of telling you what was missing. Fabric was never affected, because the library ships inside the jar there. - Fixed the Minecraft 26 development server failing to boot, which made the mod impossible to test locally on those versions. Released servers were never affected.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:tDw1xQja:WeQ3iwOr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tDw1xQja:WeQ3iwOr"
}

