All versions
0.1.13
Release
Forgeborne Odyssey 0.1.13last month 74
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
0.1.13
Gameplay
- Pit kiln now requires a grate before loading greenware or sealing: At Stage 1, attempting to remove greenware or seal the kiln without a grate installed will prompt "Grate required"
- Birch bark drop adjusted: Stripping birch logs now drops a fixed 4 birch bark instead of a random 1-2
- Tar kiln placement tightened: Right-clicking a dirt-like block with an empty hand now requires holding Shift to place a tar kiln, preventing accidental placement
Integration
- Jade plugin now supports tar kiln: Jade can now display the progress status of the tar kiln
Advancements
- Pit kiln advancement prerequisite corrected: "Kiln Mastery" now requires
first_greenwareinstead ofsparks_fly(greenware must exist before firing, makes more logical sense) - Guide book advancement trigger: Added
tutorial_guide_bookto the guide book advancement trigger items
Guide Book
- Tutorial overview updated: Overview page now lists Chapter 6 (Tar Kiln & Birch Tar) and Chapter 7 (Quern & Ore Processing), chapter color unified to
§4 - Pit kiln guide improvements:
- Overview page: Max temperature description updated to "900°C (1200°C with blowpipe)", added tip that temper grog in recipes can be substituted with sand/red sand
- Results page: Detailed firing conditions and products for each greenware type
- Color formatting unified across EN/ZH guide books: Natural metals, red mold, and other color markers changed from
§6to§4
Fixes
- Fixed BOM encoding issues in 9 rubble crafting recipes: Removed BOM markers from JSON file headers, resolving recipe loading failures in certain environments
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:7aV51V7y:jDiqU2ej"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7aV51V7y:jDiqU2ej"
}

