lawremi / PerFabricaAdAstra

Through crafting, to the stars
http://pfaa.wikia.com/
Artistic License 2.0
17 stars 7 forks source link

Garnet Sand replaces Casserite Sand when using Geologica+GregTech oregen #31

Closed fnuecke closed 9 years ago

fnuecke commented 9 years ago

I'm having a strange issue when combining Geologica with GregTech. This happens using the default configurations, running CustomOreGen-1.7.10-1.2.15, PFAA-1.7.10-0.2.22 and gregtech_1.7.10-5.06.06. There are no warnings or otherwise related messages in the log.

First off, here's what seems to be working as intended:

Now what doesn't work as expected:

I'd expect Casserite Sand to still spawn in that case, or if anything, Small Casserite Ore. But Garnet Sand?

After some more experimentation (/cogSettingEx ... drawWireframe is awesome, by the way) it appears the Casserite Sand spawns again if I remove the Garnet Sand clouds from the Gregtech.xml. I also noticed that the wireframes perfectly overlap (as do those of the GraniticSand* stuff above, which I have also not seen spawn). I suspect the overlap leads to only one of the definitions always prevailing / there being too little space to spawn a mixture of the different ore types?

Some clarification on whether this is expected behavior (and if so, why) or whether this might be a bug (and if so, how to work around it) would be very much appreciated. Thanks!

PS: not sure if this is the right place, or if this should rather go onto the CustomOreGen tracker, because I can't tell where the actual issue comes from.

Edit: a few images to illustrate the issue: only GT oregen, only Geologica oregen, both enabled.

Dream-Master commented 9 years ago

Disable Gt oregen on the Overworld because PFAA have everything you need. In the Nether and the End you have Gregtech Ores than you have to disabled via Gui on Startup ore add manuell in CustomOreGen_Option.text in your save Folder:

GregtechGenOres=false GeologicaGenRocks=true GeologicaGenOres=true GeologicaGenPetroleum=true GeologicaOverride=true GeologicaGenCoal=true GeologicaGenIron=true GeologicaGenGold=true GeologicaGenLapis=true GeologicaGenDiamond=true GeologicaGenRedstone=true GeologicaGenCopper=true GeologicaGenTin=true GeologicaGenAluminum=true GeologicaGenMercury=true GeologicaGenLeadZinc=true GeologicaGenTungsten=true GeologicaGenNickel=true GeologicaGenChromium=true GeologicaGenTitanium=true GeologicaGenMolybdenum=true GeologicaGenManganese=true GeologicaGenUranium=true GeologicaGenApatite=true GeologicaGenSalt=true GeologicaGenQuartz=true GeologicaGenBIF=true GeologicaGenSandOres=true GeologicaGenVolcanic=true GeologicaGenSerpVeins=true GeologicaGenLaterites=true GeologicaGenIgVeins=true GeologicaGenIgIntrusion=true GeologicaGenEvaporite=true GeologicaGenVMS=true GeologicaGenSEDEX=true GeologicaGenPegmatite=true GeologicaGenCarbonate=true GeologicaGenBarite=true GeologicaGenMarine=true GeologicaGenGraphite=true GeologicaGenClay=true

lawremi commented 9 years ago

Acknowledging this. Probably an issue with CustomOreGen, but this issue is fine.

lawremi commented 9 years ago

Fixed in CustomOreGen git; will release soon.

fnuecke commented 9 years ago

Awesome. Thanks to both of you!