Links
Tags
Creators
Details
All versions
1.20.1-1.1.0
Release
Valoria-1.20.1-1.1.03 weeks ago 165
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Any compatible version
Any compatible version
Changes
Added
- Added Invulnerability frames to Katana dash
- Added 4 tiers of Hammers: Bronze, Black Gold, Infernal, and Void
- Added unique leap and ground smash ability for Hammers with custom animated expanding shockwave particle
- Added 5 specialized enchantments for Hammers:
- Shock Absorption: mitigates fall damage during hammer smash (up to 100% on level III)
- Concussion: stuns and staggers targets in the impact radius for 0.2s - 0.8s
- Repulsion: launches enemies far away and upward from the epicenter of the smash
- Collapse: inverts knockback to pull enemies towards the player and slows them for 2s
- Sundering: shatters enemy armor upon impact for 5s
- Added Sundered status effect (reduces armor rating, dynamically supporting percentage-based armor)
- Added 4 tiers of Heavy Anvils (Bronze, Black Gold, Infernal, Void) with an interactive forging minigame, dynamic sweet-spot, instability meter, and 3D item rendering on the anvil
- Added Rift Ring accessory with custom Rift shaders and mechanics
- Added
RingsandNecklacespages to theJewelrysection of the Codex, and connected them directly to the gem pages using the new grey dashedlinkTolines - Added
addRecipe(ResourceLocation loc)method toGeneralPagefor precise control over which specific recipe is displayed in the Codex - Added Codex pages for all gems (Amber, Amethyst, Sapphire, Ruby) that unlock automatically upon obtaining them for the first time, detailing their spawn locations and uses
- Added Heavy Workbench recipe to craft an Amethyst Gem from 4 Wicked Amethysts
- Added a new Codex page about the Nihility (Void) effect, which automatically unlocks with a warning tooltip when a player takes critical void damage
- Added new models and visual states for looted Sarcophagus
- Added magical sparkle particles to opened but unlooted Sarcophagus
- Added Server Config option
enableFirstJoinRewardto toggle the Starter Bundle reward on first world join - Added
valoria:first_join_rewardLootCondition to support data-driven toggling of the Starter Bundle reward
Fixed
- Fixed Valoria portal frame duping
- Fixed Water Bubble can stun King Crab
- Fixed Multiblock LootTable
- Fixed Swamp Wanderer possible but rare possibility to crash the game
- Fixed Magmatic generation
- Fixed Fortress generation
- Fixed Sarcophagus loot duping
- Fixed Incorrect model generation for Tiered accessories
- Fixed Alchemy Station (Tier 1) wasn't added to mineable with axe tag
- Fixed Layering issues inside Codex
- Fixed multiblock blocks (like Sarcophagus and tall plants) dropping items when broken in Creative mode
- Fixed Crypt structure generating one block too low and occasionally eating large chunks of surface terrain
- Fixed Abilities sound mismatching
Changed
- Moved Sarcophagus mob equipment and Halloween logic from hardcode to
sarcophagus_gear.jsonloot table - Refactored entity spawning and gear distribution logic using data-driven LootTables
- Increased the Sarcophagus open sound volume
- Optimized Sarcophagus logic to only process on the server side
- Moved Curio Curses effects from hardcode to
valoria:cursestag to allow data-driven configuration - Moved PotBlock mob spawning from hardcode (Silverfish) to
valoria:pot_spawnsentity type tag - Changed several drops to be guaranteed (Nihility shard for Corrupted Troll & Wicked Scorpion, Pain crystal for Corrupted, Oceanic Shell for King Crab)
- Reduced Dryador movement speed
- Removed annoying banners from Codex, replaced with 2 small buttons near home button
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Valoria-1.20.1-1.1.0-nomusic.jar | Unknown | 13.61 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:m6xgg1aC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PmIir1iT:m6xgg1aC"
}

