Tags
Creators
Details
1.4.0
Compatibility
Required content
Changes
What's new in Forest X Reborn 1.4.0?
- Added rat
- Added crocodile
- Added sarbakan and dart
- Added cattail
- Added mulberry tree
- Added tumbleweed
- Added scorpion
- Added calibri and calibri feather
- Added vulture
- Added new types of skeletons
- Added raspberry
- Added pink and white rose bushes
- Added eucalyptus tree
- Added eucalyptus forest
- Added frozen swamp
- Added ice desert
- Added more trades for villagers with items from the mod
- Added polar and brown bear pelt and carpets
- Added sickles
- Added rye
- Added GUI for fermentation barrel
- Pelts can be dropped from bears
- Brown bears are now reacting to raspberries
- Five types of butterflies have been added
- The chance of the appearance of a old growth forest has been reduced
- Blueberries no longer appear in the ordinary forest
- Some improvements for old growth forest
- Added the sound of equipping silver armor
- Added a wave of the hand when interacting with some blocks
- Added the ability to remove the paint layer from the blocks
- The colors in the peat bog now match the colors of a regular swamp
- Now villages will appear in the semi-desert
- Increased the chance of some mobs appearing
- Changed id for bread with lard
- Updated some textures
- Added new painting - Pig in mood
- Removed music discs tab
- The growing period for all plants has been increased
- The brown bear has become bigger
- Updated panorama
- [Bugfix] Fixed a bug that caused the quiver to stack into 64 items
- [Bugfix] Fixed raccoon ID
- [Bugfix] Fixed a bug that caused non-vanilla tags to be used for painting blocks
- [Bugfix] Fixed a bug due to which it was possible to use bone meal at the last stage of some plants
- [Bugfix] Fixed sliding of the silver block
- [Bugfix] Missing tags have been returned
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:6SZBMNXj:IgxVR77v"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6SZBMNXj:IgxVR77v"
}

