Ah, nice. They fire from dispensers too, so you can set your fireworks up and trigger them with redstone from a distance. Add a diamond to the star recipe and it makes a neat effect. Add a fire charge to the star recipe to create a larger explosion. Adding glowstone dust to the star recipe adds a twinkle effect. You can also add multiple stars to a rocket and they will explode at the same time. Add a gold nugget to the star recipe and you get a star-shaped explosion. *deep breath* Add a feather to the star recipe and the explosion particles scatter randomly in a burst. Wow, they got REALLY detailed with this fireworks thing.
May I suggest adding a signed book to the star recipe so it writes whatever the first line of the book is in the sky. It'd make for an awesome Game Over message at the end of adventure maps.
-
- DraxisWuf
- Registered Member
-
Member for 13 years, 3 months, and 5 days
Last active Tue, Apr, 24 2018 21:52:04
- 0 Followers
- 1,171 Total Posts
- 83 Thanks
0
0
0
You may be falling victim to the 128+ vanilla Minecraft bug. Any biome id greater than 128 is considered a sub-biome by Minecraft. If you've got any biomes in that range it can cause all sorts of issues. Unfortunately it looks like from this point forward we can't have any more than 128 biomes, minus the default Minecraft ones of course.
0
Update your Forge.
In other news, it looks like Adubbz definitely added code to supposedly fix the 128+ sub-biome issue. I found the commit in the repository. However, if the fix ever did work it's definitely not working now. Perhaps the fix was negated due to an upgrade in Forge since it was made. I'm going to try downgrading my Forge and testing it like that. However, many mods I use require the latest recommended Forge, so that's definitely not a final solution if it does work.
0
No, it's a 'bug' related to vanilla Minecraft where any biome with an id greater than 128 is considered a sub-biome of whichever biome has an id equal to that biome's id -128. Get it? Supposedly Adubbz was going to implement a workaround, but I'm not sure if that was ever done for 1.7.10.
Anyway, I may have figured it out though. It seems like Mariculture borks up the BoP world generator pretty noticeably. I think it may be overriding whatever fix Adubbz implemented because I haven't encountered the sub-biome bug since removing it. Or I could just be incredibly lucky/unlucky in my testing. Which is why I asked if the bug had been taken care of in 1.7.10.
EDIT: Nope, definitely still an issue. Ran into a Fire Swamp biome next to a Storage Cell biome from AE2. Is there any way you might be willing to fix this issue for 1.7.10 Adubbz?
1
Promised land and a number of other, smaller features such as healing springs, puddles, and poison ivy were cut out of the 1.7.10 version. The devs are now busy with 1.8, so it will likely never be added back to this version. Wait for the 1.8 release if it really bothers you that much.
Speaking of which, I'm still having sub-biome issues with other mod's biomes with ids greater than 128 generating in a BoP world. I was under the impression this was fixed. Is it not possible to revisit this bug in 1.7.10 or will I need to wait for 1.8? Unfortunately the 1.7.10 version of BoP seems rather half-baked.
0
1
0
Yeah, that's one of two problems with the current version that are keeping me from adopting it full-time. The biomes F3 report are nothing like the biomes you actually see. Often multiple BoP biomes will appear in a larger RWG-named biome. And rivers do not have their own biome designation. I'm hoping this is something he can fix, as it borks 90% of biome-dependent mods. Everything from generation mods to Forestry bees.
1
0
at net.minecraftforge.oredict.ShapedOreRecipe.<init>(ShapedOreRecipe.java:89)
at com.cricketcraft.chisel.Features$5.addRecipes(Features.java:145)
at com.cricketcraft.chisel.Features.loadRecipes(Features.java:2519)
at com.cricketcraft.chisel.Features.init(Features.java:2476)
at com.cricketcraft.chisel.Chisel.init(Chisel.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:513)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304)
at com.google.common.eventbus.EventBus.post(EventBus.java:275)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:208)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:187)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304)
at com.google.common.eventbus.EventBus.post(EventBus.java:275)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:118)
at cpw.mods.fml.common.Loader.initializeMods(Loader.java:691)
at cpw.mods.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:288)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:541)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:867)
at net.minecraft.client.main.Main.main(SourceFile:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
EDIT: And this different crash is from the version you upload to, I assume, fix the last crash (2.3.1):
at cpw.mods.fml.common.LoadController.transition(LoadController.java:162)
at cpw.mods.fml.common.Loader.initializeMods(Loader.java:692)
at cpw.mods.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:288)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:541)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:867)
at net.minecraft.client.main.Main.main(SourceFile:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
Caused by: java.lang.NoClassDefFoundError: com/cricketcraft/chisel/block/BlockMarbleSlab
at com.choonster.chiselfacades.ChiselFacades.init(ChiselFacades.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:513)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304)
at com.google.common.eventbus.EventBus.post(EventBus.java:275)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:208)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:187)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304)
at com.google.common.eventbus.EventBus.post(EventBus.java:275)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:118)
at cpw.mods.fml.common.Loader.initializeMods(Loader.java:691)
... 10 more
Caused by: java.lang.ClassNotFoundException: com.cricketcraft.chisel.block.BlockMarbleSlab
at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:191)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 37 more
Caused by: java.lang.NullPointerException
EDIT2: Nevermind. This latest error appears to be a problem with ChiselFacades. Guess I'll need to wait for an update to that.
0
Well the main difference being, in my opinion, that in the interim between 1.6.4 and 1.7.2 many modders were still doing great things in 1.6.4. Now, between 1.7.10 and 1.8, it feels like a veritable ghost town. Many prominent modders have even stated that they're not even going to attempt the transition to 1.8 when a stable Forge becomes available.
0
I once said 1.5.2 was the peak of Minecraft modding, but with time 1.6.4 proved me wrong. But now with 1.8 looming for quite some time it feels as though 1.7.2 hasn't even managed to catch up yet with the breadth and variety of mods we had for 1.6.4. Many modders have 'phoned in' 1.7+ updates for their 1.6.4 mods with nary a peep about new additions, much less 1.8 support.
So am I crazy? Is the Mincraft modding community as rich an vibrant as it's always been? Will it continue to be so on into the future?
0
He's referring to the borked-up name. At least I think he is. That's been an issue off and on since 1.6.4
0
Yes it is. What makes you say that?
Also, I'm still, after all this time, having an issue where text and any non-opaque block like glass appears behind the clouds. This is an old bug. Is there no way to fix it?