Configured features need to be properly registered
Sinhika opened this issue ยท 0 comments
Versions
- Silent's Mechanisms: 1.16.3-0.8.8+73
- Silent Lib: 1.16.3-4.9.0+63
- Forge: 35.1.13
- Modpack: Custom test pack of all SimpleOres2 and SimpleOres add-ons, Silent Gear, Silent's Mechanisms, required libs, and Blame 1.7.4
Expected Behavior
- Blame is a mod that checks for unregistered ConfiguredFeature(s), ConfiguredStructure(s) and ConfiguredCarver(s). It then squawks in the log files about which features appear to be unregistered, identifying them by the blocks they generate and other parameters.
- If everything was correctly registered, I would expect Blame to be silent and have nothing to say in the log file.
Actual Behavior
- Blame dumps a detailed log of unregistered features attached to silents_mechanisms. Summary of the report:
`
****************** Blame Report 1.7.4 ******************
This is an experimental report. It is suppose to automatically read
the JSON of all the unregistered ConfiguredFeatures, ConfiguredStructures,
and ConfiguredCarvers. Then does its best to collect the terms that seem to
state whose mod the unregistered stuff belongs to.
Possible mods responsible for unregistered stuff:
silents_mechanisms:bauxite_ore
silents_mechanisms:bismuth_ore
silents_mechanisms:copper_ore
silents_mechanisms:lead_ore
silents_mechanisms:nickel_ore
silents_mechanisms:platinum_ore
silents_mechanisms:silver_ore
silents_mechanisms:tin_ore
silents_mechanisms:uranium_ore
silents_mechanisms:zinc_ore
`
Links/Images
- I had someone point out the problem in my own mods here, and explain why it was an important issue: Sinhika/SimpleOres2#46.
- If you need reference code, I have updated SimpleOres2 and SimpleCoreLib to configure features properly.
Steps to Reproduce the Problem
- Create a Minecraft profile/instance with SilentLib, Silent's Mechanisms, and Blame.
- Generate a new world.
- Examine latest.log, searching for "Blame". You will find a detailed report.