Petrolpark's Library

This library provides a variety of largely data-driven APIs for mod and modpack developers, and contains code common to my Create add-ons and other mods. Most of its systems are designed to be very versatile to allow modders and modpack developers to do things with the game they can't normally.

The library is heavily integrated with (https://modrinth.com/mod/create), but does not depend on it. Create-required features will simply be disabled if the mod is not installed.

Here is a list of API features in order of size and utility:

# API Features

## (https://github.com/petrolpark/Create-Library/wiki/Flags)

Flags are data-driven things that can be added to items stacks, fluid stacks and other objects like block entities. They persist through vanilla processes like Crafting, Smelting etc., most Create processes, and processes from this library like Ageing and Recycling (these can all be changed in the Configs). For example, items crafted from an item flagged with "poison" will also have the "poison" Flag.

## (https://github.com/petrolpark/Create-Library/wiki/Item-Decay)

Decay can be applied to items that will cause them to change after a given time, even if they are in an arbitrary modded inventory, allowing for things like rotting items or aging wine. They are based on the similar feature in Factorio, and are data-driven. Decays can change the item itself, or modify components (such as adding or removing Flags).

### Ageing Recipes

A recipe type that causes items placed in a Barrel (or other implementing container) to start a given Decay. The Decay is stopped if the item is removed from the container.

## (https://github.com/petrolpark/Create-Library/wiki/Teams)

A system for checking whether players belong to a specific group, and storing data for that group. Implementations include a single player, vanilla's scoreboard teams, and FTB Teams (upcoming). Team-bound items and block entities allow a player to select a Team of which they are a member, and then any members of that Team will access the same information for that object.

## (https://github.com/petrolpark/Create-Library/wiki/Wishes) (WIP)

Designed to remove RNG grind, Wishes are items that can be granted as quest rewards, Restaurant rewards, crafted, etc. and allow the player to choose items (specifically, specify an Advanced Ingredient, see below). Whenever the player rolls a loot table, the game will try its best to manipulate the loot table to fulfill the player's existing Wishes. It is a lot more involved than just rolling the loot table until the item is found, and as such works for Wishes more complex than just a specific item, such as items with particular enchantments.

## (https://github.com/petrolpark/Create-Library/wiki/Extended-Inventory) (Experimental)

Adds two new attribute types, `petrolpark:player.extra_inventory_slots` and `petrolpark:player.extra_hotbar_slots` that do exactly what they say on the tin. The extra slots will not only show in the inventory screen, but in vanilla and most arbitrary modded menus. Being attributes, they can be modified by armor, potions, enchantments etc. just with datapacks and/or commands. The aim is to provide a backpack system that does not involve having to click into a separate screen.

## (https://github.com/petrolpark/Create-Library/wiki/Loot-Table-Modifications)

Data-driven modification of existing vanilla or modded loot tables without having to overwrite the whole loot table, with greater versatility than NeoForge's (https://docs.neoforged.net/docs/resources/server/loottables/glm/) (such as being able to add, remove and modify individual loot pools and loot pool Entries). This allows multiple mods or datapacks to modify an existing loot table at once with datapacks.

## (https://github.com/petrolpark/Create-Library/wiki/Recycling) (WIP)

A versatile and balanced "uncrafting" system. Automatically scans recipes and tries to create reverse recycling recipes that accept as a parameter the proportion of ingredients to recycle, and if an item has numerous different recipes then recycling will usually produce nothing unless explicitly defined. If a recipe ingredient does not have a single obvious inverse item, it is omitted from the recycing results. Ingredient inverses can be defined with a datapack. For example, you can register your item "Scrap Planks" to the `minecraft:planks` tag ingredient, and then any recipe that takes the `minecraft:planks` tag as an ingredient will recycle into the corresponding number of Scrap Planks.

This system interfaces with the Item Compression system (see below), so if a modded recipe requires one Moddium Ingot, then the corresponding recycling recipe with 25% returns will give 2 or 3 Moddium Nuggets, without you having to tell it that. Modders can also register recycling output modifiers to affect the results based on the input item,