Jump to content

Requesting Feedback on Registration


Tablock_

Recommended Posts

I would like any feedback on what I have done for registering my items and blocks. I used an enum to organize all of the different namespaces or id's. Each namespace then contains the types of objects that are registered to them. Examples: "steelstone" stores an item only while "bismuth_ore" contains a block and an item. You can tell which namespaces contain what by looking at where they are defined in the ID class. I created a sub-class called Register that I use to define my namespaces. The methods inside this subclass do the registering, but only once I pass an instance of the Register class into one of my namespaces. Feel free to understand how it works, but the important thing I would like feedback on is if this is a valid way to approach registration, or that I just overcomplicated it.

 

public enum ID
{
    STEELSTONE(new Register().item()),
    CARBON(new Register().item()),
    STEEL_BLEND(new Register().item()),
    STEEL_INGOT(new Register().item()),
    RAW_BISMUTH(new Register().item()),
    BISMUTH_INGOT(new Register().item()),
    BISMUTH_NUGGET(new Register().item()),
    XYLUTH_INGOT(new Register().item()),
    SPECIAL_PICKAXE(new Register().object(new PickaxeItem(Main.SPECIAL_TIER, 1, -2.8F, newItemProperties()))),
    
    MACHINE_CASING(new Register().block(Blocks.IRON_BLOCK).blockItem()),
    BISMUTH_ORE(new Register().block(Blocks.IRON_ORE).blockItem()),
    DEEPSLATE_BISMUTH_ORE(new Register().block(Blocks.DEEPSLATE_IRON_ORE).blockItem()),
    XYLITE_ORE(new Register().block(Blocks.NETHER_GOLD_ORE).blockItem()),
    KRYPTOPHYTE_ORE(new Register().block(Blocks.OBSIDIAN).blockItem()),
    MACHINE_BLOCK(new Register().block().blockItem()),
    
    BISMUTH_GENERATOR(new Register().block().blockItem().blockEntity());
    

//Feel free to understand how this works below. Otherwise the methods .block() registers a block using the corresponding namespace, .item() registers item, etc. Keep in mind I frequently used method overloading.


    public static final Named<Item> BISMUTH_ORES = ItemTags.bind(Main.MOD_ID + ":bismuth_ores"); 
    public static final Named<Block> NEEDS_SPECIAL_TOOL = BlockTags.bind(Main.MOD_ID + ":needs_special_tool");
    
    private String name = this.toString().toLowerCase();
    private Block block;
    private Item item;
    private BlockEntityType<?> blockEntityType;
    
    private ID(Register registry)
    {
        registry.register(this);;
    }
    
    private static class Register
    {
        private List<Supplier<Object>> suppliers = new ArrayList<Supplier<Object>>();
        private ID id;
        
        private void register(ID id)
        {
            this.id = id;
            
            for(Supplier<Object> supplier : suppliers)
            {
                Object object = supplier.get();
                
                if(object instanceof Item)
                {
                    id.item = (Item) object;
                    
                    Main.ITEMS.register(id.name, () -> id.item);
                }
                
                if(object instanceof Block)
                {
                    id.block = (Block) object;
                    
                    Main.BLOCKS.register(id.name, () -> id.block);
                }
                
                if(object instanceof BlockEntityType<?>)
                {
                    id.blockEntityType = (BlockEntityType<?>) object;
                    
                    Main.BLOCK_ENTITIES.register(id.name, () -> id.blockEntityType);
                }
            }
        }
        
        private Register object(Object object)
        {
            suppliers.add(() -> object);
            
            return this;
        }
        
        private Register item(Item.Properties itemProperties)
        {
            return object(new Item(itemProperties));
        }
        
        private Register item()
        {
            return item(newItemProperties());
        }
        
        private Register block(BlockBehaviour.Properties blockProperties)
        {
            return object(new Block(blockProperties));
        }
        
        private Register block(Block blockToCopy)
        {
            return block(BlockBehaviour.Properties.copy(blockToCopy));
        }
        
        private Register block()
        {
            suppliers.add(() -> createInstance(""));
            
            return this;
        }
        
        private Register blockItem(Item.Properties itemProperties)
        {
            suppliers.add(() -> new BlockItem(id.block, itemProperties));
            
            return this;
        }
        
