/
ISubtypeRegistry.java
52 lines (46 loc) · 1.69 KB
/
ISubtypeRegistry.java
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
package mezz.jei.api;
import javax.annotation.Nullable;
import net.minecraft.item.Item;
import net.minecraft.item.ItemStack;
/**
* Tell JEI how to interpret NBT tags and capabilities when comparing and looking up items.
* <p>
* Some items have subtypes, most of them use meta values for this and JEI handles them by default.
* If your item has subtypes that depend on NBT or capabilities instead of meta, use this interface so JEI can tell those subtypes apart.
* <p>
* Note: JEI has built-in support for differentiating items that implement {@link net.minecraftforge.fluids.capability.CapabilityFluidHandler},
* adding a subtype interpreter here will override that functionality.
* <p>
* Replaces {@link INbtIgnoreList}.
* <p>
* Get the instance by implementing {@link IModPlugin#registerItemSubtypes(ISubtypeRegistry)}.
*
* @since 3.6.4
*/
public interface ISubtypeRegistry {
/**
* Tells JEI to treat all NBT as relevant to these items' subtypes.
*/
void useNbtForSubtypes(Item... items);
/**
* Add an interpreter to compare item subtypes.
*
* @param item the item that has subtypes.
* @param interpreter the interpreter for the item.
*/
void registerNbtInterpreter(Item item, ISubtypeInterpreter interpreter);
/**
* Get the data from an itemStack that is relevant to comparing and telling subtypes apart.
* Returns null if the itemStack has no information used for subtypes.
*/
@Nullable
String getSubtypeInfo(ItemStack itemStack);
interface ISubtypeInterpreter {
/**
* Get the data from an itemStack that is relevant to telling subtypes apart.
* Returns null if there is no data used for subtypes.
*/
@Nullable
String getSubtypeInfo(ItemStack itemStack);
}
}