Tags
Creators
Details
Licensed AGPL-3.0-only
Published 3 years ago
Updated 3 years ago
All versions
1.2.0
Release
v1.2.0 (Archived)3 years ago 96
Compatibility
Minecraft: Java Edition
1.12.x
Platform
Forge
Supported environments
Client and server
Changes
v1.2.0
Unified RagiChemistry into RagiMaterials
- RagiMaterials supports various features based on the material system !!
Updated Dependencies
- Removed
- Forgelin-Continuous
- from this version, this mod includes kotlin library
- Forgelin-Continuous
- Added
- Mixinbooter
New Features
- New creative tabs: COMMON
- Removed material fluids
Blocks
- Crucible: melts metallic materials and casts them into components
Items
- Unfired Cast & Cast: used for Crucible to convert MaterialStacks into ItemStacks
Materials
- Added melting / boiling / sublimation point for steel-like materials
- the value is the same as iron
- Added new object
MaterialStack- consisting of
HiiragiMaterialand its quantity (Integer) - Similar to
FluidStackbut more suitable for the material system
- consisting of
- Fixed incorrect material info for grinding balls (Ender IO)
Shapes
- Changed the type of
HiiragiShape.scalefrom Double to Integer- this value is the same as fluid amount
- Example: a scale of ingot is 144
- this value is the same as fluid amount
Integration
Had Enough Items
- Added new category
- Crucible
- Crushing (Maybe removed in next update)
- Heat Source (Maybe removed in next update)
- Material
- Added new ingredient:
MaterialStack
For Devs
- Unified some registry classes into
HiiragiRegistry - New Capability
IMaterialHandler- Similar to
IFluidHander
- Similar to
- Item Interface
ICastItem- Used for Crucible Casting Recipe
- Added new function
alloyOf()to create alloy materials - Added core mod and mixin (current not used)
- Added new contributor: yuzu_machan
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:jczuskJT:bzuhJEp0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jczuskJT:bzuhJEp0"
}

