Links
Tags
Creators
Details
All versions
0.9.4+26.1.x-fabric
Release
Neatly Better 0.9.4+26.1.x-fabric3 months ago 65
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Required content
Changes
- Infinity Arrows can now be picked up
- Re-Introduced Void Fog
- World Playtime is displayed in World Selection List
- Lapis Lazuli now stays in enchanting tables
- Saturation Effect has been added to secondary effects of beacons
- Fixed Uncentered Crosshair
- Throwing Potion of invisibility onto item frames will now make them invisible
- Players can now click through signs, wall banners and item frames to access containers behind them
- Attacking with a torch in main hand will ignite attacked entities
- vines can be sheared to stop their growth
- Remaining durability is displayed as a number on top of tools in GUIs
- Burnt logs have a 50% chance to drop charcoal
- Wool, Carpets & Beds can be dyed by right clicking them with a dye item
- Bubble columns flow through copper grate blocks
- New Terracotta, concrete stairs & slabs with every dyed variant
- Slabs can be crafted into block thanks to new utility recipes
- Delete button in world selection screens now move world files into trash instead of deleting them entirely
- Legacy combat with sword blocking has been re-introduced (disabled by default)
- Alternative recipes of Chest, TNT, Furnace, Hopper Minecarts, dispensers & repeaters have been added
- New Charcoal block has been added with similar properties to coal blocks
- Rightclicking a sign with phantom membranes will make them invisible (except text)
- Added new Potions with Glow effect
- Shulker bullets despawn after their shulker dies
- Shulker boxes now display preview of their contents
Fixed Bed Item Model Fixed Client Crash related to bundles
Optional dependencies
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:QnGtCsFv:UQbonZyk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QnGtCsFv:UQbonZyk"
}



