Tags
Creators
Details
All versions
1.21.1-0.3r
Release
Artemis' Thin Logs 0.3r2 days ago 12
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added:
- Natural thin tree and thin fungus world generation across many overworld biomes and both Nether forests.
- Connected thin log geometry: thin logs now build into branch-like shapes and junctions instead of only acting as simple axis-aligned posts.
- Manual connection editing with Shift + Axe, letting you disable or restore individual branch connections for custom shapes.
- Support for anchoring thin logs to solid faces, which makes wall- and ceiling-mounted detailing possible.
- A new overlay system for leaves, carpets, moss carpet, snow layers, and snow blocks that works with the new connected branch shapes.
Changed:
- Ported the mod from Forge 1.20.1 to NeoForge 1.21.1.
- Thin log rendering has been reworked to use connected branch models instead of the older per-axis overlay model setup.
- Overlay rendering now reuses the real block models, render types, and colors of the applied blocks, which improves compatibility with resource packs and shaders.
- Thin logs are now registered under the correct vanilla wood, stem, bamboo, and stripped-log tags, improving compatibility with vanilla systems and other mods.
Fixed:
- Fixed axe stripping so each thin log now strips into its correct matching wood type instead of always becoming a stripped oak thin log.
- Fixed leaf color rendering by delegating tinting to the actual leaf block, improving biome color accuracy.
- Fixed overlay item handling so carpets, leaves, snow layers, and snow blocks are removed and dropped more reliably.
- Fixed support checks for snow and carpet overlays so unsupported overlays are cleaned up correctly.
- Fixed snowy-block updates under thin logs so snow-covered setups interact more consistently with the surrounding terrain.-
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:zf33MPFz:JP2DifCM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zf33MPFz:JP2DifCM"
}

