Jump to content

[SOLVED] Spruce Sapling not growing - Forge 11.15.0.1699 (for Minecraft 1.8.9)


Recommended Posts

Posted

In the 1.8.9 versions of Forge, it seems that single spruce saplings cannot be grown with bonemeal.

 

I tested it in vanilla Minecraft 1.8.9 and the spruce tree grows as expected, but in Forge, tested version 11.15.0.1699 with no other mods installed, I can use over 20 stacks of bonemeal and the tree does not grow, even though there is plenty of room around it and above it.

 

The 2x2 spruce trees will grow easily, but a single sapling won't. Oak, birch, acacia and both single and 2x2 jungle trees grow as expected, as well as 2x2 dark oak trees. A single dark oak sapling will, of course, not grow.

 

So, in other words, a single spruce sapling behaves just like a single dark oak sapling, i.e. not growing at all.

 

Of course, I have made sure that 5x5x8 area around it is clear, as it is normally the case with spruce saplings and I tested it also on a superflat world, where there is indubitably plenty of room.

Posted

I think this patch for

WorldGenTaiga2

(the small spruce tree generator) is causing the issue.

 

The original line checks that the neighbouring block is not air and is not leaves. The replacement line checks that the neighbouring block is air and is not leaves.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Posted

Well, spruce trees generate fine in the world, both 1x1 and 2x2. I'm not sure if that code is or is not part of the world generator, or if gets called only when a spruce tree grows. I'm not really in position to comment on that.

 

Just to clarify, the bug happens only when a player plants a single spruce sapling - it never grows into a 1x1 spruce tree regardless of how much time passes or how much bonemeal is used.

 

 

EDIT: The issue has been solved in one of the recent updates.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I fight fires for a living, it's in my blood as a volunteer firefighter. But nothing could have prepared me for the fire that almost reduced my family's future to ashes. I had secretly accumulated $150,000 worth of Bitcoin over the years, intending to lock up my children's education and provide my wife with some leeway from our constant shift-work life. That was until a phishing attack struck me while I was out fighting a wildfire. The call had been on a hot afternoon. We were dashing to contain wildfires tearing across parched scrub lands. At such frantic moments, my phone pulsed with a security alert message from what looked like my Bitcoin wallet operator. Drenched with sweat, fatigue, and hyper adrenaline, I had clicked on the link and input my log-ins without questioning anything. I was tricked by hackers during my most vulnerable time. Hours later, returning to the station, I emptied my wallet. The harsh reality hit me with more force than any fire could ever have. My carefully saved safety net had vanished. My heart beat faster than the sirens. I felt as though I had failed my family. I explained my terror of burgers at our favorite local diner that evening to my friend. He leaned in close and whispered a single word: Hackerzed Nemesis Recovery. He swore by their effectiveness, stating they worked miracles when his cousin had crypto stolen from him in a scam. I was skeptical old-school and desperate, so I called them. From the first call, their team treated me like family. They didn't only view figures; they viewed a husband and a father attempting to rectify a horrific error. They labored day and night, following stolen money through blockchain transactions like l detectives. Progress was made every day, translating intricate tech into fireman-speak. Ten days later, I got the call. “We recovered your Bitcoin.” I cried. Right there in the station, surrounded by smoke-stained gear, I let it all out. Relief. Gratitude. Hope they don't stop there. Knowing I worked in emergency services, Hackerzed Nemesis Recovery offered to run an online security workshop for my entire fire department. They turned my disaster into a lesson that safeguarded my team. These folks don’t just recover wallets; they rebuild lives. They rebuilt mine. I fight fires for a living, it's in my blood as a volunteer firefighter. But nothing could have prepared me for the fire that almost reduced my family's future to ashes. I had secretly accumulated $150,000 worth of Bitcoin over the years, intending to lock up my children's education and provide my wife with some leeway from our constant shift-work life. That was until a phishing attack struck me while I was out fighting a wildfire. The call had been on a hot afternoon. We were dashing to contain wildfires tearing across parched scrub lands. At such frantic moments, my phone pulsed with a security alert message from what looked like my Bitcoin wallet operator. Drenched with sweat, fatigue, and hyper adrenaline, I had clicked on the link and input my log-ins without questioning anything. I was tricked by hackers during my most vulnerable time. Hours later, returning to the station, I emptied my wallet. The harsh reality hit me with more force than any fire could ever have. My carefully saved safety net had vanished. My heart beat faster than the sirens. I felt as though I had failed my family. I explained my terror of burgers at our favorite local diner that evening to my friend. He leaned in close and whispered a single word: Hackerzed Nemesis Recovery. He swore by their effectiveness, stating they worked miracles when his cousin had crypto stolen from him in a scam. I was skeptical old-school and desperate, so I called them. From the first call, their team treated me like family. They didn't only view figures; they viewed a husband and a father attempting to rectify a horrific error. They labored day and night, following stolen money through blockchain transactions like l detectives. Progress was made every day, translating intricate tech into fireman-speak. Ten days later, I got the call. “We recovered your Bitcoin.” I cried. Right there in the station, surrounded by smoke-stained gear, I let it all out. Relief. Gratitude. Hope they don't stop there. Knowing I worked in emergency services, Hackerzed Nemesis Recovery offered to run an online security workshop for my entire fire department. They turned my disaster into a lesson that safeguarded my team. These folks don’t just recover wallets; they rebuild lives. They rebuilt mine. Contact : What    s    App: +      1, 6,3        ,9 3,        9,5   4,6,        2,8 Mail:         hackerzednemesis001               (@)            zohomail           (.)     com Website  :          https:        //hackerzednemesis      (.)                 com info               (@)         hackerzednemesis          (.)                    com
    • Can you upload full latest.log somewhere? Perhaps some interesting errors are reported just before the crash happens
    • It now starts but when i try making or joining a new world it crashes and the log says the same errors as before.  
    • Those other mods will need to be downgraded as well then - down to the version in which they supported Create 5. Or you will have to drop the plugins incompatible with Create 6. I know it stings, but you can't have it both ways ¯\_(ツ)_/¯
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.