VisualProspecting Identifying Ore Veins Incorrectly

[SamuelPtolemyDawson]

Your GTNH Discord Username

Lazorati\9174

Your Pack Version

2.7.0 Beta 4

Your Server

SP

Java Version

Java 19

Type of Server

Single Player

Your Expectation

For Visual Prospecting to correctly record my ore vein data and display properly to Journeymap.

The Reality

When upgraded my world to Beta 4, I ensure to move across Journeymap and VisualProspecting data. However, I've noticed that veins are all being identified incorrectly. Existing 'found' veins have had their labels changed, and newly prospected ones are being identified incorrectly. Below screenshot shows a vein being newly scanned in beta 4 with an LV Prospector's Scanner - the chat readout identified it as a Terra & Aer vein, despite being in the overworld. However it also detects ores typical of an Apatite vein.

Example of existing prospecting data that has been changed, after being ported over from Beta 3. The highlighted Naquadah vein was in fact a Mica vein.

Your Proposal

For ore veins to be correctly identified and recorded.

Final Checklist

• [X] I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the bug still exists will prompt us to investigate and reopen it once we confirm your report.
• [X] I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
• [X] I have asked other people and they confirm they also have this problem by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.

[Lyfts]

Did you delete/forget to copy the veintypesLUT file in the visualprospecting folder?