Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated yesterday
All versions
1.5.0
Release
Backwoods 1.5.06 months ago 1,066
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
REUPLOAD
New Content
- 5 biomes.
- 7 advancements.
- 12 tools.
- 1 entity.
- 1 command.
- 23 blocks.
- 2 plants.
- 1 debug weapon.
- 1 potion effect.
- 23 foods.
- 1 dimension.
- 1 igniter.
- 1 utility.
- 6 items.
- 6 paintings.
- Geode in Loss.
Changes
- Code cleanup/fixes.
- Nerfed plaque block hardness
- Used loot tables for entities for proper loot chances.
- Redid rot effigy features/usage
- Increased the Rot spawn requirement since it's intended for overpowered players.
- Changed Loss main filler block.
- Plaque spreading has been improved to grow more consistently and naturally.
- Significantly increased Loss timer.
- Lowered faded block hardness and resistance.
- Implemented custom spawning conditions to make the Hollow rarer
- Adjusted vanishing effects of some entities
- Ash roses can now be put into flower pots.
- Nerfed rotten tools.
- Splinters now swing their arm while mining.
- Deleted shaders folder in built-in optional resource pack.
- Deleted 3 unused structures.
- Ash Weavers now drop ash roses if killed.
- Carrying the Plaque block now inflicts bad effects. These effects intensify the longer the block is held and slowly fade after it is dropped.
- Reduced damage of rotting blocks.
- Changed Faded block texture.
- Slightly increased Seep drop chance.
- Added a rare chance for tools to turn into something while in the Loss Dimension or when carrying Faded Blocks.
- Igniter success rates now vary by dimension.
- Faded blocks won't sustain plants.
Reupload of 1.5.0 since I forgot to delete experimental code in the splinter.
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:vOBTyVQ6:1uzY7GOM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vOBTyVQ6:1uzY7GOM"
}