        private Register blockItem()
        {
            return blockItem(newItemProperties());
        }
        
        private Register blockEntity()
        {
            suppliers.add(() -> BlockEntityType.Builder.of(this::createBlockEntity, id.block).build(null));
            
            return this;
        }
        
        private Object createInstance(String childClassName, Object... initargs)
        {
            String blockClassName = "com.tablock.my_first_mod.block." + WordUtils.capitalize(id.name.replace('_', ' ')).replaceAll(" ", "");
            Class<?>[] parameterTypes = new Class<?>[initargs.length];
            
            for(int index = 0; index < initargs.length; index++)
            {
                parameterTypes[index] = initargs[index].getClass();
            }
            
            try
            {
                return Class.forName(blockClassName + childClassName).getConstructor(parameterTypes).newInstance(initargs);
            }
            catch(Exception exception)
            {
                exception.printStackTrace();
                
                return null;
            }
        }
        
        private BlockEntity createBlockEntity(BlockPos blockPos, BlockState blockState)
        {
            return (BlockEntity) createInstance("$BlockEntityChild", blockPos, blockState);
        }
    }
    
    private static Item.Properties newItemProperties()
    {
        return new Item.Properties().tab(Main.MOD_TAB);
    }
    
    public String getName()
    {
        return name;
    }
    
    public Block getBlock()
    {
        return block;
    }
    
    public Item getItem()
    {
        return item;
    }
    
    public BlockEntityType<?> getBlockEntityType()
    {
        return blockEntityType;
    }
}

Link to comment
Share on other sites

I am using DeferredRegister. I am initializing them in my Main class and calling DefferedRegister$register(IEventBus bus):

public static final String MOD_ID = "my_first_mod";
public static final DeferredRegister<Item> ITEMS = DeferredRegister.create(ForgeRegistries.ITEMS, Main.MOD_ID);
public static final DeferredRegister<Block> BLOCKS = DeferredRegister.create(ForgeRegistries.BLOCKS, Main.MOD_ID);
public static final DeferredRegister<BlockEntityType<?>> BLOCK_ENTITIES = DeferredRegister.create(ForgeRegistries.BLOCK_ENTITIES, Main.MOD_ID);
public static final DeferredRegister<MenuType<?>> CONTAINERS = DeferredRegister.create(ForgeRegistries.CONTAINERS, Main.MOD_ID);
public static final IEventBus BUS = FMLJavaModLoadingContext.get().getModEventBus();

public Main() throws ClassNotFoundException
{        
   Class.forName("com.tablock." + MOD_ID + ".setup.ID"); //loads the ID class from before
        
   ITEMS.register(BUS);
   BLOCKS.register(BUS);
   BLOCK_ENTITIES.register(BUS);
   CONTAINERS.register(BUS);
        
   TierSortingRegistry.registerTier(Main.SPECIAL_TIER, new ResourceLocation("special"), List.of(new ResourceLocation("netherite")), List.of());
        
   DistExecutor.unsafeRunWhenOn(Dist.CLIENT, () -> () -> BUS.addListener(Client::init));
        
   MinecraftForge.EVENT_BUS.register(this);
}

 

Link to comment
Share on other sites

Ok I understand, but how might I pass the Item constructor directly and have an Item variable that refers to the same item? I have tried using the ObjectHolder annotation, but I dislike having to have a variable for each type (i.e. item, block, block entity, etc). Since I am storing all of my registry types inside individual objects that represent a specific namespace, I can't use ObjectHolder because it requires a static initializer. Basically, I want to remove the hassle of manually creating a variable every time I need to register a new type. I don't want to have two variables, one a Block and the other an Item, just to represent the same namespace. If this is impossible then I will just use ObjectHolder and put my register types into corresponding classes, one class holding all my items, another my blocks, etc.

Edited by Tablock_
Link to comment
Share on other sites

I see what you are saying, but I may have found a solution that better fits me:

private static final Supplier<Object> supplier = () -> new Item(newItemProperties());

private static final RegistryObject<Item> item = Main.ITEMS.register("test_item", () -> (Item) supplier.get());

