All versions
2.0.0-alpha.6
Alpha
[b1.7.3] StationAPI 2.0.0-alpha.62 months ago 463
Uploaded by
Compatibility
Minecraft: Java Edition
b1.7.3
Platforms
Babric
Fabric
Supported environments
Client-side
Client and server
Changes
- Fixed doors, pistons, and random ticking in custom height worlds
- Tags getter for registry entries
- Internal registry changes
- Fixed license placing
- Fixed genSources while using VineFlower
- Stats management
- Fixed bonemeal API in multiplayer
- Fixed memory leak during registry growth
- Added faster index boundary checking in flattening
- Changed setBlockState -> setBlockStateWithoutNotifyingNeighbors
- Removed object data type for MessagePacket
- Changed direction enums to match modern directions
- Added biome caching
- Fixed being able to spawn on any block
- Added ItemCraftedEvent and CraftingResultEvent
- Added better invalid json recipe feedback
- Translation keys are now automatically set for block and item templates based on the identifier
- ItemUsedInCraftingEvent no longer fires on null items
- Namespace resolving of other classes
- Mods with outdated entrypoints are now better reported on crashes
- Better consistency in events
- Missing entity/mob handlers now throw an exception
- EntityRegisterEvent now throws an exception on duplicate identifiers
- Updated DFU to v9
- Added convention tags
New Contributors
- @ProdOrDev made their first contribution in https://github.com/ModificationStation/StationAPI/pull/246
- @Lemmmy made their first contribution in https://github.com/ModificationStation/StationAPI/pull/249
Full Changelog: https://github.com/ModificationStation/StationAPI/compare/2.0.0-alpha.4.1...2.0.0-alpha.6
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| StationAPI-2.0.0-alpha.6-sources.jar | Source jar | 207.17 KiB |
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:472oW63Q:aatB4eaI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:472oW63Q:aatB4eaI"
}

