Jump 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.

Malivil

Members
  • Joined

  • Last visited

Everything posted by Malivil

  1. Firstly it's "Forge", not "Forage" And secondly, the latest forge is for 1.4.3 Use this one instead: http://adf.ly/673885/http://files.minecraftforge.net/minecraftforge-universal-6.0.1.355.zip Oh, and don't double post. The edit button is there for a reason.
  2. Works fine for me. What version of IC2 beta? What version of forge? Logs?
  3. Unlikely. Post the code that is causing the error (or your entire @Mod file) and we can try to identify the issue.
  4. That exception occurs when IC2 looks for CraftGuide but doesn't find it. It doesn't break anything, it just looks ugly in the logs. That's not the issue.
  5. Install OptiFine after Forge and it should work fine.
  6. Delete the __MACOSX folder from inside your Minecraft.jar and try again. If it still doesn't work, post the new crash log here (and please, don't color it this time)
  7. You have old versions of CodeChickenCore and NotEnoughItems installed Remove them from your coremods folder
  8. AutoSwitch 2.4.2 is working perfectly for me with Forge 350
  9. Every time you start the game it creates a new ForgeModLoader-0.log Post it here so we can see what the new problem is.
  10. You have a block ID set over the 4096 limit
  11. Buildcraft 2.2.14 is for MC 1.2.5 You can get the 1.3.2 version from here: http://www.mod-buildcraft.com/2012/09/13/pre-release-for-minecraft-1-3-2/
  12. Update Forge to 297 or higher
  13. Update Forge and if you're using ComputerCraft 1.42, update that to 1.43 as well.
  14. Just remove it from the AutoSwitch.zip and they will both load fine. I made a post in the thread on the minecraft forums suggesting the author move his API into a separate package so this conflict doesn't happen.
  15. You're using cornCrop.blockID before you declare cornCrop Move your block instantiations above your item instantiations and then it should be fine.
  16. It IS compatible, as long as you install OptiFine AFTER Forge
  17. Ah, guess i'm just lucky that it works for me. Nevermind, then.
  18. To be more specific, the MCPatcher's "HD Textures" mod and Forge are not compatible. If you disable that mod in MCPatcher, everything works perfectly. Also, I use HD textures without using OptiFine at all.
  19. File should be named "Generic.java" not "tutorial.generic.Generic.java"
  20. "minecraftforge-universal-4.0.0.200" Update.
  21. As long as you don't use the "HD Textures" mod that comes with MCPatcher, it works fine. I use it.
  22. Can we see the code you're using to create the recipe? The damage value of an item being created in a recipe is the 3rd (and optional) parameter in the ItemStack constructor, so you can set the damage value using that.
  23. Ok, I'll let him know that. Thanks for replying so quickly. As a point of interest, why would this have started happening in the latest Forge builds? Or does it have nothing to do with that, and is a timing issue or something that would only happen periodically?
  24. When upgrading to Forge build #239, this IllegalArgumentException started happening when loading MineCraft with a mod that previously worked perfectly. The mod is SuperSlopes available here: thread download Error: Full log is attached for your reference. ForgeModLoader-client-1.log

Important Information

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

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.