Sana36

Inconsistencies, make it hard to help: 1. When 'helping' on the forum following the rules as I know it, answering simple questions or reminding people to post logs in a certain way. The someone more senior comes along and helps anyway. Change it from a rule to a guideline or something and then let us all know, maybe by posting it in writing somewhere. 2. Testing forge. Being involved in reporting issues found during testing, 1.13.x was frustrating. The grass seed one was mentioned multiple times from very early and nothing happened. The beta was released with almost no mobs and one or maybe two people commented. You want more testers, ones that actually notice when no land based mobs spawn, help make the feed back process work. Decide where they need to be reported and come up with a label or format that makes the most of their value and allows others to add their tests of the same issue. 3. Generally knowing what is going on with development of Forge, I found out most of what I knew from comments in obscure PRs. The link to your document in the header on the forum is a great idea but also think of a less technical, more player oriented version that can be copy and pasted to answer any questions about 1.14.x.

It is fine to test the world but there are limits on how many times to say the same thing. PR 5485, 5675 & 5434

I love Forge too, which is why I started helping. As I understand it, the idea was not to make any changes which would have to be undone for 1.14.x and therefore, hopefully, make it quicker for forge 1.14.x to be released.

Update your forge version to the current version 1.13.2-25.0.209 yours is .149 Then provide logs, as described in the EAQ, to enable us to help you. Mods will only work with the matching version of Minecraft and Forge. In the EAQ there is more information about mods.

Please provide logs, in the way described in the EAQ, to enable us to help.

Please attach logs as described in the EAQ includes how to load them up. Use Github Gists or Pastebin to attach your logs to your post. Do not attach your logs to your post or use file-uploading services like dropbox, mediafire, onedrive, or, any site that has a countdown before offering downloads.

Please provide logs as described in the support EAQs.

There is a lot of useful information in the EAQs. Glad it fixed your issue.

Is this issue closed?

Create your own thread and provide all logs as described in the EAQs.

Please provide a screen shot of your launcher and the installation log. Details of how to provide logs are in the EAQs at the top of the support forum.

Looking at the names of your mods, you may want to delete and reinstall from a trusted source. Have a look at the signature above as it contains further information.

You have loaded up a vanilla log of 1.8.9. Also be aware 1.8.9 is not supported by this forum due to its age. Please upgrade to a modern version of Forge to receive support.

Tall grass was still dropping at normal rate, last I checked. But yes it is known and won't be fixed in 1.13x Forge.

You have 8 core mods and 98 mods one of which has errored. Also, I need confirmation of this, it looks from the naming conventions of your mods that not all of them are from a trusted source. So general advice is to remove all mods that didn't come from CurseForge and replace them with mods that do.

The preference for logs is to use Github Gists or Pastebin, The information is provided in the EAQs Include the entire log(s) needed. Use Github Gists or Pastebin to attach your logs to your post. Do not attach your logs to your post or use file-uploading services like dropbox, mediafire, onedrive, or, any site that has a countdown before offering downloads.

Try updating to 1.13.2 - 25.0.202, the lastest version and seeing if the error still occurs. If it does post the log files as described in the EAQs in full.

Pulled together this from existing EAQs and multiple peoples signatures. It still needs input because, a lot of it has not been updated since 2013.

179 Mods and one that says "Do not report to Forge! (If you haven't disabled the FoamFix coremod, try disabling it in the config! Note that this bit of text will still appear.) (foamfix-0.10.5-1.12.2.jar)" Have you disabled this modification?

Forge 1.8.9 is no longer supported. Forge is the overlay that sits between Minecraft and mods, without it, or another 'brand' of the same thing, mods do not work.

The signature is the part at the bottom of all DaemonUmbra's messages. It starts with "This is my Forum Signature..." There is a lot of information in it that can be accessed by clicking on the "> reveal hidden contents" line in grey. This is where the information you need is. So click on the first one Then click on the one under logs Then click on the one under Twitch That is where the information you need is and also the file you need.

Did you put the mods where minecraft want the mods? Provide a path of where you put them. Go to, for a standard install on a Mac ~/Library/Application Support/minecraft/

A sample replacement EAQ

Another possible update - the "old" (1.6.89-j) official Minecraft launcher will no longer work with current versions of Forge.

So one question, two replies and two different answers. I know enough of the people involved to be pretty confident the answer is currently 1.11 & 1.12.2 & going forward is expected to be 1.12.2 & 1.14x. But the overarching rule of the forum is don't answer anything you don't know for sure. Is there a problem with updating the EAQs?