[1.6.3.20]Functionality of scanning common or rare ores becomes invalid

[nizhuan-jjr]

Whether the ores is vanilla or custom, the scanner won't show the location for them now.

Prepared to scan

Right after the scan

Actual location of the ores(left:oreGold; up:oreCoal; bottom:oreRuby(from Pixelmon Reforged 6.3.4); right: pixelmon:fire_stone_ore(from Pixelmon Reforged 6.3.4))

This is the scannable configuration file which I added the support to Pixelmon Reforged 6.3.4.
scannable.cfg.txt

[nizhuan-jjr]

The animal module and the monster module work fine.

[fnuecke]

Yeah, it still renders the results, they're just barely/not really visible due to OptiFine shaders and the scan effect/result rendering not being "compatible" so to say. Usually this just resulted in slightly off coloring/brightness, but it's much worse when the shaders use a gbuffer for example. I've just not had the time to work around this until now.

However! In the next build this should work with all kinds of shaders now, as I'm rendering the effect and results in the UI layer basically, which shaders shouldn't really touch anyway. This needs some extra work, so only doing that when shaders are actually in use, but yeah.