Links
Tags
Creators
Details
1.0-forge
Compatibility
Changes
This is an attempt to override Forge's early loading screen.
Usage may be unstable, and the game can crash unexpectically
Forge does not support custom early window (NeoForge does), so I tried to use an ugly "hack" to override it.
Unfortunately, the override is applied quite late, which may result in the original red early loading (or a white screen) to "flash" on the very game start. I can't do anything about that.
However, the red color of the original loading can be changed using darkMojangStudiosBackground:true in options.txt.
Installation
In contrast to NeoForge, this requires the default value in fml.toml:
earlyWindowProvider = "fmlearlywindow"
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:Bi8o4aLw:OkTiQ8J1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Bi8o4aLw:OkTiQ8J1"
}

