Links
Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated last month
All versions
0.4.1+babric
Beta
RetroAPI 0.4.1 (Babric)last month 68
Compatibility
Minecraft: Java Edition
b1.7.3
Platform
Babric
Supported environments
Client and server
Changes
StationAPI mods now get the same automatic treatment RetroAPI mods do.
Creative tabs
- Auto tabs now include mods that register through StationAPI, not just RetroAPI. A mod that has never heard of RetroAPI gets a tab named after itself.
- Spawn eggs are no longer duplicated into the owning mod's tab, since they already sit in the Spawn Eggs tab. Eggs from other mods are left where they are.
Spawn eggs
- Automatic eggs now work under StationAPI. The sweep reads vanilla's EntityRegistry, which both toolchains populate. Living entities only.
- The fallback egg is tinted from a saturation weighted average of the mob's own render texture, so eggs are distinguishable before anyone draws one. Drop a sprite at assets/<mod>/textures/item/<mob>_spawn_egg.png to replace it.
Opting out without a dependency
- com.periut.retroapi.compat.RetroOptional takes only Strings, so a mod can call excludeItemGroup, excludeSpawnEggs and excludeSpawnEgg reflectively with no hard dependency on RetroAPI.
- templates/RetroCompat.java.txt is a copy in helper that wraps the mod check and the reflection, and does nothing when RetroAPI is absent.
Fixes
- The handshake length widener uses ModifyArg instead of ModifyConstant. Only one injector may claim a constant, so RetroTweaks and Glass Networking previously fought over it and whichever lost crashed on startup. Both now apply.
Known incompatibilities
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:sRwCV0VA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iFaqJ8QH:sRwCV0VA"
}




