[SOLVED][1.16.5] Deferred register vs static register

[TonyOneG112]

Hi, I'm new on this,

1. can anyone tell me why use deferred and not use static? 

2. If I use deferred, how can I take a "declared" item/entity/block... Example: 

public static final DeferredRegister<EntityType<?>> ENTITIES = DeferredRegister.create(ForgeRegistries.ENTITIES, "livinglife");

public static final RegistryObject<EntityType<verruct>> VERRUCT = ENTITIES..register("verruct", () -> EntityType.Builder.<verruct>of(verruct::new, EntityClassification.MISC) .sized(0.98F, 0.7F) .clientTrackingRange(8) .build("verruct"));

vs

public static final EntityType<verruct> VERRUCT = (EntityType<verruct>) EntityType.Builder.of(verruct::new, EntityClassification.MONSTER).build("verruct") .setRegistryName("livinglife", "verruct");

 

why i ask that? because in second I can call "VERRUCT", in first idk how can i call it :(, any help it's fine ❤️

and is because i need to register render and register entity, code of register render:

public class onRendersEntity { public static void onRendersRegistry() { RenderingRegistry.registerEntityRenderingHandler((EntityType<verruct>) "HERE I PUT VERRUCT" , verructRenderer::new); LifeAndLive.LOGGER.debug("LIFE AND LIVE - Entity rendered"); } }

 

but idk how to call the entity when using deferred, i came to this because i'm having same problem of this thread: 

PDT, I'm still learning, sorry if this is obvious. 

Edited October 19, 2021 by TonyOneG112
Solved, close thread

[fweo]

If you're asking how to get the EntityType when using the DeferredRegister way, you can call VERRUCT.get() and that will get you the EntityType out of the registry object. You can do the same for any other type of registry object.

The only thing to be careful about is to make sure that the entities have actually been registered by the time you call VERRUCT.get(), but if you register your renderer at the right time that won't be a problem. In 1.17.1 you register renderers with the EntityRenderersEvent.RegisterRenderers event, I'm not sure about 1.16.5 but it's probably similar. This event will always fire after entities have been registered, so you can safely call the getter. 

You should use deferred registration because it ensures that your entities (or blocks, or whatever else you register) get registered at the right time. If everyone did this, it would allow forge to introduce a lot of useful features, such as reloading/enabling/disabling mods while the game is running. This is impossible to do with static initialisers. 

By the way, you can click the <> button while drafting your post and it will let you format your code like this:

RenderingRegistry.registerEntityRenderingHandler(VERRUCT.get(), verructRenderer::new);
LifeAndLive.LOGGER.debug("LIFE AND LIVE - Entity rendered"); 

 

[diesieben07]

8 hours ago, TonyOneG112 said:

can anyone tell me why use deferred and not use static? 

What do you mean by "static registration"?

8 hours ago, TonyOneG112 said:

2. If I use deferred, how can I take a "declared" item/entity/block... Example: 

public static final DeferredRegister<EntityType<?>> ENTITIES = DeferredRegister.create(ForgeRegistries.ENTITIES, "livinglife");

public static final RegistryObject<EntityType<verruct>> VERRUCT = ENTITIES..register("verruct", () -> EntityType.Builder.<verruct>of(verruct::new, EntityClassification.MISC) .sized(0.98F, 0.7F) .clientTrackingRange(8) .build("verruct"));

vs

public static final EntityType<verruct> VERRUCT = (EntityType<verruct>) EntityType.Builder.of(verruct::new, EntityClassification.MONSTER).build("verruct") .setRegistryName("livinglife", "verruct");

Registry entries such as EntityType must be initialized at a very specific time (during the registry event). If you don't do this, various problematic things can happen that aren't immediately obvious, specifically when your mod is installed on an already existing world, when your mod is removed from a world, etc. etc.

When you use a static initializer to create it, you have no precise control over when exactly the instance is created.

DeferredRegister ensures that your supplier is called at the correct time.

8 hours ago, TonyOneG112 said:

why i ask that? because in second I can call "VERRUCT", in first idk how can i call it :(, any help it's fine ❤️

You need to use the methods on RegistryObject, specifically the get method.