Hi,

 

I've got a small question about Forge:

 

- For what are all these loading states? (For do they, why have they to be there etc.)

 

I came up with this question because I wondered for a long time for what the reloading texture manager state is and before I'm asking here for every state

I come up with a question I'm just asking for all states at once.

 

Thx in advance.

Bektor

Are you talking about the loading states like "pre init", "init", "post init", "server started" and such?

 

One major use for these is to manage features of your mod that might interact with other mods. The reason is that if the user has multiple mods applied to their game, when starting up it will first call pre-init on all those mods, then init on all those mods, then post init on all those mods. Therefore, if you put code in your post-init, you will know that all the other mods have already finished their pre-init and init stages.

 

So for example if your mod allowed people to make a statue using the model of an entity, and you wanted your mod to include the ability to make statues of entities from other people's mods, then you'd want to grab the models during the post-init -- so you could be certain the other mods' entities are all registered along with their renderers.

 

There are also some standard things that are meant to be done in certain stages. At least you shouldn't do them any earlier. Like registering blocks, events, commands, etc. each have their appropriate place.

 

There are also some standard things that are meant to be done in certain stages. At least you shouldn't do them any earlier. Like registering blocks, events, commands, etc. each have their appropriate place.

 

Pretty much all of those are pre-init.  Registering blocks, items, entities, and all renderers must occur in pre-init.

Recipes can be done anywhen, as can events.

I mean the loading states in the nice splash screen when starting Minecraft: like I can see there stuff like reloading texture manager state etc.