Yes, this is the same issue that was reported further up on this page and on our IRC channel on Friday. Shecky is looking into what is causing this issue.
and it worked like a charm. Basically I just called the whole ID for the redwood quarter log instead of each single quarter. Probably this just was not up to date.
Due to this, I'd also recommend using this system for the firs (don't know if its importanz as they still use the old generation):
Of course, using the old generation, fir trees do not need to be chopped down containing multiple sorts of wood, but still... Just in case ^^
Last, I would ask you (the dev team) now, whether you would show the friendliness to push out a 3.15.8.1 version or so for 1.6.4 containing this fix.
I mean, I can use my own fixed version for now, but I would appreciate using an official one, if you understand me. ;D
Thanks for considering the fixes and the fixed release, and of course thanks for the great mod!
- Shad0w
(€dit: not doing this via pull request (or how that is called) because I have no idea how github stuff works at all)
and it worked like a charm. Basically I just called the whole ID for the redwood quarter log instead of each single quarter. Probably this just was not up to date.
Due to this, I'd also recommend using this system for the firs (don't know if its importanz as they still use the old generation):
Of course, using the old generation, fir trees do not need to be chopped down containing multiple sorts of wood, but still... Just in case ^^
Last, I would ask you (the dev team) now, whether you would show the friendliness to push out a 3.15.8.1 version or so for 1.6.4 containing this fix.
I mean, I can use my own fixed version for now, but I would appreciate using an official one, if you understand me. ;D
Thanks for considering the fixes and the fixed release, and of course thanks for the great mod!
- Shad0w
(€dit: not doing this via pull request (or how that is called) because I have no idea how github stuff works at all)
Yes, Shecky identified the problem a couple days ago when you reported it and knows what needs to be done to fix it. The problem will be fixed in the next release as well as the biome ID issue that some are having.
I have crash when im trying to use Extrabiomesxl 3.16 RC with hardcore ender expansion 1.6.3.
---- Minecraft Crash Report ----
// Ooh. Shiny.
Time: 28.09.14 23:03
Description: Initializing game
java.lang.RuntimeException: Hardcore Ender Expansion has found a defective recipe and cannot proceed! Another mod is likely registering a recipe BEFORE registering blocks and items, which is considered a serious error! Please, remove other mods until this message stops appearing to find which mod causes the issue, and then report it to that mod's author. You can also enable logDebuggingInfo in config to pinpoint the exact issue better.
at chylex.hee.mechanics.orb.OrbAcquirableItems.initialize(OrbAcquirableItems.java:123)
at chylex.hee.HardcoreEnderExpansion.onPostInit(HardcoreEnderExpansion.java:261)
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.GeneratedMethodAccessor5.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:694)
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)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at chylex.hee.mechanics.orb.OrbAcquirableItems.initialize(OrbAcquirableItems.java:123)
at chylex.hee.HardcoreEnderExpansion.onPostInit(HardcoreEnderExpansion.java:261)
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.GeneratedMethodAccessor5.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:694)
at cpw.mods.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:288)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:541)
-- Initialization --
Details:
Stacktrace:
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)
-- System Details --
Details:
Minecraft Version: 1.7.10
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 147377456 bytes (140 MB) / 334581760 bytes (319 MB) up to 3207856128 bytes (3059 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx3G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
FML: MCP v9.05 FML v7.10.84.1217 Minecraft Forge 10.13.1.1217 Optifine OptiFine_1.7.10_HD_U_A4 16 mods loaded, 16 mods active
mcp{9.05} [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
FML{7.10.84.1217} [Forge Mod Loader] (forge-1.7.10-10.13.1.1217.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
Forge{10.13.1.1217} [Minecraft Forge] (forge-1.7.10-10.13.1.1217.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
CodeChickenCore{1.0.3.26} [CodeChicken Core] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
NotEnoughItems{1.0.3.56} [Not Enough Items] (NotEnoughItems-1.7.10-1.0.3.56-universal.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
CustomSpawner{3.3.0} [DrZhark's CustomSpawner] (CustomMobSpawner 3.3.0.zip) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
customnpcs{1.7.10b} [CustomNpcs] (CustomNPCs_1.7.10b.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
MoCreatures{6.3.0} [DrZhark's Mo'Creatures Mod] (DrZharks MoCreatures Mod v6.3.0.zip) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
ExtrabiomesXL{3.16.RC1} [ExtrabiomesXL] (ExtrabiomesXL-universal-1.7.10-3.16.RC1.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
HardcoreEnderExpansion{1.6.3} [Hardcore Ender Expansion] (HardcoreEnderExpansion MC-1.7.10 v1.6.3.jar) Unloaded->Constructed->Pre-initialized->Initialized->Errored
Mantle{1.7.10-0.3.1.jenkins180} [Mantle] (Mantle-mc1.7.10-0.3.1.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
cfm{3.3.5} [§6MrCrayfish's Furniture Mod] (MrCrayfishFurnitureModv3.3.5(1.7.10).jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
Natura{2.2.0} [Natura] (natura-1.7.10-2.2.0-b1.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
ReiMinimap{1.7.10} [Rei's Minimap] (ReiMinimap-1.7.10-3.6.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
SlimevoidLib{2.0.4.6} [Slimevoid Library] (SlimevoidLibrary-2.0.4.6.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
WirelessRedstoneCore{1.8.0.0} [Wireless Redstone] (WirelessRedstoneCore-1.8.0.0.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized
Mantle Environment: DO NOT REPORT THIS CRASH! Unsupported mods in environment: optifine
Launched Version: 1.7.10-Forge10.13.1.1217
LWJGL: 2.9.1
OpenGL: GeForce GTX 660/PCIe/SSE2 GL version 4.4.0, NVIDIA Corporation
GL Caps: Using GL 1.3 multitexturing.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Anisotropic filtering is supported and maximum anisotropy is 16.
Shaders are available because OpenGL 2.1 is supported.
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Anisotropic Filtering: Off (1)
Yep a goof on my part there, it seems that I missed updating the redrock slab recipes. That said I also noticed that I missed the recipe for the scarecrow, and the cactus paste though they were just plain missing as they were still looking for the old item id's which no longer exist in 1.7.
I should be able to get another build out later tonight with a fix to this and what I hope should fix the issues with BoP and our biomes not keeping custom id's once again due to a goof on my part.
Noticed something, I'm having a biome conflict between Reika's chromaticraft rainbow forest and extrabiomes. See if I try changing either one of the id's for the biomes mountain taiga (47) or rainbow forest (47) for either mod and try to start the game the biome id's in either mods config file automatically change right back to what it was prior to me changing it. No matter how many times I try they just go back to what they were generated with it's almost as if the coding in either mod overwrites user changes to mod config files which makes it extremely difficult to sort out biome id conflicts.
Noticed something, I'm having a biome conflict between Reika's chromaticraft rainbow forest and extrabiomes. See if I try changing either one of the id's for the biomes mountain taiga (47) or rainbow forest (47) for either mod and try to start the game the biome id's in either mods config file automatically change right back to what it was prior to me changing it. No matter how many times I try they just go back to what they were generated with it's almost as if the coding in either mod overwrites user changes to mod config files which makes it extremely difficult to sort out biome id conflicts.
I don't know why Reika's chromaticraft is not keeping it's settings, but I do know that in RC1, I made a change to how we search for empty biome id's and I made a slight goof on my end and made it use the default ID instead of the one from the config if the one from the config was free. This will be fixed in RC2 but it does not look like I will be able to get it out tonight, so it probably won'y be out till I have time to take care of it tomorrow afternoon once I get home from work.
As for Reika's chromaticraft, if they keep their id when you change it's config without us installed then I'd say that it is just a case of my goof causing Reika's chromaticraft to take the first free biome id that it saw (it's old one) and then going with it since EbXL had reverted to it's own default. If they have issues remembering biome settings without us installed then they might have a similar problem to the one in EbXL of their own.
Release Candidate 2 is out now, and I really need to be off to bed, as I have a younger sibling who has yet to finish saving up for a car that needs picked up before I head out to work in the morning. Anyways just a couple bug fixes this time. As always you can get it off the OP, take a quick peek at the fairly boring and sparse blog post, or get it off Curse.
Change Log
Bug Fixes
Biomes once again remember custom id's as set in config.
Scarecrow and cactus paste are once more craftable.
Redrock slabs and it's variants register prior to creating their crafting recipes so as to no longer create invalid recipes.
Hardcore ender expansion is also for 1.7.10 HardcoreEnderExpansion{1.6.3} [Hardcore Ender Expansion] (HardcoreEnderExpansion MC-1.7.10 v1.6.3.jar) Unloaded->Constructed->Pre-initialized->Initialized->Errored
Yep a goof on my part there, it seems that I missed updating the redrock slab recipes. That said I also noticed that I missed the recipe for the scarecrow, and the cactus paste though they were just plain missing as they were still looking for the old item id's which no longer exist in 1.7.
I should be able to get another build out later tonight with a fix to this and what I hope should fix the issues with BoP and our biomes not keeping custom id's once again due to a goof on my part.
Even so, why would any mod intentionally crash the game? Very bad form in my opinion.
Even so, why would any mod intentionally crash the game? Very bad form in my opinion.
I would agree accept that as it stands if there are not enough free biomes for us to add all the ones that one has enabled in their config file, or if one of the biome id's that were open at the time that we read the config file is some how no longer open when we go and create the biome. In this case I think I can see the reasoning behind their crashing the game, if a player tries to craft a recipe with an invalid output then the game will crash and the world will not save, so they are causing the crash before a player loses progress in a world.
The question of if their solution the best answer is probably a no, but that being said, the error message leaves a lot to be desired. It it at least told the player what it knew about the recipe that was invalid, in this case the inputs, it would have been a lot easier to know what was causing the error, rather than a cryptic message that says nothing about what mod caused the issue. The only reason that I can think of for them not listing the recipe is that they thought that if a mod registered a recipe before a block/item was registered then it would have done so before any items/blocks were registered, but if that was the case then I can't see how anyone could publicly release a mod in that state as I'd think that you would try to craft one of your recipes before your release. In our case it was an obscure and rarely used recipe that to my knowledge had thought/remembered to check and I had thought that I fixed it when I hit up the same error with the other slabs.
Release Candidate 2 is out now, and I really need to be off to bed, as I have a younger sibling who has yet to finish saving up for a car that needs picked up before I head out to work in the morning. Anyways just a couple bug fixes this time. As always you can get it off the OP, take a quick peek at the fairly boring and sparse blog post, or get it off Curse.
Change Log
Bug Fixes
Biomes once again remember custom id's as set in config.
Scarecrow and cactus paste are once more craftable.
Redrock slabs and it's variants register prior to creating their crafting recipes so as to no longer create invalid recipes.
awesome now I can get back to work compiling, adding and making my mod list to play minecraft again
Tiny thing that still needs fixing: Red Cobblestone Stairs are called Red Cobblestone Stair
Thanks for the catch, since it is not game breaking and we want to catch any major error before we do another release.
That said Allaryin and I have been trying to do some lag busting from world generation here tonight, he discovered that MC is recalculating skylighting for every single block that is generated as part of our tree generation. We are going to see if we can narrow down as many of the calls as possible and possibly reduce some of the generation lag that our trees produce, but I won't be able to do the rest of my part of the testing till tomorrow. (For reference from the checking that I have seen that seems that a small vanilla oak tree recalculates the lighting from the sky about 256 times (8*8*4) and the more blocks in the tree the more times that it recalculates the lighting for the chunk. I don't have exact numbers at the moment but a tree like the Baldcypress could actually be generating 5120 lighting updates, per chunk that it spawns in and that could slow things down a bit when you generate more than one tree at a time.
Gamer, Minecraft Mod Developer, Creator of many mods that can be found in my CurseForge profile. (Helped port Grimoire of Gaia to 1.8.9 and helped getting a 1.12.2 version going)
I'm not sure how you concluded that ExtrabiomesXL was involved. Line 709 of the log shows that Artifact crashed because it was registering an entity (Mob) with an id that has already been registered. It would seems this is a bug in Artifact as each mod can get globally unique identifiers for its mobs..
I'm not sure how you concluded that ExtrabiomesXL was involved. Line 709 of the log shows that Artifact crashed because it was registering an entity (Mob) with an id that has already been registered. It would seems this is a bug in Artifact.
Edit: Added "of the log"
it only happened when I updated to 3.16.RC2. Before it was working fine...
Rollback Post to RevisionRollBack
Gamer, Minecraft Mod Developer, Creator of many mods that can be found in my CurseForge profile. (Helped port Grimoire of Gaia to 1.8.9 and helped getting a 1.12.2 version going)
https://github.com/ExtrabiomesXL/ExtrabiomesXL/issues/400
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYes, this is the same issue that was reported further up on this page and on our IRC channel on Friday. Shecky is looking into what is causing this issue.
That's what I did:
I replaced
tree.setString("logs", String.format("%d,0; %d,0; %d,0; %d,0;", q[0], q[1], q[2], q[3]));withtree.setString("logs", String.format("%d; %d,3;", BlockSettings.REDWOODQUARTERLOG.getID(), BlockSettings.NEWLOG.getID()));and it worked like a charm. Basically I just called the whole ID for the redwood quarter log instead of each single quarter. Probably this just was not up to date.
Due to this, I'd also recommend using this system for the firs (don't know if its importanz as they still use the old generation):
tree.setString("logs", String.format("%d,0; %d,1; %d,1; %d,1; %d,1;", BlockSettings.CUSTOMLOG.getID(), q[0], q[1], q[2], q[3]));replaced bytree.setString("logs", String.format("%d,0; %d;", BlockSettings.CUSTOMLOG.getID(), BlockSettings.FIRQUARTERLOG.getID()));Of course, using the old generation, fir trees do not need to be chopped down containing multiple sorts of wood, but still... Just in case ^^
Last, I would ask you (the dev team) now, whether you would show the friendliness to push out a 3.15.8.1 version or so for 1.6.4 containing this fix.
I mean, I can use my own fixed version for now, but I would appreciate using an official one, if you understand me. ;D
Thanks for considering the fixes and the fixed release, and of course thanks for the great mod!
- Shad0w
(€dit: not doing this via pull request (or how that is called) because I have no idea how github stuff works at all)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYes, Shecky identified the problem a couple days ago when you reported it and knows what needs to be done to fix it. The problem will be fixed in the next release as well as the biome ID issue that some are having.
So long as the mod is installed the biomes will spawn. You do not have to do anything special.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYep a goof on my part there, it seems that I missed updating the redrock slab recipes. That said I also noticed that I missed the recipe for the scarecrow, and the cactus paste though they were just plain missing as they were still looking for the old item id's which no longer exist in 1.7.
I should be able to get another build out later tonight with a fix to this and what I hope should fix the issues with BoP and our biomes not keeping custom id's once again due to a goof on my part.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI don't know why Reika's chromaticraft is not keeping it's settings, but I do know that in RC1, I made a change to how we search for empty biome id's and I made a slight goof on my end and made it use the default ID instead of the one from the config if the one from the config was free. This will be fixed in RC2 but it does not look like I will be able to get it out tonight, so it probably won'y be out till I have time to take care of it tomorrow afternoon once I get home from work.
As for Reika's chromaticraft, if they keep their id when you change it's config without us installed then I'd say that it is just a case of my goof causing Reika's chromaticraft to take the first free biome id that it saw (it's old one) and then going with it since EbXL had reverted to it's own default. If they have issues remembering biome settings without us installed then they might have a similar problem to the one in EbXL of their own.
Release Candidate 2 is out now, and I really need to be off to bed, as I have a younger sibling who has yet to finish saving up for a car that needs picked up before I head out to work in the morning. Anyways just a couple bug fixes this time. As always you can get it off the OP, take a quick peek at the fairly boring and sparse blog post, or get it off Curse.
Change Log
Biomes once again remember custom id's as set in config.
- Scarecrow and cactus paste are once more craftable.
- Redrock slabs and it's variants register prior to creating their crafting recipes so as to no longer create invalid recipes.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumEven so, why would any mod intentionally crash the game? Very bad form in my opinion.
I would agree accept that as it stands if there are not enough free biomes for us to add all the ones that one has enabled in their config file, or if one of the biome id's that were open at the time that we read the config file is some how no longer open when we go and create the biome. In this case I think I can see the reasoning behind their crashing the game, if a player tries to craft a recipe with an invalid output then the game will crash and the world will not save, so they are causing the crash before a player loses progress in a world.
The question of if their solution the best answer is probably a no, but that being said, the error message leaves a lot to be desired. It it at least told the player what it knew about the recipe that was invalid, in this case the inputs, it would have been a lot easier to know what was causing the error, rather than a cryptic message that says nothing about what mod caused the issue. The only reason that I can think of for them not listing the recipe is that they thought that if a mod registered a recipe before a block/item was registered then it would have done so before any items/blocks were registered, but if that was the case then I can't see how anyone could publicly release a mod in that state as I'd think that you would try to craft one of your recipes before your release. In our case it was an obscure and rarely used recipe that to my knowledge had thought/remembered to check and I had thought that I fixed it when I hit up the same error with the other slabs.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumawesome now I can get back to work compiling, adding and making my mod list to play minecraft again
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThanks for the catch, since it is not game breaking and we want to catch any major error before we do another release.
That said Allaryin and I have been trying to do some lag busting from world generation here tonight, he discovered that MC is recalculating skylighting for every single block that is generated as part of our tree generation. We are going to see if we can narrow down as many of the calls as possible and possibly reduce some of the generation lag that our trees produce, but I won't be able to do the rest of my part of the testing till tomorrow. (For reference from the checking that I have seen that seems that a small vanilla oak tree recalculates the lighting from the sky about 256 times (8*8*4) and the more blocks in the tree the more times that it recalculates the lighting for the chunk. I don't have exact numbers at the moment but a tree like the Baldcypress could actually be generating 5120 lighting updates, per chunk that it spawns in and that could slow things down a bit when you generate more than one tree at a time.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIts between Artifacts and Extrabiomesxl
Crashlog: http://pastebin.com/2dLruD9w
Log: http://pastebin.com/WKG2wMD2
It seems to crash with duplicate id. Somehow...
Gamer, Minecraft Mod Developer, Creator of many mods that can be found in my CurseForge profile. (Helped port Grimoire of Gaia to 1.8.9 and helped getting a 1.12.2 version going)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'm not sure how you concluded that ExtrabiomesXL was involved. Line 709 of the log shows that Artifact crashed because it was registering an entity (Mob) with an id that has already been registered. It would seems this is a bug in Artifact as each mod can get globally unique identifiers for its mobs..
Edit: Added "of the log"
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumit only happened when I updated to 3.16.RC2. Before it was working fine...
Gamer, Minecraft Mod Developer, Creator of many mods that can be found in my CurseForge profile. (Helped port Grimoire of Gaia to 1.8.9 and helped getting a 1.12.2 version going)