Titanium/Ilmenite Ore not generating
PlayerDot opened this issue ยท 3 comments
Bug Description
Titanium is an ore obtained by mining Ilmenite Ore in Galacticraft's Tier 3 Asteroids dimension. I spent a ridiculous amount of time using Tinker's Construct tools, Blood Magic picks, RF Tools' Builder Silktouch quarry etc. to try and locate asteroids containing Ilmenite/Titanium but even after I found 10 diamond asteroids and 16 meteoric iron block asteroids (which, according to the wiki, have <2% chance of being generated!) and spent 3 hours loading new chunks to mine out the asteroids, I haven't found a single one containing titanium. Titanium is either not being generated or has its weight set to such ridiculously low levels that it's virtually impossible to find, which makes it really difficult to advance to Tier 4 and continue towards Mystical Agriculture. Another thing to note is that I haven't found a single silicon asteroid either, even though they're supposed to be more common than diamonds and meteoric iron blocks.
Did this behavior use to work in the previous version?
Probably. I played on a friend's server 2 versions ago and she got to Mystical Agriculture.
Steps to Reproduce (for bugs)
- Reach Asteroid Belt
- Spent many hours searching for Titanium/Ilmenite Ore
- Find nothing
Client Information
- Modpack Version: 3.1.3
- Java Version: Java 8 Update 251
- Launcher Used: Twitch
- Memory Allocated: 6 gb
- Server/LAN/Single Player: Single Player/LAN
- Optifine Installed: Yes
- Shaders Enabled: No
World Information
- Modpack Version world created in: 3.1.3
- Additional Content Installed: /
Hi
Using the scanner set with 1 rare addon + 2 range addons was able to find an asteroid in 15-20 minutes that had ilmenite ore in center. It was about 1000 blocks distance away from portal entry in asteroid dimension.
I got more than 10 stacks of ilmenite ores.
Used normal space equipment + visio wand astral sorcery + scanner + obsidian pick unbreakable with vein mine.
@PlayerDot: hello! ๐
This issue is being automatically closed because it does not follow the issue template.