Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 20 hours ago
All versions
0.2.3+babric
Beta
RetroAPI 0.2.3 (Babric)last month 14
Compatibility
Minecraft: Java Edition
b1.7.3
Platform
Babric
Supported environments
Client and server
Changes
Sharper tools & tags.
- Custom tools now work on vanilla blocks: beta-accurate
mineable/{pickaxe,axe,shovel}andneeds_{stone,iron,diamond}_tooldefaults, so a plain.tool(PICKAXE).tier(IRON)item mines vanilla iron ore at iron speed, not just modded ores. mineabletags now grant speed only; whether a block needs a tool to drop comes from its material or aneeds_<tier>_tooltag (matches modern MC). Behavior change:.mineable(...)alone no longer gates drops on a hand-breakable material.- Multi-kind tools (
.tool(PICKAXE, AXE)paxels) and dynamic runtime tier (.tier(stack -> ...)). Declared plain-item tools mine at their tier's speed. AddedRetroTool.SHEARS. - Item tags plus arbitrary runtime-mutable tags for items and blocks; reads StationAPI's tag layouts and vanilla flattening names.
- Layered sprites with no model JSON:
.layers(base, overlays...)/.overlay(id). .facing()blocks: built-in orient-to-placer on placement, no custom enum oronPlaced.- Ergonomics: interface injection (no
RetroBlockAccess/RetroItemAccesscasts) and constructor factories (RetroBlockAccess.of(Ctor::new)). - StationAPI compatibility: clean hand-off of vanilla harvesting when StationAPI is present. See
STATIONAPI_TAG_COMPAT.md.
Built and validated against StationAPI 2.0.0-alpha.6.2 for b1.7.3 (Ornithe). All features exercised by the headless populate self-check.
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:iFaqJ8QH:RoVpvth1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iFaqJ8QH:RoVpvth1"
}

