Skip to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

LexManos

Forge Code God
  • Joined

  • Last visited

Everything posted by LexManos

  1. There isn't you screwed up your install. DO NOT download MCp Use the one Forge downloads for you in forge/mcp
  2. We don't care if you use them, We just care if you edit your jar. None of those mods NEED to edit the jar. Least of which Reis.
  3. Ya, no, the other thread was a one time deal. This is a English forum. If you want help please use English.
  4. Don't use a web client, don't use names with > 16 characters. And you MUST be on a registered nick. Simple rules, filters out 75% of noobs.
  5. Yes, 1.6 broke 1.5 things. Namely the new resource pack stuff. SRG names are not for Major MC releases But anything within the same branch typically WILL work So 1.6.X 1.5.X 1.4.X etc... It's useful because things like 1.4, where it goes all the way up to 1.4.7 And 1.6 is looking like it'll do the same.
  6. The installer should of put that file into the libraries folder. See if its in there.
  7. at net.minecraft.client.main.Main.main(Main.java:77) at Start.main(Start.java:68) thats not the entry point see the launch configs shipped for eclipse with fml.
  8. It will always be up tot he Optifine dev, there are reasons why we added a disable flag. We do not add optifine incompatibility We added Mojang jar verification. Because we have NEVER actually supported ANY base editing mods. With forge this has not been necessary for a year. With Vanilla this has not been necessary since 1.6's new launcher was created. The ONLY reason editing the jar was needed was because we could not re-direct the entry point of Minecraft. With the new launcher we CAN which means the is no longer NEEDED to edit the jar. And as for optifine, his method is fairly easy to do. All he needs to do is use the tools that we made that are open source and freely available. All he has to do is: GenPatchSet HisObfed.jar VanillaMinecraft.jar And there is still a open call for if he wishes any help in cleaningup his workspace and making his life easier. But.. i've gotten nothing so meh. The new launcher allows you to specify your entry point into minecraft: https://github.com/MinecraftForge/FML/blob/master/jsons/1.6.2-rel.json#L125 And to make 1.5.2 work with the launcher Mojang is using donated code from FML: https://github.com/Mojang/LegacyLauncher There are reasons why we do the things we do, contrary to popular belief we actually speak with developers and mojang themselves. The old system of edit the jar was due to necessity, there are features in place that make it no longer necessary. So we will no longer support anyone who does so. Its one of the main issues that i've ran into with people in MC modding. The inability to evolve or adapt to changes. Everyone is under the "Well it worked 3 years ago why doesn't it work anymore!?!??!?!?" And that is a sad sad thing.
  9. Intentional, don't edit your jar, if you use a mod that tells you to, go tell them to stop.
  10. I'd have to see the full stack to determine which exactly is to long. But typically it's the username if the len is 16. And mc allows longer names as long as it's local .. cuz well.. they didnt add a check
  11. Caused by: java.lang.RuntimeException: Attempted to load class ats for invalid side SERVER at cpw.mods.fml.common.asm.transformers.SideTransformer.transform(SideTransformer.java:51) Obviously not. And as you said this is obviously an issue there end. They have a hard reference to Minecraft, which is client side only.
  12. 2013-07-10 21:37:40 [sEVERE] [unlitTorch] Failed to modify! Seems like you have a error there... Anyways ALWAYS post code -.- We arnt mind readers we cant guess hats wrong without seeing the code.
  13. 1) This is cpw's doing read the damn logs 2) NOTHING should touch the jar anymore in 1.6. Not even Forge or FML need to touch the jar, why the hell should anything else? 3) It IS possible to bypass this, but it's up to the Jar-Modders to do so and we WILL NOT support it here.
  14. That log doesnt show it downloading the scala-compiler library, which takes some time as it's quite large.
  15. Error with bspkrsCore{whatever that is} go speak with them not us.
  16. Nós não estamos indo para dar-lhe uma pasta pré-instalado. Isso é ilegal. Por favor, forneça imagens e registra-lo de tentar instalar Forge.
  17. Your username is to long, Minecraft only allows for 16 chr usernames.
  18. [lmgtfy]fix jar file association[/lmgtfy]
  19. Yes, what SanAndreas was trying to point out, is that you need to be within the same working directory so that the install scripts have access to the other scripts included with Forge.
  20. Log log s logs logs logs Seems to me like you're trying to install something else into minecraft as I'm quite sure I tested, blocks are not invisible.
  21. I have no idea what you just said. Post a log.
  22. Feel free to file a issue on the FML GitHub. We do not use ModLoader, and rely on users feedback for compatibility issues.
  23. Dont download mcp manually The real mcp is downloaded by Forge and in forge/mcp/
  24. Its a mojang launcher issue, it isn't caching the scala libraries so it's re-downloading them each time. If you're REALLY worried about it, you could edit the version json and break the server address. But its not really a issue. And Mojang will fix it soon

Important Information

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.