Jump to content

LexManos

Forge Code God
  • Posts

    9273
  • Joined

  • Last visited

  • Days Won

    68

Everything posted by LexManos

  1. It already exists, and has been documented several times. It however is not a system we advertise or encourage people to use because flat out, the downloads page is how we pay the bills. And people who bypass that bypass how we make money. It's a shitty thing, but it's as simple as that.
  2. Interesting this is actually a vanilla world loading bug that we generically fix in Forge. {Illegal blockstates being saved to the chunk data} It *should* pulse the world and remove it's 'powered' flag. But seems vanilla is broken and doesn't do that.
  3. Update to a modern forge/minecraft version, not 1.8
  4. There isn't much we can do, with that load of mods it could be anything.He'll have to start tracking down which mod is causing issues. Create a world that has issues, and start deleting mods till it goes way. As for AMD, there shouldn't be any issues from Forge on AMDs, as I usually run on AMD.
  5. I typically don't browse this forum for real bugs as this forum is nothing but people installing mods for incorrect minecraft versions. So reporting things on github is the way to do. As for this, it's been fixed: https://github.com/MinecraftForge/MinecraftForge/commit/c0eea379a4cdb8ecc6af7342ba62e0dadc17b3ee
  6. It is expressly disallowed because Mojang expressly disallowed modifying of that texture from texture packs.
  7. No, int he launcher, you can edit the profile you are trying to laucnh, and select a Minecraft version. Is Forge in that list? If not post your installer logs, as well as a screenshot of your .minecraft folder.
  8. You wouldn't have the same problem with a newer version as this was fixed in the latest 1.6.4 and the early 1.7.10s so just update. Reading the eaqs also helps as this exact error is described in it.
  9. I said of your game directly not of your profile settings. I *think* I know what is actually happeneing, sometime in the past you did a dumb thing and extracted the contexts of the forge jar to your game directory. So it was loading the access transformers from that file and not from the jar. This is evidenced by the fact that you had completely different AT settings, and deleting the minecraft directory fixed it. When I get some time i'll add some more debug output to ATs to detect and notify of this case.
  10. Show me a screenshot of your game directory..
  11. No idea, Optifine is one of the evil mods we reluctantly support. He edits a lot of Minecraft internals and hes closed source we have no idea what he is doing. It's on him to be compatible with us.
  12. Optifine is trying to do some stuff that your graphics card does not support, This isn't on us.
  13. It is explicitly designed that we do NOT give out 'full code examples' because if you're a modder you shouldn't need copy paste code. And we have a history of the community spouting copy pasta all over the place, we will not contribute to this. As for the javadocs, due to how Minecraft is obfuscated and the mappings are crowdsourced, the javadocs are useless as you would have different functions and docs then someone else based on what snapshot you're using. Your IDE is the way to go for javadocs. As for everything else, as diesieben points out, the github is public and we rely on the community to develop tutorials/documents on things. So if you want them, start making them.
  14. That checksum is correct but something is causing you to not load all the transformers. You say it works with just Forge and not Optifine? Would seem Optifine is causing issues then Im not sure how it can but it is... Try updating to the latest Forge and posting your logs.
  15. Hes giving us the wrong log as they both have the same timestamp. Delete the mods folder Delete the Logs folder and give us the new log.
  16. Post a screenshot of what you THINK is your mods folder.
  17. THere is no 'other' place, it's loading from the default mods folder: C:/Users/tkawasaki/AppData/Roaming/.minecraft/mods/OptiFine_1.7.10_HD_U_B4.jar
  18. Then you didnt edit the right profile in the launcher. Make sure you're running the correct one. The big green play button has the profile name, and the version it will run.
  19. There are a few profiling mods none of which are officially endorsed by Forge. Yes it would be nice if there was one. But nobody has volunteered to make/help make one.
  20. You installed a client only mod on the server, don't do that.
  21. There is nothing we can do to tell you what is lagging your server. Something is either the number of mods you have on it or the machine you have in the world. Start removing mods, start unloading chunks.
  22. They are installed as versions, you have to go in and edit your selected profile to use the forge version.
  23. [18:45:15] [main/INFO] [FML/]: Forge Mod Loader version 13.20.0.2253 for Minecraft 1.11.2 loading [18:45:15] [main/DEBUG] [FML/]: Examining for coremod candidacy OptiFine_1.7.10_HD_U_B4.jar [18:45:15] [main/INFO] [FML/]: Loading tweaker optifine.OptiFineForgeTweaker from OptiFine_1.7.10_HD_U_B4.jar [18:45:15] [main/DEBUG] [FML/]: Examining for coremod candidacy Railcraft_1.10.2-10.0.1.jar [18:45:15] [main/DEBUG] [FML/]: Not found coremod data in Railcraft_1.10.2-10.0.1.jar [18:45:15] [main/DEBUG] [FML/]: Examining for coremod candidacy worldedit-forge-mc1.11-6.1.6-dist.jar [18:45:15] [main/DEBUG] [FML/]: Not found coremod data in worldedit-forge-mc1.11-6.1.6-dist.jar [18:45:15] [main/DEBUG] [FML/]: Examining for coremod candidacy worldedit-forge-mc1.7.10-6.0-beta-01.jar [18:45:15] [main/DEBUG] [FML/]: Not found coremod data in worldedit-forge-mc1.7.10-6.0-beta-01.jar Are you kidding me? Seriously dude... There are only so many times we can say Minecraft Mods DO NOT WORK ON DIFFERENT MINECRAFT VERSIONS!
  24. You still have mods for the wrong version installed. [18:45:15] [main/DEBUG] [FML/]: Examining for coremod candidacy OptiFine_1.7.10_HD_U_B4.jar Delete your mods folder and try again.
×
×
  • Create New...

Important Information

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