---- Minecraft Crash Report ----
// I just don't know what went wrong
Time: 5/3/16 1:45 PM
Description: FML has discovered extracted jar files in the mods directory.
This breaks mod loading functionality completely.
Remove the directories and replace with the jar files originally provided.
java.lang.RuntimeException: Extracted mod jars found, loading will NOT continue
at net.minecraftforge.fml.relauncher.CoreModManager.discoverCoreMods(CoreModManager.java:298)
at net.minecraftforge.fml.relauncher.CoreModManager.handleLaunch(CoreModManager.java:246)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupHome(FMLLaunchHandler.java:95)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupClient(FMLLaunchHandler.java:72)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.configureForClientLaunch(FMLLaunchHandler.java:34)
at net.minecraftforge.fml.common.launcher.FMLTweaker.injectIntoClassLoader(FMLTweaker.java:119)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:115)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- System Details --
Details:
Minecraft Version: 1.8.9
Operating System: Mac OS X (x86_64) version 10.10.5
Java Version: 1.8.0_74, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 55907880 bytes (53 MB) / 127139840 bytes (121 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 5 total; -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
---- Minecraft Crash Report ----
// I just don't know what went wrong
Time: 5/3/16 1:45 PM
Description: FML has discovered extracted jar files in the mods directory.
This breaks mod loading functionality completely.
Remove the directories and replace with the jar files originally provided.
java.lang.RuntimeException: Extracted mod jars found, loading will NOT continue
at net.minecraftforge.fml.relauncher.CoreModManager.discoverCoreMods(CoreModManager.java:298)
at net.minecraftforge.fml.relauncher.CoreModManager.handleLaunch(CoreModManager.java:246)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupHome(FMLLaunchHandler.java:95)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupClient(FMLLaunchHandler.java:72)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.configureForClientLaunch(FMLLaunchHandler.java:34)
at net.minecraftforge.fml.common.launcher.FMLTweaker.injectIntoClassLoader(FMLTweaker.java:119)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:115)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- System Details --
Details:
Minecraft Version: 1.8.9
Operating System: Mac OS X (x86_64) version 10.10.5
Java Version: 1.8.0_74, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 55907880 bytes (53 MB) / 127139840 bytes (121 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 5 total; -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
plz fix this cause this mod looks epic!
It looks like you put the wrong thing in your mods folder.
EDIT: Somebody also had this problem. I want to say that i have the latest Lucky block version with the latest Spiral Addon version (v1.10 for MC 1.8.9 right?). Tried redownloading the mods 3 times for both 1.8 and 1.8.9. The same problem was occuring. Also I checked for duplicated mods but I didn't find anything. Please don't leave me alone D:
---- Minecraft Crash Report ----
WARNING: coremods are present:
Contact their authors BEFORE contacting forge
// My bad.
Time: 3/7/2016 1:52 PM
Description: There was a severe problem during mod loading that has caused the game to fail
net.minecraftforge.fml.common.LoaderException: java.lang.IllegalArgumentException: The name lootplusplus:spiral.gingerbread_stairs has been registered twice, for Block{lootplusplus:spiral.gingerbread_stairs} and Block{null}.
at net.minecraftforge.fml.common.registry.GameRegistry.registerBlock(GameRegistry.java:286)
at net.minecraftforge.fml.common.registry.GameRegistry.registerBlock(GameRegistry.java:226)
at com.tmtravlr.lootplusplus.config.ConfigLoaderBlocks.loadBlockAdditions(ConfigLoaderBlocks.java:737)
at com.tmtravlr.lootplusplus.LootPlusPlusMod.afterInit(LootPlusPlusMod.java:218)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at net.minecraftforge.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:560)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
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 net.minecraftforge.fml.common.LoadController.sendEventToModContainer(LoadController.java:211)
at net.minecraftforge.fml.common.LoadController.propogateStateMessage(LoadController.java:189)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
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 net.minecraftforge.fml.common.LoadController.distributeStateMessage(LoadController.java:296)
at net.minecraftforge.fml.common.Loader.initializeMods(Loader.java:740)
at net.minecraftforge.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:310)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:495)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:329)
at net.minecraft.client.main.Main.main(SourceFile:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
Caused by: java.lang.IllegalArgumentException: The name lootplusplus:spiral.gingerbread_stairs has been registered twice, for Block{lootplusplus:spiral.gingerbread_stairs} and Block{null}.
at net.minecraftforge.fml.common.registry.FMLControlledNamespacedRegistry.add(FMLControlledNamespacedRegistry.java:437)
at net.minecraftforge.fml.common.registry.GameData.registerBlock(GameData.java:125)
at net.minecraftforge.fml.common.registry.GameRegistry.registerBlock(GameRegistry.java:276)
... 40 more
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
Hmm... Yeah, that's not good. I'm curious about what's in the block additions folder. Open up the zip download, and look in the file config/block_additions/stairs.txt. What do you see?
Lets guess, the spiral.fingerbread_stairs is the texture, the Gingerbread Stairs is the in-game block name and the lootplusplus:gingerbread is the data for the Loot++, but what is that 0 in the end?
Will it survive, doctor? D:
EDIT: I found this in the generic folder (inside the block_additions)
The first part is the item id, the second the item name like you said, and the third and fourth are the block and metadata to inherit properties from (in this case, the gingerbread you found in the other file).
I'm about to release a new version of Loot++ with bugfixes (version 1.7.1). Maybe try it with that when it comes out.
I feel like something is wrong where I hear some boss music playing such as the Grim's and another boss and nothing spawns but only changes difficulty to hard and music plays. Feels like an error towards the Loot ++ mod and not sure what is up on that side.
EDIT: Apparently i had a old version of loot ++ this whole time and never notice it till now. and strange enough had 1.9 spiral lucky block version which was for 1.8.9 i think, so change 1.9 for the 1.8 version and useing a higher version of loot ++ now, going to test them out now after double checking the other lucky block mods i had for their right version.
Nevermind, I deleted the Loot++ and the lucky_block folders from .minecraft/config and it worked... But thank you very much and sorry...
Aha!
You must have had block additions in your Loot++ config file. Had you ever run spiral lucky blocks in 1.7.10 before? That used the Loot++ configs to load the blocks and items (as the addon system was added in 1.8).
Just fyi, it's always better to create a new folder if you are running minecraft modded to avoid things like this! =P I usually make a folder like .other_minecraft/Lucky Blocks 1.8.9 and point the vanilla launcher to that folder.
You must have had block additions in your Loot++ config file. Had you ever run spiral lucky blocks in 1.7.10 before? That used the Loot++ configs to load the blocks and items (as the addon system was added in 1.8).
Just fyi, it's always better to create a new folder if you are running minecraft modded to avoid things like this! =P I usually make a folder like .other_minecraft/Lucky Blocks 1.8.9 and point the vanilla launcher to that folder.
And sure, I'd accept translations.
I don't remembering using loot++ for 1.7.10 but i did had a custom made config for lucky block mod config from all other lucky blocks but 1.8 changed that system using addons and able to use multiple blocks now. anyway deleted the config for loot ++ and deleted loot++ from the add on section not that long ago. many things still spawn, i did get boss mob spawns also and the Grim boss also, but i believe i get just boss music also.
Using 1.8 not 1.8.9 not clarify and 1.8 version of spiral lucky block and even you astral lucky block 1.0 version. Whatever 1.8 works with and not sure the higher version cause problems or compatible.
so things work okay but errors are still there and there are about 500 or 600 of them but still get lots of okay normal lucky block spawn.
though i know there is a problem still and not sure not what is it. i still check it out time to time when i can.
Hey IRC Hack I wanted to tell you that in one of the random drops of this mod makes my game crash and its really annoying. I lost all my good stuff and weapons because of this. Plz fix this so I cant have this problem again.
I'M SORRY I KEEP FORGETTING (╯°□°）╯︵ ┻━┻
Please update astral and spiral to 1.9
i got a crash report
:
---- Minecraft Crash Report ----
// I just don't know what went wrong
Time: 5/3/16 1:45 PM
Description: FML has discovered extracted jar files in the mods directory.
This breaks mod loading functionality completely.
Remove the directories and replace with the jar files originally provided.
java.lang.RuntimeException: Extracted mod jars found, loading will NOT continue
at net.minecraftforge.fml.relauncher.CoreModManager.discoverCoreMods(CoreModManager.java:298)
at net.minecraftforge.fml.relauncher.CoreModManager.handleLaunch(CoreModManager.java:246)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupHome(FMLLaunchHandler.java:95)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupClient(FMLLaunchHandler.java:72)
at net.minecraftforge.fml.relauncher.FMLLaunchHandler.configureForClientLaunch(FMLLaunchHandler.java:34)
at net.minecraftforge.fml.common.launcher.FMLTweaker.injectIntoClassLoader(FMLTweaker.java:119)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:115)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- System Details --
Details:
Minecraft Version: 1.8.9
Operating System: Mac OS X (x86_64) version 10.10.5
Java Version: 1.8.0_74, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 55907880 bytes (53 MB) / 127139840 bytes (121 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 5 total; -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
plz fix this cause this mod looks epic!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt looks like you put the wrong thing in your mods folder.
where do u download it from
Is the v1.10 version of this lucky block compatible with 1.8? If not can you release a 1.8 version?
Sup.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt is indeed compatible with 1.8.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHmm... Yeah, that's not good. I'm curious about what's in the block additions folder. Open up the zip download, and look in the file config/block_additions/stairs.txt. What do you see?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYep, that all looks like it should...
The first part is the item id, the second the item name like you said, and the third and fourth are the block and metadata to inherit properties from (in this case, the gingerbread you found in the other file).
I'm about to release a new version of Loot++ with bugfixes (version 1.7.1). Maybe try it with that when it comes out.
I feel like something is wrong where I hear some boss music playing such as the Grim's and another boss and nothing spawns but only changes difficulty to hard and music plays. Feels like an error towards the Loot ++ mod and not sure what is up on that side.
EDIT: Apparently i had a old version of loot ++ this whole time and never notice it till now. and strange enough had 1.9 spiral lucky block version which was for 1.8.9 i think, so change 1.9 for the 1.8 version and useing a higher version of loot ++ now, going to test them out now after double checking the other lucky block mods i had for their right version.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAha!
You must have had block additions in your Loot++ config file. Had you ever run spiral lucky blocks in 1.7.10 before? That used the Loot++ configs to load the blocks and items (as the addon system was added in 1.8).
Just fyi, it's always better to create a new folder if you are running minecraft modded to avoid things like this! =P I usually make a folder like .other_minecraft/Lucky Blocks 1.8.9 and point the vanilla launcher to that folder.
And sure, I'd accept translations.
I don't remembering using loot++ for 1.7.10 but i did had a custom made config for lucky block mod config from all other lucky blocks but 1.8 changed that system using addons and able to use multiple blocks now. anyway deleted the config for loot ++ and deleted loot++ from the add on section not that long ago. many things still spawn, i did get boss mob spawns also and the Grim boss also, but i believe i get just boss music also.
Using 1.8 not 1.8.9 not clarify and 1.8 version of spiral lucky block and even you astral lucky block 1.0 version. Whatever 1.8 works with and not sure the higher version cause problems or compatible.
so things work okay but errors are still there and there are about 500 or 600 of them but still get lots of okay normal lucky block spawn.
though i know there is a problem still and not sure not what is it. i still check it out time to time when i can.
Do I need to do something after updating loot++ to make the chest work?Cos the chest are still broken.
I had a problem with this and the Loot++ for 1.8.9
The crash reports are on my account. Please fix!
Can i add this to my mod-pack?
I AM A EXTREME NOOB
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSure, you can add this, but only if you can get modpack permission for the lucky block mod as well.
Is it seriously only for 1.8.9? =[
I can't find a 1.7.10 version ;-;
Hi how to Download This Awesome Lucky Block mod?
Hey IRC Hack I wanted to tell you that in one of the random drops of this mod makes my game crash and its really annoying. I lost all my good stuff and weapons because of this. Plz fix this so I cant have this problem again.
can you show a full file location of the Addons folder? i can't find it