Is there a way I could get my hands on FN 1.2.2, the version that works with 1.4.7? I'm trying to revive an old server and the links here do not seem to work. ;(
Sorry, those files were lost a year or two ago. :/
Nightshade, any plans on moving to 1.10 or should I not expect FN to move past 1.7 anytime soon? I realize its a huge update, but there's a lack of biome adding mods in 1.10 right now, we're basically reduced to BOP entirely.
Not any time soon. It's pretty much status quo right now until I get requests to update. Also, remember how long it took me to update to 1.7? It was something like 3 or 4 months I think, so if I get started on it, it still might not be soon. That all depends on how complicated the update to 1.10 is.
Anyway, if you have a number of people who want the update, get them to post on this thread so I can know there is a demand for it, then I will feel justified spending the time to update.
It's there, but only in the form of one ID. It's called "Biome ID Index." There are seven biomes in all, so if the index is set to 14, for example, the IDs would be 14,15,16,17,18,19,20 and 21.
Finally finished that update, however, nether trees and the nether mushroom still need to be planted on grass/dirt to grow. I want them to be able to be planted on both dirt/grass and netherrack. They are meant to change the soil they are planted on into netherrack as they are corrupting by nature.
On the bright side, it no longer crashes. However the nether shroom flesh now drops blaze logs... Haha.
Some other notes: The leaves of your overworld trees seem to not play nice with fast leaf decay and tree capacitor mods, some will break after felling a tree but not all. All trees consume durability and bonemeal in creative mode, and trees will delete blocks on growth. Which can lead to some incredible griefing opportunities on servers (Especially with angel oak). Nether shrooms can't be naturally obtained from their larger brethern or placed on netherrack, only dirt, which it turns dirt into netherrack after growing. Same for nether trees.
Also, player placed leaves decay.
Thanks for the notes. I'll get those fixed in the near future. As for the mushroom blocks, I fat-fingered the "1" key when I was writing the mushroom generation code, hence the metadata value of 13. This means that all newly generated mushrooms will produce the correct blocks, but previous once will just drop as blaze logs.
The download link is updated. Same version number, but should fix the mushroom bug. Again, you'll only notice the change with newly generated mushrooms.
Storm, if your game crashes upon loading the world, try to use an inventory editor to delete the item in question. That item is now "corrupted." I could make another update so in order for you to be able to load the world with the corrupted item, but I'm not a fan of adding layers of protective Swiss cheese in my code. :/
Also, Nightshade, I can only deduce this to be on your end. Logs that are rotated out of their normal orientation are dropping as "Oak Log" with their orientation intact in item form. These logs cannot be used for crafting, and have to be replaced in upright orientation to be usable.
at ForgottenNature.Items.ItemNetherLogs.func_77667_c(ItemNetherLogs.java:31)
at net.minecraft.item.Item.func_77657_g(Item.java:547)
at net.minecraft.item.Item.func_77653_i(Item.java:636)
at net.minecraft.item.ItemStack.func_82833_r(ItemStack.java:427)
at net.minecraftforge.client.GuiIngameForge.renderToolHightlight(GuiIngameForge.java:583)
at net.minecraftforge.client.GuiIngameForge.func_73830_a(GuiIngameForge.java:154)
at net.minecraft.client.renderer.EntityRenderer.func_78480_b(EntityRenderer.java:1038)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:1001)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:898)
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 ForgottenNature.Items.ItemNetherLogs.func_77667_c(ItemNetherLogs.java:31)
at net.minecraft.item.Item.func_77657_g(Item.java:547)
at net.minecraft.item.Item.func_77653_i(Item.java:636)
at net.minecraft.item.ItemStack.func_82833_r(ItemStack.java:427)
at net.minecraftforge.client.GuiIngameForge.renderToolHightlight(GuiIngameForge.java:583)
at net.minecraftforge.client.GuiIngameForge.func_73830_a(GuiIngameForge.java:154)
-- System Details --
Details:
Minecraft Version: 1.7.10
Operating System: Windows 8.1 (amd64) version 6.3
Java Version: 1.7.0_79, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 5938790248 bytes (5663 MB) / 6442450944 bytes (6144 MB) up to 6442450944 bytes (6144 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xms6144m -Xmx6144m -XX:MaxPermSize=512m -XX:+UseG1GC -XX:MaxGCPauseMillis=4
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
FML: MCP v9.05 FML v7.10.99.99 Minecraft Forge 10.13.4.1558 10 mods loaded, 10 mods active
States: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored
UCHIJAAAA mcp{9.05} [Minecraft Coder Pack] (minecraft.jar)
UCHIJAAAA FML{7.10.99.99} [Forge Mod Loader] (modpack.jar)
UCHIJAAAA Forge{10.13.4.1558} [Minecraft Forge] (modpack.jar)
UCHIJAAAA CodeChickenCore{1.0.7.47} [CodeChicken Core] (minecraft.jar)
UCHIJAAAA ForgottenNature{1.7.11} [Forgotten Nature] (ForgottenNature_1.7.11.jar)
UCHIJAAAA bspkrsCore{6.16} [bspkrsCore] ([1.7.10]bspkrsCore-universal-6.16.jar)
UCHIJAAAA creativecore{1.2.0} [CreativeCore] (CreativeCore v1.3.8 mc1.7.10.jar)
UCHIJAAAA ImmibisCore{59.1.4} [Immibis Core] (immibis-core-59.1.4.jar)
UCHIJAAAA koresample{1.7.10-1.3.2} [Kore Sample] (KoreSample-1.7.10-1.3.2.jar)
UCHIJAAAA redgear_core{2.2.2} [Red Gear Core] (RedGearCore-1.7.10-2.2.2.jar)
GL info: ' Vendor: 'NVIDIA Corporation' Version: '4.5.0 NVIDIA 355.82' Renderer: 'GeForce GTX 750 Ti/PCIe/SSE2'
Launched Version: 1.7.10-Forge10.13.4.1448-1.7.10
LWJGL: 2.9.1
OpenGL: GeForce GTX 750 Ti/PCIe/SSE2 GL version 4.5.0 NVIDIA 355.82, 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: [JessInsteadOfSteve.zip, Better Audio.zip] 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)
It's failing where the item grabs its name, but there isn't a 13th name, so I placed an appropriate fix. The update is on the OP (just updated it a moment ago). Go ahead and test the new version and get back to me if the problem persists. =D
0
If I remember right, that was a very easy update. You can post a dropbox link and I will see if it's simple enough for me to try
Typically, third digit updates aren't earth-shattering.
0
Sorry, those files were lost a year or two ago. :/
1
Not any time soon. It's pretty much status quo right now until I get requests to update. Also, remember how long it took me to update to 1.7? It was something like 3 or 4 months I think, so if I get started on it, it still might not be soon. That all depends on how complicated the update to 1.10 is.
Anyway, if you have a number of people who want the update, get them to post on this thread so I can know there is a demand for it, then I will feel justified spending the time to update.
Thanks
0
Geeze, my bad for getting back to you so late.
It's there, but only in the form of one ID. It's called "Biome ID Index." There are seven biomes in all, so if the index is set to 14, for example, the IDs would be 14,15,16,17,18,19,20 and 21.
Hope this helps.
0
The biome IDs aren't posted here because they are configurable. Look at the config file.
0
Something not working?
1
Finally finished that update, however, nether trees and the nether mushroom still need to be planted on grass/dirt to grow. I want them to be able to be planted on both dirt/grass and netherrack. They are meant to change the soil they are planted on into netherrack as they are corrupting by nature.
Anyway, check out the change log!
=D
0
I have been chipping away at the bugs Storm mentioned earlier; I have not forgotten
0
=O
By restart you mean you made a new world?
In the worlds I create they no longer drop blaze logs. They might be called spore stalk logs, but shouldn't be blaze logs.
0
Thanks for the notes. I'll get those fixed in the near future. As for the mushroom blocks, I fat-fingered the "1" key when I was writing the mushroom generation code, hence the metadata value of 13. This means that all newly generated mushrooms will produce the correct blocks, but previous once will just drop as blaze logs.
The download link is updated. Same version number, but should fix the mushroom bug. Again, you'll only notice the change with newly generated mushrooms.
0
Sorry :/
0
Storm, if your game crashes upon loading the world, try to use an inventory editor to delete the item in question. That item is now "corrupted." I could make another update so in order for you to be able to load the world with the corrupted item, but I'm not a fan of adding layers of protective Swiss cheese in my code. :/
0
This is fixed by-the-way =D
0
It's failing where the item grabs its name, but there isn't a 13th name, so I placed an appropriate fix. The update is on the OP (just updated it a moment ago). Go ahead and test the new version and get back to me if the problem persists. =D
0
I'm not able to recreate that result... but I'm attempting a fix. I found a possible cause.