Dangers of Static Block Initialization

[Caffeinated Pinkie]

What exactly is the danger of doing the following:

public static final Block MOD_BLOCK = new ModBlock();

@SubscribeEvent
public static void onRegisterBlocks(Register<Block> event) {
  	MOD_BLOCK.setRegistryName("mod_block");
	event.getRegistry().register(MOD_BLOCK);
}

instead of:

public static Block MOD_BLOCK;

@SubscribeEvent
public static void onRegisterBlocks(Register<Block> event) {
 	MOD_BLOCK = new ModBlock();
  	MOD_BLOCK.setRegistryName("mod_block");
	event.getRegistry().register(MOD_BLOCK);
}

 

The Forge documentation is somewhat unclear on this topic, mainly just implying that it causes issues when introducing DeferredRegisters.

[Draco18s]

Because you never know when a static block will execute, and if it executes too early, Forge can't insure that it has full control over the object.

(Forge does lots of lots of behind the scenes magic and dangerous sorcery that you, as a modder, don't need to worry about, but that if it isn't done in order, things break)