Tags
Creators
Details
Licensed ARR
Published 9 months ago
Updated last month
All versions
2.5.0-1.21.1
Release
astages-2.5.0-1.21.13 months ago 112
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
New Features
- Add config options for recipe viewer integration and asynchronous cache building. (#230)
- Implement EMI integration for item, fluid and recipes. (#232)
- Implement REI integration for item, fluid and recipes. (#236)
- Update item property restrictions and tooltip messages (Introduce new methods). (#257)
- Update item messages for consistency. (#261)
- Refactor collision handling, Alex's Caves compatibility. (#278)
Bug Fixes
- Fix mod restriction evaluation logic. (#234)
- Fix remove_all action and command. (#237)
- Finally solved "AStages is forgetting Player Data". (#239)
- Handle corrupted legacy simple_restrictions.json. (#240)
- Improve player validation in block breaking and harvesting events. (#253)
- Add player validation in entity interaction event. (#254)
- Add player validation in player attack event. (#255)
API Changes
- Refactor reload handling to use ClientReloadPhase for improved clarity and consistency. (#217)
- Enhance client reload handling with new phases and improved model management. (#223)
- Introduce RecipeViewerManager and enhance JeiItemStagesPlugin with caching functionality. (#224)
- Replace HashMap with ConcurrentHashMap for thread-safe caching in OfflinePlayerStage. (#238)
- Update attribute names for consistency across restrictions. (#256)
- Mark update events as not yet implemented and deprecate UnpackLootTableEvent. (#258)
- Simplify client restriction reload state management. (#259)
- Add composite StreamCodec methods for variable argument handling (1.21.X only). (#260)
- Immutable server stages view in AStagesUtils. (#275)
- Replace List with Set for collections for structure restrictions. (#276)
- Add client-side structure restriction handling. (#277)
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:6wy8fmIk:7fwq6bMy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6wy8fmIk:7fwq6bMy"
}

