Tags
Creators
Details
0.2.0-Fabric
Compatibility
Required content
Changes
New Feature: Action Keys
Save actions for later use and assign those actions to keys! It supports all current action types and they are saved to your client's config instead of the world.
How to use:
- Create an action and put it in a command block (or any other in-world trigger)
- Run
/obscraft saveAction <id> - Send the translatable component (aka trigger the command block)
You should receive a toast indicating the save was successful.
You can assign an action to a key using /obscraft setActionKey <keyId> <actionId> (omit the actionId to clear a key instead)
Action Keys can be rebound in the normal Controls menu.
As a reminder, Architectury API and Fabric API (for Fabric) is required.
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:kNO8U2JY:qInByvUN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kNO8U2JY:qInByvUN"
}

