You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document was made as I have noticed that this is a bit of a grey area when it comes to Origins datapacking and addon development. Pehkui has always been a very common dependency in the custom Origins scene, and I think that it's probably about time that a resource on how to do size changes in Origins was made.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Disclaimer: This migration guide is provided in Yarn mappings, if you're using different mappings and don't know what any of these are, I'd recommend looking up your mappings using Linkie
TL;DR - for Addon Devs
If you are making a datapack, this change exclusively is an internal one, you should not have to change anything about your datapack for it to function with this. If there is any incorrect behaviour as a result of this rewrite though, you're best to report it here.
If you're an addon dev, this change might affect you, as any code that references Item Actions will need to be updated.
Replace the type of direct Item Action references (Pair<World, ItemStack>) with Pair<World, StackReference>.
If you are registering any Item Actions, use the new ItemActionFactory class. In most cases, ItemActionFactory#createItemStackBased should work just fine. If you need to replace
If something is in all three versions, it will not be mentioned here.
I'm not going to be mentioning bugs as differences, mainly because I feel it is unfair to compare unintended behaviour.
I will also not be mentioning Farmer's Delight Refabricated's Skillet flipping here, because this is moreso a comparison to the original mod, I'll include this when the original has it.
To also note, the Decomposition REI integration in Farmer's Delight Fabric is bugged, it supports a block tag, however, it only shows one item from said block tag.
Data Driven Enchantments are something that was introduced by 1.21, it is a total rewrite to how enchantments are implemented through code, to make them customisable to an end user through datapack.
This guide's examples are in Mojmap, which may not be the mappings you are using. I will provide Yarn names for important classes, but otherwise, I'd recommend Linkie for remapping class/method/field names.
The Basic Datapack Structure
Data driven enchantments belong in the data/<namespace>/enchantment/ folder.
I'd highly recommend datagen as enchantment JSON can get complicated pretty quickly, especially with predicates and all, explaining datagen is out of scope for this guide, but it will help knowing how to use it.
Enchantments in data are structured as follows:
| Field Name | Type | Default | Description |