Describe the Bug

The 0.5.1 update broke almost every addon to create. some of them have recovered since but most are still broken. i'd like you to re-add whatever this is i pulled out of the logs of my minecraft server i was just creating:
'com.tterrag.registrate.util.nullness.NonNullSupplier com.simibubi.create.foundation.data.CreateRegistrate.lazy(java.lang.String)'
It WAS a method but doesn't exist now:
§7java.lang.NoSuchMethodError: 'com.tterrag.registrate.util.nullness.NonNullSupplier com.simibubi.create.foundation.data.CreateRegistrate.lazy(java.lang.String)'

It happens in both 1.19 and 1.20.

Reproduction Steps

1. Add (almost) any create addon
2. Launch Minecraft or Minecraft Server
3. See the game crash and in the logs, all the create addons which are incompatible with 0.5.1 fail to load.
   ...

Expected Result

Game Doesn't crash and i can use whatever create addon i wish, like before 0.5.1.

Screenshots and Videos

No response

Crash Report or Log

There is no specific log. you can make one yourself with the recipe above.

Operating System

Windows 11

Mod Version

0.5.1d

Minecraft Version

1.19.2

Forge Version

There is no specific forge version. it should work on any version create works on.

Other Mods

(almost) any create addon mod. (or set of them)

Additional Context

This is causing trouble all around the create community. it will take forever for ALL the create addons to make themselves compatible.

Please just PLEASE make it compattible here instead it will fix them all at once!

Longest issue in the world. also the most important.

It will not be re-added. It is the addons' responsibility to update. The method was deprecated for removal and its replacement was added in commit 131c9a5, which was pushed around 9 months ago and released as part of 0.5.0g around one month after. The method was removed in 0.5.1a, which was released about 3 months ago. Addon developers had at least 5 months to update their addons to remove usage of this method, but some did not do this until it was removed and started causing issues. It is not our responsibility to resolve those issues given the extensive time frame that developers had to update their addons to remove usage of the method.

It will not be re-added. It is the addons' responsibility to update. The method was deprecated for removal and its replacement was added in commit 131c9a5, which was pushed around 9 months ago and released as part of 0.5.0g around one month after. The method was removed in 0.5.1a, which was released about 3 months ago. Addon developers had at least 5 months to update their addons to remove usage of this method, but some did not do this until it was removed and started causing issues. It is not our responsibility to resolve those issues given the extensive time frame that developers had to update their addons to remove usage of the method.

well i'm not a mod developer (even though i'm good at Java Programming) and i didn't know that. but none of the addons seem to have notice. some are even thinking that the issue is fixed when it's not. And they definetly got more than enough time to update to the new method. they just didn't notice. like i said this is STILL a big problem. (that was only one solution)

Well if you want addons to regain compatibility you should be telling them to update, not the other way around

i already told create big cannons.