-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
Comments
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. |
I'm actually the one who requested these changes, like 2 years ago :P but I'll revert to the old version, thanks Morgan! |
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. |
Agreed :P |
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. |
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.
The text was updated successfully, but these errors were encountered: