Links
Tags
Creators
Details
0.3.1+26.3
Compatibility
Changes
Afterburner 0.3.1 (Forge 26.3)
A small update, the same as Fabric 0.3.1 minus the Opal part (Opal is Fabric only). On Windows PCs with both a built-in and a separate graphics card, Windows often starts Java on the built-in one, so the game runs much slower than the PC can. Afterburner now notices: the title screen says so once, and the settings screen has a button that sets Windows' own graphics preference for the game's Java to the faster card (it applies from the next start; the same switch is in Windows under Settings > System > Display > Graphics). Nothing is changed unless you press it.
New, on by default (each can be switched off in the settings)
- Idle Graphics Card Note: On Windows PCs with a built-in and a separate graphics card: if the game runs on the built-in one, the title screen says so once, and these settings get a button to switch (from the next start). Nothing changes on its own.
Everything else is as in 0.3.0.
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:o0kOtaIS:7lXKGiRQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o0kOtaIS:7lXKGiRQ"
}

