Tags
Creators
Details
All versions
5.5.0-1.20.1
Release
History Stages 5.5.0-1.20.13 months ago 31
Compatibility
Minecraft: Java Edition
1.20β1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Full Changelog: https://github.com/Flix100000/History-Stages/compare/5.4.0-1.20.1...5.5.0-1.20.1
New
- Compat: Locked items are now inert vs Spell Engine & Better Combat (#87).
- EMI: Brought EMI integration up to the same level as JEI.
- FTB Quests: Replaced stage cycling button with a searchable picker screen.
- Locks: Added NBT criterion to tag locks (#84).
- Stages: Added ability to hide or replace display names and tooltips of locked items.
- Editor: Added dependency graph viewer.
- Editor: Widgets and buttons now grow to fit long translations.
- I18n: Made hardcoded player-facing text translatable.
- Stages: Added temporary stage mode with auto re-lock timer.
- Stages: Added AUTO stage mode and auto-trigger system (#80).
- Editor: Added multi-select to entity picker.
- Spawnlock: Added per-dimension filter for spawn-locked entities.
- Stages: Added scoreboard objective dependency.
- Pedestal: Added config to lock scroll in pedestal while researching.
- Pedestal: Comparator output now reflects research progress (0-15).
Fixes
- Toasts: Stack variable-height notifications without overlap.
- Research: Gate isItemNeeded deposit timer by NBT criterion.
- Locks: Split place/use gating and block copycat material application (#81, #85).
- Research: Gate dependency item deposits by NBT criterion.
- Pedestal: Orient tier 2 pedestal to player facing on placement.
Optional dependencies
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:vChjQZEl:uRFdMktA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vChjQZEl:uRFdMktA"
}

