NetherEx Quartz changing to Assorted Quartz in the nether when approached #128

Closed
opened 2018-06-01 01:11:01 +00:00 by import_user_oitsjustjose_95mQ · 3 comments
import_user_oitsjustjose_95mQ commented 2018-06-01 01:11:01 +00:00 (Migrated from git.oitsjustjose.com)

Versions:

  • Minecraft Forge: 14.23.3.2702
  • Geolosys: 1.12.2-1.9.3

What happens:

When in the nether NetherEx Ores(gloomy/lively/fiery/icey quartz ore, a quartz which uses the same background as gloomy/lively netherrack and netherrack quartz which is essentially vanilla nether quartz) convert to assorted quartz in the nether. other mods might be as well, it's hard to tell as they seem to change before I can get close enough to see the item name. Vanilla quartz seems unchanged.

What should happen:

nothing, I think, for the most part the netherex ores should remain as they are unless they're disabled.

Logs (if necessary):

Additional Comments:

## Versions: - Minecraft Forge: 14.23.3.2702 - Geolosys: 1.12.2-1.9.3 ## What happens: When in the nether NetherEx Ores(gloomy/lively/fiery/icey quartz ore, a quartz which uses the same background as gloomy/lively netherrack and netherrack quartz which is essentially vanilla nether quartz) convert to assorted quartz in the nether. other mods might be as well, it's hard to tell as they seem to change before I can get close enough to see the item name. Vanilla quartz seems unchanged. ## What should happen: nothing, I think, for the most part the netherex ores should remain as they are unless they're disabled. ## Logs (if necessary): ## Additional Comments:
import_user_oitsjustjose_95mQ commented 2018-06-01 01:25:38 +00:00 (Migrated from git.oitsjustjose.com)

This is a result of Retroactively replace existing ores in world = true

If you don’t want ores to be exchanged for Geolosys ones, set this to false.

This is a result of `Retroactively replace existing ores in world` = true If you don’t want ores to be exchanged for Geolosys ones, set this to false.
import_user_oitsjustjose_95mQ commented 2018-06-01 01:36:02 +00:00 (Migrated from git.oitsjustjose.com)

Is there a way to specify this by dimension or modid?
I would prefer it do it in the overworked but not the nether.

On Thu, May 31, 2018, 8:25 PM Jose notifications@github.com wrote:

This is a result of Retroactively replace existing ores in world = true

If you don’t want ores to be exchanged for Geolosys ones, set this to
false.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
http://git.oitsjustjose.com/oitsjustjose/Geolosys/-/issues/128#issuecomment-393731050,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADeUEDulhZPdmBXNtOz2AEj_33YTGLgAks5t4JgSgaJpZM4UV868
.

Is there a way to specify this by dimension or modid? I would prefer it do it in the overworked but not the nether. On Thu, May 31, 2018, 8:25 PM Jose <notifications@github.com> wrote: > This is a result of Retroactively replace existing ores in world = true > > If you don’t want ores to be exchanged for Geolosys ones, set this to > false. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <http://git.oitsjustjose.com/oitsjustjose/Geolosys/-/issues/128#issuecomment-393731050>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ADeUEDulhZPdmBXNtOz2AEj_33YTGLgAks5t4JgSgaJpZM4UV868> > . >
import_user_oitsjustjose_95mQ commented 2018-06-01 13:05:40 +00:00 (Migrated from git.oitsjustjose.com)

Alright, I'll probably add a block blacklist for the ore converter, so that if you don't want a specific block to be converted you can say so.

That'll probably come out in the 1.9.4 release - I've gotta write it first.

Alright, I'll probably add a block blacklist for the ore converter, so that if you don't want a specific block to be converted you can say so. That'll probably come out in the 1.9.4 release - I've gotta write it first.
import_user_oitsjustjose_95mQ (Migrated from git.oitsjustjose.com) closed this issue 2018-06-04 00:41:41 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
oitsjustjose/Geolosys#128
No description provided.