Sulfur Ore can be found in Extreme Mountains and Extreme Mountains Edge Biomes or hilly biomes if using a biome mod. It is found around layer 10, but only near lava pools.
Direwolf20 1.7.10 Help, Venting and Discussion Thread
- Thread starter ScottulusMaximus
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
Sulfur Ore can be found in Extreme Mountains and Extreme Mountains Edge Biomes or hilly biomes if using a biome mod. It is found around layer 10, but only near lava pools.
I have a mailbox, which is the confusing part. Does the mailbox I'm using being owned by me have anything to do with it? It's not just me either, everyone on the server I'm on who has tried hasn't been able to send mail to the trade station despite owning a mailbox.
Niter is found under the sand in a desert as for sulfer i had mine from the aroma mineing world what i installed to keep my overworld tidy with no holes everywere
In the PneumaticCraft config file, there's a part that lets you turn off plants spreading.
Hi All,
Has anyone else had issues with Golems harvesting oreberries. I have a 9x9 lined with Oreberry. 2 Stonegolems, 1 Harvest and 1 Gather and a chest in the center. The Harvest Golem just ignores the Oreberry completely.
Has anyone else had issues with Golems harvesting oreberries. I have a 9x9 lined with Oreberry. 2 Stonegolems, 1 Harvest and 1 Gather and a chest in the center. The Harvest Golem just ignores the Oreberry completely.
Disable the not enough keys mod in the mods folder. Its a client side mod which got dropped in the server files by accident i think.
I was not aware of this, thank you. However you caught me at a bad time because its midnight for me, so you'll get them tomorrow. Sorry about that
Yeah, I didn't even know 1.0.2 was out already. I wish the launcher would "announce" this fact somehow, instead of keeping the "Recommended" setting at 1.0.1
It seems the only way I ever learn about the even-numbered updates is thru the forums via reading random posts. Now we just need to see that changelog! I sure hope Forge got "rev'ved up" so we can run j8u25 finally...
Here's what I found by examining the mod list in-game... In 1.0.2, Forge is v10.13.2.1231 and I'm trying to find if that's the latest version - okay it was released on Oct 17 which means it is still one month old. And I see Forge Multipart is still listed as v1.1.0.310 which means its the same version as was included in Dire v1.0.1 modpack from October 1 (build 314 is the latest)... and therefore, IMO the j8u20 problems are still included, so noone should update their java at this point. That's a shame.
Update: I did more searching, and found this. Buried in that changelog for Forge Build 1217 is the fix for the j8u20 problems... it's this one: "Fix java 8u20. Closes #501 and a bunch of other bugs too." So that means this issue has been resolved for a long time now - Build 1217 was released way back on September 14th! Pretty confusing, perhaps someone who understands the development of Forge better than I do can comment and confirm? Perhaps this explains why there have been some people who pop up on the forums saying "I'm running j8u25 and Direwolf modpack just fine!"
One last link for anyone following this mess, it might help explain what's going on better than me.
Final update: Add me to the list of those running Direwolf 1.7.10 just fine with j8u25... so my problem (in the future) will only be if I want to go back to an older modpack like Dire 1.6.4 and play one of my saved worlds... those probably won't work and I'll have to install j7 to run them.
It seems the only way I ever learn about the even-numbered updates is thru the forums via reading random posts. Now we just need to see that changelog! I sure hope Forge got "rev'ved up" so we can run j8u25 finally...
Here's what I found by examining the mod list in-game... In 1.0.2, Forge is v10.13.2.1231 and I'm trying to find if that's the latest version - okay it was released on Oct 17 which means it is still one month old. And I see Forge Multipart is still listed as v1.1.0.310 which means its the same version as was included in Dire v1.0.1 modpack from October 1 (build 314 is the latest)... and therefore, IMO the j8u20 problems are still included, so noone should update their java at this point. That's a shame.
Update: I did more searching, and found this. Buried in that changelog for Forge Build 1217 is the fix for the j8u20 problems... it's this one: "Fix java 8u20. Closes #501 and a bunch of other bugs too." So that means this issue has been resolved for a long time now - Build 1217 was released way back on September 14th! Pretty confusing, perhaps someone who understands the development of Forge better than I do can comment and confirm? Perhaps this explains why there have been some people who pop up on the forums saying "I'm running j8u25 and Direwolf modpack just fine!"
One last link for anyone following this mess, it might help explain what's going on better than me.
Final update: Add me to the list of those running Direwolf 1.7.10 just fine with j8u25... so my problem (in the future) will only be if I want to go back to an older modpack like Dire 1.6.4 and play one of my saved worlds... those probably won't work and I'll have to install j7 to run them.
Last edited:
DW and others had been talking about a update for atleast for a week or 2. I think when it slides to recommended, you are notified when you start the modpack that there is an update.