Is the above code valid? The Item constructor should not be called until it is already passed into the DeferredRegister. I am not entirely sure if this is valid due to their being an Item cast. If the code above isn't valid, is this?

private static final Supplier<Item> supplier = () -> new Item(newItemProperties());
 
private static final RegistryObject<Item> item = Main.ITEMS.register("test_item", supplier);
Edited by Tablock_
Link to comment
Share on other sites

Here is my revised class. I am using registry objects to access my items and blocks. See the bottom of the class with all of the accessor methods. Also one question, why is it not ok to supply the Item constructor indirectly? I thought maybe because the game should be creating a new item object instead of reusing the same one. However, doesn't blocks and items use the same object anyway? I thought block entities created their own unique objects, that's why they can cause lag.

public enum ID
{
	STEELSTONE(new Register().item()),
	CARBON(new Register().item()),
	STEEL_BLEND(new Register().item()),
	STEEL_INGOT(new Register().item()),
	RAW_BISMUTH(new Register().item()),
	BISMUTH_INGOT(new Register().item()),
	BISMUTH_NUGGET(new Register().item()),
	XYLUTH_INGOT(new Register().item()),
	SPECIAL_PICKAXE(new Register().object(Item.class, () -> new PickaxeItem(Main.SPECIAL_TIER, 1, -2.8F, newItemProperties()))),
	BIOME_FINDER(new Register().object(Item.class, () -> new BiomeFinder(newItemProperties()))),
	
	MACHINE_CASING(new Register().block(Blocks.IRON_BLOCK).blockItem()),
	BISMUTH_ORE(new Register().block(Blocks.IRON_ORE).blockItem()),
	DEEPSLATE_BISMUTH_ORE(new Register().block(Blocks.DEEPSLATE_IRON_ORE).blockItem()),
	XYLITE_ORE(new Register().block(Blocks.NETHER_GOLD_ORE).blockItem()),
	KRYPTOPHYTE_ORE(new Register().block(Blocks.OBSIDIAN).blockItem()),
	MACHINE_BLOCK(new Register().block().blockItem()),
	
	BISMUTH_GENERATOR(new Register().block().blockItem().blockEntity());
	
	public static final Named<Item> BISMUTH_ORES = ItemTags.bind(Main.MOD_ID + ":bismuth_ores"); 
	public static final Named<Block> NEEDS_SPECIAL_TOOL = BlockTags.bind(Main.MOD_ID + ":needs_special_tool");
	
	private String name = this.toString().toLowerCase();
	private RegistryObject<Block> block;
	private RegistryObject<Item> item;
	private RegistryObject<BlockEntityType<?>> blockEntityType;
	
	private ID(Register registry)
	{
		registry.register(this);
	}
	
	private static class Register
	{
		private HashMap<Class<?>, Supplier<Object>> supplierMap = new HashMap<>();
		private ID id;
		
		private void register(ID id)
		{
			this.id = id;
			
			for(Object key : supplierMap.keySet())
			{
				Supplier<Object> supplier = supplierMap.get(key);
				
				if(key.equals(Item.class))
				{
					id.item = Main.ITEMS.register(id.name, () -> (Item) supplier.get());
				}
				
				if(key.equals(Block.class))
				{
					id.block = Main.BLOCKS.register(id.name, () -> (Block) supplier.get());
				}
				
				if(key.equals(BlockEntityType.class))
				{
					id.blockEntityType = Main.BLOCK_ENTITIES.register(id.name, () -> (BlockEntityType<?>) supplier.get());
				}
			}
		}
		
		private Register object(Class<?> type, Supplier<Object> supplier)
		{
			supplierMap.put(type, supplier);
			
			return this;
		}
		
		private Register item(Item.Properties itemProperties)
		{
			return object(Item.class, () -> new Item(itemProperties));
		}
		
		private Register item()
		{
			return item(newItemProperties());
		}
		
		private Register block(BlockBehaviour.Properties blockProperties)
		{
			return object(Block.class, () -> new Block(blockProperties));
		}
		
		private Register block(Block blockToCopy)
		{
			return block(BlockBehaviour.Properties.copy(blockToCopy));
		}
		
		private Register block()
		{
			return object(Block.class, () -> createInstance(""));
		}
		
