2.3.6-beta
Compatibility
Required content
Changes
MineLights 2.3.6-beta
This is a beta release which introduces (day one 😁) support for Minecraft 26.1! Previous server version compatible (as of 2.3.1)!
Key Features & Major Changes
- Added support for 26.1.
Installation / Upgrade Instructions
- DELETE your old mine-lights-*.jar file completely.
- Download the from this release.
- Place the new mine-lights-2.3.6-beta.jar into your mods folder.
- Run Minecraft
- Using anything which isn't OpenRGB?
- Start Minecraft
- Wait for MineLights.exe to finish downloading in the background
- If all goes well, you will see a dialog asking you if you want to grant
MineLights.exepermission to access the internet! - After accepting, your supported devices will show red. You can now enjoy!
- Using anything which isn't OpenRGB?
This is a beta release. Expect the unexpected! If you encounter any bugs, do please let me know!
Full Changelog & Technical Details
- Added support for Minecraft 26.1.
- This version introduced official mappings to the game. As a result, mods such as
Cloth ConfigandMod Menuhave not been released! - There is as a result no option to configure the mod. As it stands, the default settings should suffice for the overwhelming majority.
- If you do want to change something, for now it will have to be via the config.json in
.minecraft\config\mine-lights.json.
- This version introduced official mappings to the game. As a result, mods such as
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| mine-lights-2.3.6-beta+26.1-sources.jar | Source jar | 84.95 KiB |
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:5cN5qhbm:KyhH0yxx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5cN5qhbm:KyhH0yxx"
}

