Links
Creators
Details
Licensed GPL-3.0-or-later
Published 3 months ago
Updated 2 months ago
All versions
1.0.4
Release
Item Get! 1.0.43 months ago 46
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Changes
Item Get! v1.0.4 Changelog
Added:
- New trigger type: Dimension Changed
- New trigger type: Manual Trigger
- Designed for command blocks, datapack functions, KubeJS scripts, NPC dialogue, scene blocks, and other mods.
- Can show a reminder and record it in the handbook without requiring the player to obtain an item.
- Public Java API:
ItemGetApi.triggerItemGetApi.showItemGetApi.unlockItemGetApi.resetItemGetApi.isUnlockedItemGetApi.fireExternalTrigger
- New server commands:
/itemget trigger <targets> <rule_id>/itemget trigger <targets> <rule_id> force/itemget show <targets> <rule_id>/itemget fire <targets> <manual_trigger_id>/itemget fire <targets> <manual_trigger_id> force
- Restored utility commands:
/itemget handbook/itemget manager
- Added a Codex skill for modpack authors to generate, edit, and validate
config/item_get/rules.json.
Changed:
- Manual Trigger rules can be edited directly in the in-game editor.
- Manual Trigger entries now appear in the manager, handbook, and filters.
triggerandfireshow the reminder, mark progress, and record it in the handbook.showonly displays the reminder without changing progress or handbook history.unlockstill records the reminder in the handbook without showing a popup.
Fixed / Improved:
- Forge and NeoForge builds are now synchronized for v1.0.4.
- Added English language keys for the new trigger and commands.
- Improved command suggestions for rule ids and manual trigger ids.
- Handbook history avoids duplicate entries for the same rule revision.
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:C1yq2I7k:OvZ6QXwS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C1yq2I7k:OvZ6QXwS"
}