		private Register blockItem(Item.Properties itemProperties)
		{
			return object(Item.class, () -> new BlockItem(id.block.get(), itemProperties));
		}
		
		private Register blockItem()
		{
			return blockItem(newItemProperties());
		}
		
		private Register blockEntity()
		{
			return object(BlockEntityType.class, () -> BlockEntityType.Builder.of(this::createBlockEntity, id.block.get()).build(null));
		}
		
		private Object createInstance(String childClassName, Object... initargs)
		{
			String blockClassName = "com.tablock.my_first_mod.block." + WordUtils.capitalize(id.name.replace('_', ' ')).replace(" ", "");
			Class<?>[] parameterTypes = new Class<?>[initargs.length];
			
			for(int index = 0; index < initargs.length; index++)
			{
				parameterTypes[index] = initargs[index].getClass();
			}
			
			try
			{
				return Class.forName(blockClassName + childClassName).getConstructor(parameterTypes).newInstance(initargs);
			}
			catch(Exception exception)
			{
				exception.printStackTrace();
				
				return null;
			}
		}
		
		private BlockEntity createBlockEntity(BlockPos blockPos, BlockState blockState)
		{
			return (BlockEntity) createInstance("$BlockEntityChild", blockPos, blockState);
		}
	}
	
	private static Item.Properties newItemProperties()
	{
		return new Item.Properties().tab(Main.MOD_TAB);
	}
	
	public String getName()
	{
		return name;
	}
	
	public Block getBlock()
	{
		return block.get();
	}
	
	public Item getItem()
	{
		return item.get();
	}
	
	public BlockEntityType<?> getBlockEntityType()
	{
		return blockEntityType.get();
	}
}

 

Link to comment
Share on other sites

11 hours ago, diesieben07 said:

Good lord why are you doing all this... stuff? This code could be so much shorter. But yes, from what I can tell it should be okay now.

I am doing it this way to save code and reduce repetition. Each value in the ID enum represents a unique namespace and contains variables that stores the RegistryObject of the block, item, block enitity, etc. These variables can be null. Moreover, if I want to add an item under the namespace "test_item", all I have to do is add one line to the ID enum: TEST_ITEM(new Register().item()). At this point, the other registry types are self-explanatory, .block() registers a block, .blockEntity() registers a block entity. There are many variants of these methods that you can see in the Registry class I created. The code is very long, I understand, but I would like to have a variable for each registry type (item, block, etc) so I can refer to them later. Having to manually create these variables especially when each declaration is very similar is tedious and annoying.

11 hours ago, diesieben07 said:
16 hours ago, Tablock_ said:

Also one question, why is it not ok to supply the Item constructor indirectly? I thought maybe because the game should be creating a new item object instead of reusing the same one. However, doesn't blocks and items use the same object anyway? I thought block entities created their own unique objects, that's why they can cause lag.

I am not sure what you mean by this.

I was asking you why it is not ok to do the following:

public static final Item ITEM = new Item(newItemProperties());

public static final RegistryObject<Item> TEST_ITEM = ITEMS.register("test_item", () -> ITEM);

I thought it was because whenever Supplier$get() is called it should be creating a new instance of the Item class, not reusing the same item object. But why would this be a problem? From my understanding, the game uses the same instance from Item class for every item of the same type. BlockEntities, however, have unique instances of the BlockEntity class for every block entity.

Edited by Tablock_
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • rp.crazyheal.xyz mods  
    • I'm developing a dimension, but it's kinda resource intensive so some times during player teleporting it lags behind making the player phase down into the void, so im trying to implement some kind of pregeneration to force the game loading a small set of chunks in the are the player will teleport to. Some of the things i've tried like using ServerLevel and ServerChunkCache methods like getChunk() dont actually trigger chunk generation if the chunk isn't already on persistent storage (already generated) or placing tickets, but that doesn't work either. Ideally i should be able to check when the task has ended too. I've peeked around some pregen engines, but they're too complex for my current understanding of the system of which I have just a basic understanding (how ServerLevel ,ServerChunkCache  and ChunkMap work) of. Any tips or other classes I should be looking into to understand how to do this correctly?
    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.