Download File

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](https://github.com/macbrayne/recovery-plus/blob/v0.5/src/main/resources/data/minecraft/portal_blocks/end_portal.json) for an example) * JSON files can have four objects: `trigger`, `predicate`, `inverted`, `action` * `trigger` can be only be `recovery_plus:inside_block` * `predicate` and `inverted` follow standard advancement location predicate syntax (stuff like `dimension` is possible) * `predicate` is the condition under which the trigger is executed * `inverted` is another optional condition under which the trigger is not executed * `action` is either `recovery_plus:add_to_backlog`, `recovery_plus:clear_backlog` or `recovery_plus:set_working_set` * `recovery_plus:add_to_backlog` adds a waypoint to the backlog * `recovery_plus:clear_backlog` removes all waypoints from the backlog * `recovery_plus:set_working_set` adds 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_name` with modid being the id of your datapack and file_name the name of the `json` file you put into `portal_blocks` (see [here](https://github.com/macbrayne/recovery-plus/blob/v0.5/src/main/resources/assets/recovery_plus/lang/en_us.json) for an example) 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