Ore Vein Detected by MV Prospector Scanner but Not Found

[ilushkabond]

Your GTNH Discord Username

ilushkabond

Your Pack Version

2.6.1

Your Server

private server

Java Version

Java 21

Type of Server

Vanilla Forge

Your Expectation

I used the "Prospector's Scanner MV" to locate an ore vein, and based on its detection, I expected to find a Casseterite ore vein starting at y=60 (the lowest value of Height=60-220 for this vein) and extending upwards to the surface. Additionally, the JourneyMap's "Show GT Ore Veins" feature displayed the area as containing a Casseterite vein. I anticipated that the vein would be present and could be mined.

The Reality

Despite following the height range for the Casseterite vein (y=60 to 220) and digging from y=60 up to the surface in the Overworld dimension, no ore vein was found. The "Prospector's Scanner MV" detection and JourneyMap overlay seem incorrect or misleading.

Seed:
6194098359988223730

Coordinates of vein center:
x = -1657 y = 77 z = -1177

Also I need to state, that server I am playing on was using bugged twilight forest file (TwilightForest-2.5.25.jar) and then client/server was patched by new version of mod:
https://github.com/GTNewHorizons/twilightforest/releases/tag/2.6.12

Screenshot from low Y value:

Screenshot from surface:

Created creative world with same seed, scanned ores nearby using Prospector's Scanner and detected "Mineralsand" instead of "Casseterite":

Tested with local server, issue with generation persist:

Your Proposal

Verify and fix potential mismatches between ore vein generation, prospector scanner detection, and JourneyMap overlays to ensure consistency and reliability.

Final Checklist

• 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.
• I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
• 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.

[chochem]

I remember some speedrunners complaining that gt generation is not consistent just based on seed. So that might explain your second world.

regarding the first, obviously you can cheat in an electric scanner and just check more clearly that way (for testing purposes). might just be some ore somewhere on the slope, it looks like you just checked the center.

but lyfts has been improving scanner accuracy a bit for 2.7 anyway.