Various new tag providers for the missing tag types (` Potion`, ` Enchantment `& ` BlockEntity` / ` TileEntity`).Note: ` RegistrateLangExtProvider` DOES NOT support registering for the ` en_us` language code, use the vanilla ` RegistrateLangProvider` provider type & methods for this.To use this provider, look for any ` lang` method whose first parameter is ` languageKey` this is the `language code` you wish to add a translation for, constants for all vanilla Minecraft supported language codes can be found in ` RegistrateLangExtProvider`.Where as vanilla Registrate only supports ` en_us` by default. An extended LanguageProvider (` RegistrateLangExtProvider`) has been implemented and many similar ` lang()` methods exist, to allow registering translations for vaious lanuages.Things like ` ToolItem` & `ArmorItem` use different constructor parameters, many helper methods have been implemented into Registrator to make registering these kinds of items easier.This is mainly helpful for easier sub Item registrations.
This allows for passing in your custom item entries right into places that would usually expect an Item. Custom ` RegistryEntry` types allows for things like ` ItemProviderEntry` to implement ` IItemProvider` and be considered an Item object by the game.Custom builders not only gives access to using custom ` RegistryEntry` types, but also more freedom in what can be registered during the building process.Registrate will be shaded into the Jar file when built, under the package ` .`Īlthough Registrate will be shaded & accessible via the ` AbstractRegistrator#backend`, you should never have to use it outside of more advanced use casesĪdds support for various new Registration types
An Auto-Magic registration system built ontop of Registrate
0 kommentar(er)
