Closed bdew closed 6 years ago
The easiest option (and it really shouldn't be a problem) would be to switch over to the Minecraft mod container when registering those, then switch back to yours. I've had to do it in the past. Also, I guess I should consider managing the registry in MCMP itself, so you can add microblocks via a config file. That way there are no overlaps if multiple mods try to register the same blocks, and those that want to register their own stuff via registry events, still can. That's not a huge priority right now, though.
Closing since amadornes has given a solution to the problem and this has been inactive for a while.
Since MicroMaterialBlock registers with the modid that owns the block, which isn't the mod that does the registration, forge emits hundreds of those warnings....
I wonder if lex would be willing to add an option to silence the warning for non-vanilla registries...