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. Humm seems that was one line outside my exception handler. Either way disable the splash screen -.-
  2. What launcher are you using, and where did you get 'Minecraft.msi'?
  3. No, that error was introduced intentionally because that mod is not registering entities correctly and will cause errors further down the line. The better option is to update/fix the Wildycraft mod. Logs, only way i'm gonna believe you, or potentially be able to help you, is with logs. Forge does not cause the JVM to persist. It's not a Forge issue.
  4. You have a lot of mods installed, and one of them is erroring: java.lang.IllegalArgumentException: Attempted to register a entity with invalid ID: 389 Name: Ghoul Class: class wildycraft.entity.EntityRSGhast Try fixing that up. Also try removing the mods you have until it stop happening, you have a mod somewhere causing it to derp.
  5. Interesting, shouldn't happen, there isn't any details as to what could be happening. As a hail mary try disabling the splash screen.
  6. Update to the latest Forge, the error code will be a bit more friendly and tell you what to do. You could also read the release notes in the releases forum and it'll tell you what to do.
  7. Looking into it, but first thing I notice about your pack is you have a lot of 1x1 textures, you should make those 16x16 or else it forces mipmapping to be disabled. Which makes things look odd. Aside from that your stonebrick.json refers to a missing model. { "model": "stonebrick" }, That model doesn't exist anywhere {No, not even in vanilla, as that 'stonebrick_normal'}. Hence the missing model. Trying it out in vanilla seems that vanilla hides these errors. Will look into that, but this is indeed an error in your resource pack {along with the 30-40 other errors that popup when reloading your pack} Heres some of your errors: [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone0' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone0.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone1' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone1.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone2' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone2.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone3' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone3.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone4' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone4.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone5' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone5.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone6' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone6.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone7' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone7.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone8' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone8.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone9' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone9.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/cobblestone10' for variant: 'minecraft:cobblestone_monster_egg#normal': java.io.FileNotFoundException: minecraft:models/block/cobblestone10.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/bdc_coarse_dirt01' for variant: 'minecraft:coarse_dirt#normal': java.io.FileNotFoundException: minecraft:models/block/bdc_coarse_dirt01.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/bdc_coarse_dirt02' for variant: 'minecraft:coarse_dirt#normal': java.io.FileNotFoundException: minecraft:models/block/bdc_coarse_dirt02.json [15:51:20] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/bdc_coarse_dirt03' for variant: 'minecraft:coarse_dirt#normal': java.io.FileNotFoundException: minecraft:models/block/bdc_coarse_dirt03.json [15:51:21] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/stonebrick' for variant: 'minecraft:stonebrick#normal': java.io.FileNotFoundException: minecraft:models/block/stonebrick.json [15:51:21] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/bdc_coarse_dirt01' for variant: 'minecraft:coarse_dirt#normal': java.lang.IllegalStateException: circular model dependencies involving model minecraft:block/bdc_coarse_dirt01 [15:51:21] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/bdc_coarse_dirt02' for variant: 'minecraft:coarse_dirt#normal': java.lang.IllegalStateException: circular model dependencies involving model minecraft:block/bdc_coarse_dirt02 [15:51:21] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/bdc_coarse_dirt03' for variant: 'minecraft:coarse_dirt#normal': java.lang.IllegalStateException: circular model dependencies involving model minecraft:block/bdc_coarse_dirt03 [15:51:21] [Client thread/WARN] [FML]: Unable to load block model: 'minecraft:block/stonebrick' for variant: 'minecraft:stone_brick_monster_egg#normal': java.lang.IllegalStateException: circular model dependencies involving model minecraft:block/stonebrick [15:51:21] [Client thread/WARN]: Texture minecraft:textures/items/empty_armor_slot_leggings.png with size 1x1 limits mip level from 4 to 0 Update: Yup looked into it more, vanilla does hide these missing models from the variants. However, this should not be expected behavior because it doesn't help resource pack makers like yourself detect when they have invalid references. So Forge will maintain this 'keep missing variants' behavior unless there is a good reason we should encourage broken resource packs...
  8. Post the actualy FML log -.- Looks like you have a mod installed that is keeping the JVM loaded.
  9. Post your log files, they are cleverly hidden in the 'logs' folder -.-
  10. Casing matters, and first and final warning Jedispencer DO NOT USE UNLOCALIZED NAME like that.
  11. I like how you starred out the part of the path that has a issue. Why have a ! in your username.. meh. You have to do as the error tells you and move it out of that folder.
  12. You have a firewall or something that is blocking the installers connection to the internet. As for the manually installed ones are not matching the md5s of the official ones. Scala has two md5s in our installer, one for the official maven releases and the other for our packed download.
  13. Try without optifine/shaders mod. If it still persists, post your specific drivers for your video card. It may be that your card doesn't support the things that the new loading screen needs and as such you just need to disable the new loading screen.
  14. Update Forge, you've added mods that use the global entity ID system in a bad way. Newer forges will give a more descriptive error. But you really should move away from mods that use this old system.
  15. Screenshots, exact links, be SPECIFIC. If you're having issues with adfocus, let me know. There are also direct links just use them.
  16. What source are you expecting? Minecraft code is not in the 'src' folder anymore, it's in the referenced libraries like a normal library.
  17. Yup, Mojang decided to change the protocol version in 1.8.7 for unknown reasons, you'll have to wait.
  18. Well there are many ways to do it, replace melons, replace pistons, replace hoppers, etc.. Probably your best bet would be to create a new block that acts like a hopper that allows melons to grow on them.
  19. You can't. Forge for 1.8.7 isn't out.
  20. Of course your client is outdated. It's 1.8 not 1.8.7. This is how modding works. This has nothing to do with jsons. That IS AN ERROR MESSAGE. And should of been stated in your first message.
  21. Why are you wanting to grow melons on hoppers?
  22. at noppes.npcs.ServerEventsHandler.invoke(ServerEventsHandler.java:160) Seems like a issue stemming from the NPCs mod.
  23. Simple as that, no. Should look into the mods you have installed, and yell at whoever is using the global ID system.
  24. Update Forge, we no longer specify the realms library in our json so there is no update process needed, mojang controls that part now. How about you actually follow the rules of the support section and POST LOGS, or actually STATE WHAT IS WRONG.

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.