What is the advantage of using DeferredRegisters instead of RegistryEvent ?

It's a modern, simple, and easy way of registering things. It also prevents the previously common problems caused by instantiating registry objects in static initializers.

There isn’t really a program-wise advantage for using deferred registry (deferred registry still subscribes to the registry event); however, it is more convinient and simpler to use.

42 minutes ago, DavidM said:

There isn’t really a program-wise advantage for using deferred registry

Yes there is. It solves the issue of people registering their blocks and items in a static (UNCONTROLLED) location. Forge can't control/verify the domain paths when ResourceLocations are created statically.

Edited May 11, 20205 yr by Draco18s

Ok, I see, thanks

8 hours ago, Draco18s said:

Yes there is. It solves the issue of people registering their blocks and items in a static (UNCONTROLLED) location.

I thought the OP was comparing DeferredRegistry to RegistryEvent, and therefore assumed that static initialization is not involved (it is a programmer screw-up rather than a code-wise problem)

17 minutes ago, DavidM said:

I thought the OP was comparing DeferredRegistry to RegistryEvent, and therefore assumed that static initialization is not involved (it is a programmer screw-up rather than a code-wise problem)

You can still static-create things before registering them with the event.

DeferredRegistry precludes that entirely.

If a modder writes things correctly, then there is no functional difference between the two. As DeferredRegistry is just a proper implementation of using ObjectHolders and Register event.

DeferredRegister was literally created as a helper for people who can't get it around their head to NOT statically initialize things. So it moves the thing that is bad to statically initialize {the registry objects} to the Register event behind the scenes. That's it. It's nothing special.