Posted January 7, 20169 yr I have Minecraft Forge for MC 1.8.9 installed, but whenever I try to install a new mod for MC 1.8.9 in my game, Forge gives me an error and won't run. The error is similar to this: --------------------------------------- MrCrayfish's Furniture Mod (cfm) wants Minecraft (1.8, 1. The File 'ForgeModLoader-Client-0.log' contains more information --------------------------------------- First of all, I cannot fin any such log file on my computer, amd second, this is happening with the last 10 mods I have tried to install. I have tried mods from the following places: - minecraftexe.com - mod-minecraft.net - 9minecraft.net and - minecraftsix.com Ideas?
January 7, 20169 yr NONE of those sites are where you should be getting anything from. Those are all sites that do nothing but steal modders work, rehost it themselves and potentially wrap them in adware that installed other crap on your machine. Get things from their official sites. And the log is in your %AppData%/.minecraft/logs folder. I do Forge for free, however the servers to run it arn't free, so anything is appreciated. Consider supporting the team on Patreon
January 7, 20169 yr Author I went to the %AppData%/.minecraft/logs folder and there is no such file. That is beside the point though. You mentioned going to the official mod sites. Which sites are those?
January 7, 20169 yr The log file is called fml-client-latest.log for 1.7+. ForgeModLoader-Client-0.log was the pre-1.7 name. Most mods have a thread on Minecraft Forum with download links. Many mods host their downloads on Curse/CurseForge. 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.
January 8, 20169 yr Author Don't you think it is odd that the Minecraft Forge 1.8.9 gave me a log file name for a pre Minecraft 1.7 version? Is that a bug? You would think that Forge would know what version of Minecraft I am running.
January 8, 20169 yr That particular GUI's text just hasn't been updated since it was first added in 1.3.2. The file name in the message is hardcoded, it's not determined from the current logging configuration. It's probably worth reporting this as a bug, though. Edit: Reported here. 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.
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.