Links
Tags
Creators
Details
0.2.0
Compatibility
Required content
Changes
RetroAPI 0.2.0
RetroAPI is a content-registration library for Minecraft Beta 1.7.3 that lets mods add blocks, items, recipes, entities, dimensions and more without requiring StationAPI. It runs on Ornithe (Fabric Loader + OSL) and Babric, and transparently delegates to StationAPI when that mod is also installed.
What it implements
Registration
- Custom blocks and items with automatic, stable ID assignment - block IDs are expanded well past the vanilla 256 cap, and assignments persist across loads.
- Block entities without subclassing
BlockWithBlockEntity(RetroBlockEntityType). - Inventory / menu GUIs (chest, furnace and dispenser styles) with automatic slot sync (
@SyncField). - Crafting, smelting and furnace-fuel recipes (
RetroRecipes). - Custom entities with renderers, and custom dimensions reached through walk-in portal blocks.
- Achievements and achievement pages.
- Sound autoloading and automatic lang / translation generation.
Rendering
- Expanded texture atlas plus custom block and item renderers and render types.
Vanilla-safe world storage (sidecar system)
- All modded content is written to
retroapi/sidecar files keyed by string identifiers, so a world can be opened in vanilla without crashing or losing data and reopened in RetroAPI intact. - Covers extended block IDs, modded block entities, modded items inside vanilla containers, and dropped item entities.
Multiplayer
- OSL-based networking with server-to-client ID mapping sync and extended-block chunk sync.
StationAPI compatibility (optional, bundled)
- Ships a
retroapi-stationapicompanion that loads only when StationAPI is also present and delegates registration, rendering, dimensions and world conversion to StationAPI. With it, RetroAPI worlds round-trip through StationAPI's flattened world format without data loss.
Downloads
- Ornithe -
retroapi-0.2.0.jar(requires OSL). - Babric -
retroapi-0.2.0-babric.jar(self-contained: OSL is bundled in).
Both jars include the StationAPI compatibility layer; it activates automatically if StationAPI is installed and stays dormant otherwise.
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:OkIGhVrU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iFaqJ8QH:OkIGhVrU"
}


