Tags
Creators
Details
2.0.0.beta.1
Compatibility
Required content
Changes
Should be pretty stable but testing and feedback is appreciated
- Rewrite the entire architecture and API
- Added new objective types
- ENTER_WORLD
- PLACEHOLDER
- DEAL_DAMAGE
- BREAK_ITEM
- WALK
- PLAYER_KILL objective now can be filtered by the victims name
- BREW objective now doesn't modify the brewed potions
- Added a bunch of API events to progress built-in objectives from other plugins. For example, API users now can progress BLOCK_BREAK, when a custom block breaks which is managed by their plugin
- ENTER_REGION types (region names) now need to specify a namespace as well, not just the region name. Currently only WorldGuard is supported like before. So use
wg:region_name - Added Nexo hook to progress BLOCK_BREAK, BLOCK_PLACE, BUILD and BLOCK_LOOT objectives for custom blocks
- Added partial ExcellentShop hook
- Objectives can now have an
on-progressandon-completesection where you can list commands that will run when the objective progresses or completes. These commands will run through CommandDispatcher as usual, so you have all the power it gives.
Examples for the new objective types:
PLACEHOLDER
tasks:
my_placeholder_objective:
task: PLACEHOLDER
display: "{status} &fMatch placeholder"
args:
placeholder: "%aurora_meta_test_int%"
# Defaults to == if not present
# Can be ==, ===, >, <, >=, <=
comparison: ">"
value: 10
# These are optional
check-interval: 200 # in ticks
async: false # be careful with this
For ENTER_WORLD, just specify the world names in the types section as usual.
For BREAK_ITEM, just specify the item id in the types section as usual.
For WALK just set the blocks the player needs to walk in the amount section.
Optional dependencies
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:NBlPi66Y:QltOQDmC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NBlPi66Y:QltOQDmC"
}

