[1.12.2] Handling "obsolete" blocks and items

[Kinniken]

Hi all,

 

I would like to know if there is a good way to make blocks and items "obsolete" in new versions of a mod. As far as I know there are two ways of dealing with this:

- Delete them from the mod. The cleanest, but popups an ugly-looking warning to players who upgrade existing worlds.

- Keep them in the mod, but make them unavailable. That avoids the issue above but then the mod is stuck with dead items/blocks for ever, removing them later just ends up with the same issue as in the first option.

 

Any better option?

 

Thanks

[V0idWa1k3r]

5 hours ago, Kinniken said:

Any better option?

Um, what other options are you looking for exactly? You can either delete the stuff you don't need or don't. Can you describe what you want to happen? If the world loads up with some registry entries missing it will always tell the player about that and there is no way around that nor should there be.

[Kinniken]

Some way of declaring an item obsolete so it neither generates warnings in old worlds nor get added to the registry of new worlds I guess.

 

"it will always tell the player about that and there is no way around that nor should there be."

 

If that is indeed the case then I have no choice... Ah well, would have been nice not to have to chose between keeping my code clean and scaring users with nasty-looking warnings.

 

[Animefan8888]

On 11/1/2018 at 10:04 AM, Kinniken said:

Some way of declaring an item obsolete so it neither generates warnings in old worlds nor get added to the registry of new worlds I guess.

You can do this in the MissingMappingEvent.

[Kinniken]

Oh, great! Thanks @Animefan8888. This can be used to "drop" mappings, not just change them? Exactly what I needed.