Tags
Creators
Details
0.5+1.19
Compatibility
Required content
Changes
0.4 was not released publicly :)
- Entering and exiting a dimension through the same portal now removes that portal from the list
- Remove modfest-specific blocks used to showcase the mod
- Make the mod datapack-able:
- Files are placed in
data/modid/portal_blocks(see here for an example) - JSON files can have four objects:
trigger,predicate,inverted,action triggercan be only berecovery_plus:inside_blockpredicateandinvertedfollow standard advancement location predicate syntax (stuff likedimensionis possible)predicateis the condition under which the trigger is executedinvertedis another optional condition under which the trigger is not executed
actionis eitherrecovery_plus:add_to_backlog,recovery_plus:clear_backlogorrecovery_plus:set_working_setrecovery_plus:add_to_backlogadds a waypoint to the backlogrecovery_plus:clear_backlogremoves all waypoints from the backlogrecovery_plus:set_working_setadds the location to the backlog, sets the working set to the backlog and removes all waypoints from the backlog
- Lang keys are
item.recovery_plus.recovery_compass.type.modid:file_namewith modid being the id of your datapack and file_name the name of thejsonfile you put intoportal_blocks(see here for an example)
- Files are placed in
waypoint = a set of location, dimension, optional target location and dimension and a type backlog = the set of waypoints currently being edited and not being displayed and working set = the set of waypoints not being edited and being displayed in the compass - usually after dying
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:DU7GOxKZ:UJ2gAldm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DU7GOxKZ:UJ2gAldm"
}

