How best to avoid "Dangerous alternative prefix" when overriding registry entries?

[Choonster]

When overriding a registry entry, the replacement needs to have the same registry name as the original. This requires setting the registry name to one with a domain that isn't your mod ID, but attempting to do so logs the "Dangerous alternative prefix" warnings and ignores the domain you specified, using your mod ID instead.

 

Is there a better way to avoid this than temporarily replacing the active ModContainer with the Minecraft ModContainer when setting the registry name and setting it back to the previous ModContainer when registering the override?

[LexManos]

26 minutes ago, Choonster said:

attempting to do so ... using your mod ID instead.

https://github.com/MinecraftForge/MinecraftForge/blob/1.12.x/src/main/java/net/minecraftforge/registries/IForgeRegistryEntry.java#L86

 

No it doesn't... And you shouldn't be fucking with the active mod container.

[Choonster]

1 minute ago, LexManos said:

https://github.com/MinecraftForge/MinecraftForge/blob/1.12.x/src/main/java/net/minecraftforge/registries/IForgeRegistryEntry.java#L86

 

No it doesnt...

 

Sorry, I misread the code and thought oldPrefix was the mod ID rather than the specified domain.

 

Still, is there a proper way to avoid this warning?

[LexManos]

No, not right now. The amount of people who screw this up accidently outweighs those who do it intentionally. So you're stuck dealing witht eh idiots. For now, just deal with the log lines.