Links
Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 2 weeks ago
All versions
v1.4-mc1.17.x-1.21.x
Release
Dynamic Lights by CreepermeYT v1.4last year 1,435
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
1.17.x
Platform
Data Pack
Changes
Additions:
- Added 1.17.x, 1.18.x, 1.19.x, and 1.20.x support!!!
- Zombies, husks, foxes, allays, and zombie villagers that hold items that should glow, will actually glow!
- Added Allays as a new glowing feature that emit a Light Level of 6
- Added Enchanted Items & Armor as a new glowing feature that emit a Light Level of 4 and max distance from player 24
- Added Crying_obsidian to the list of items to emit a Light Level of 10
- Added Sculk_catalyst to the list of items to emit a Light Level of 7
- Added a new Light Level of 5, with items such as the amethyst cluster, trial spawners, vaults, and magma block
Changes:
- Overhaul of the Toggle Options Menu section, which now has two columns, two new toggle options, and an Active Lights counter which can be updated by pressing the [] button
- Improved the explanation of the Incompatible Screen which will now show up when a pre-1.17 mc version is detected
- Completely overhauled the Dynamic Light Generation Engine... again... but this time it is more efficient! and this time it works on pre 1.20.2 versions!
- Massively improved the datapack description
- Changed the pack.png background color to the intended shade of gray used by modrinth.
Bugs Fixed:
- Fixed v1.3's "SMART" engine's HORRIBLE performance
- marker, item_frame, block_display, item_display, text_display entities creating dynamic lights when lit on fire or struck by lightning
- After toggling ON/OFF any option in the menu, the feedback would have used the previous menu color rather than the new color
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:ZfuJWuL4:PIjtt3nN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZfuJWuL4:PIjtt3nN"
}

