Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nether ores explode with new Netherending Ores config #1856

Closed
MorganSimic opened this issue Nov 24, 2020 · 5 comments
Closed

Nether ores explode with new Netherending Ores config #1856

MorganSimic opened this issue Nov 24, 2020 · 5 comments
Labels
Bug A modpack specific bug Config Status: Fixed In Next Release This issue has been fixed in the next (unreleased) version of the pack

Comments

@MorganSimic
Copy link
Collaborator

Modpack version
1.82a

Issue
With the new version of Netherending Ores, ores do now explode by default. There is a whole new config section, that wasn't there before, since i think that was not intentional.

Proposed fix:
Change true to false in the this segment of the netherending ores config.
"ore explosions" { # Enables the ability for ores to explode. [default: true] B:"Ore explosion"=true
Haven't checked yet, but there may be some other nasty suprises in the new config.

@MorganSimic MorganSimic added Config Bug A modpack specific bug labels Nov 24, 2020
@MorganSimic
Copy link
Collaborator Author

Yeah i checked, the new (1.4) version, also does now add mobs by default (the netherfish) and stuff, also changes the drop behaviour of ores by default now. Some ores now drop items instead of the ore block. Not sure if that is good change or not.
Also it has it's own config for angering pigmen, so that may conflict with AngerManagment.
This all isn't mentioned in the changelog of the mod, only on the curseforge feature page, it's mentioned what 1.4+ does.
So the config probably needs some serious clean up in general.

@NielsPilgaard
Copy link
Collaborator

I'm actually the one who requested these changes, like 2 years ago :P but I'll revert to the old version, thanks Morgan!

@MorganSimic
Copy link
Collaborator Author

Haha, okay. That i couldn't have anticipated. But i feel now, after two years players are so used to how it works, such a drastic change doesn't seem nice.

@NielsPilgaard
Copy link
Collaborator

Agreed :P

NielsPilgaard added a commit that referenced this issue Nov 27, 2020
@NielsPilgaard NielsPilgaard added the Status: Ready For Testing In-game testing of the issue is required label Nov 27, 2020
@joycourier
Copy link

Damn, that's a recent update that flew under the radar? I'll be honest, this update has been responsible for many a shitted pant.

@NielsPilgaard NielsPilgaard added Status: Fixed In Next Release This issue has been fixed in the next (unreleased) version of the pack and removed Status: Ready For Testing In-game testing of the issue is required labels Jul 3, 2021
SSyl pushed a commit to SSyl/Enigmatica2Expert-SSylTweaks that referenced this issue Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A modpack specific bug Config Status: Fixed In Next Release This issue has been fixed in the next (unreleased) version of the pack
Projects
None yet
Development

No branches or pull requests

3 participants