Jump to content

quadraxis

Forge Modder
  • Posts

    201
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by quadraxis

  1. Sorry, I should have perhaps been more clear. I want the latest.log file from the client where this happens. Please also upload it to a text-hosting site like pastebin/gist/etc and link it here, rather than trying to put the whole log in your post.
  2. Post the latest.log file from when this happens.
  3. Have you actually tried clicking "Yes"? What happens?
  4. The report shows an outdated version of Optifine, try updating or removing it.
  5. You are using an outdated version of Optifine, try updating or removing it.
  6. I've seen many messed up mod file names from mod repost website, but that is one of a kind. Sorry to break it to you, but that's the file name you'll get off of CurseForge:
  7. Known issue, see https://github.com/MinecraftForge/MinecraftForge/issues/5675. Possibly waiting on a better system in https://github.com/MinecraftForge/MinecraftForge/pull/5497, or in 1.14, although the currently broken hooks should probably be removed to restore vanilla behaviour in the meantime.
  8. You can use a service like Gist (https://gist.github.com/) to upload log files, you do not need to create a full-blown Git repository.
  9. All enums that are extensible in 1.13+ will have a static create() method patched in by Forge.
  10. Particles are not backed by a Forge registry at present, so those features wil not work (https://github.com/MinecraftForge/MinecraftForge/issues/5514). The annotation is probably added by default due to the package and is not indicative of support here.
  11. https://github.com/MinecraftForge/Installer/issues/43
  12. Update Forge to 2836. Also, try to use a more descriptive title than "It looks like you are using an unsupported modified version of the game.".
  13. java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects You ran out of memory, allocate some more.
  14. The logs are not particularly helpful here, but it seems like you may be using Java 11. Currently, only Java 8-10 are supported for 1.13.
  15. Caused by: java.lang.IllegalArgumentException: Block: class com.brandon3055.draconicevolution.blocks.energynet.EnergyCrystal has property: type with invalidly named value: crystal_ıo It's an issue with Draconic Evolution, actually, so you'll need to try updating that.
  16. You cannot use an instance name that ends in '!'.
  17. Only Java 8 is supported for 1.12.
  18. This looks like you have the 1.13 version of ModNameTooltip on 1.12, but the jar file name claims to be the 1.12 version. When/where/how did you get the mod? Try redownloading it and see if this fixes the problem.
  19. They aren't: Memory: 3458883760 bytes (3298 MB) / 4116185088 bytes (3925 MB) up to 4116185088 bytes (3925 MB) JVM Flags: 2 total; -Xmx4096M -Xms4096M Initial heap is set to max deliberately here, so it's not due to allocation demands, and they have 3298/3924 MB free. Consider voting on vanilla ticket MC-123545 if you misunderstood the situation it due to the crash report being unclear.
  20. Update to the latest version of Forge (currently 25.0.90).
  21. Then this should probably be reported for investigation.
  22. What version of Forge are you using? (not "1.13.2", the full exact version) Some code for registry synching was only added recently (https://github.com/MinecraftForge/MinecraftForge/commit/d99a55a7d18e6e6035156970565ef7fcf77ea812).
×
×
  • Create New...

Important Information

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