Links
Tags
Creators
Details
All versions
1.0.4.1
Release
Valoria-1.20.1-1.0.4.14 days ago 214
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Changes
Added
- Added Heavy Workbench recipes for Crimtane Tools and Armor
- Added Heavy Workbench recipes for Pyratite Armor
- Added Bows and Crossbows to Forge and Tridot tags
- Added Pyratite Plate item
- Added recipes for elemental bows and crossbows to the Heavy Workbench
- Added upgrade recipes for elemental shields to the Manipulator
- Added visual tooltips and on-hit effects for custom arrows (Nature, Aquarius, Infernal, Wicked, Pyratite, Soul)
- Added Jade bow and Jade crossbow recipes
- Added Bronze shield recipe
- Added Nature shield recipe
- Added Aquarius shield recipe
- Added Infernal shield recipe
- Added Void shield recipe
- Added Crimtane shield recipe
- Added Spider shield recipe
- Added Keybinds to Curio accessories and Curio
Fixed
- Fixed Cattail model, datagen generated wrong one
- Fixed Jade bow and Jade crossbow data tags
- Fixed some of the shields had misplaced placement in hands
- Fixed Pixie spawn egg texture
Changed
- Updated and tweaked models for curved shields (Pyratite, Spider, Void, and basic Curved Shield)
- Adjusted Shadewood Spider and King Crab loot tables (better drop chances and Looting scaling)
- Changed Spider Helmet recipe
- Changed Spider Chestplate recipe
- Changed Spider Leggings recipe
- Changed Spider Boots recipe
- Changed Shadewood drops
- King Crabs are neutral now
- Resorted Heavy Workbench and Alchemy recipes
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Valoria-1.20.1-1.0.4.1-nomusic.jar | Unknown | 13.28 MiB |
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:PmIir1iT:KdG143Fs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PmIir1iT:KdG143Fs"
}




