Jump to content

LexManos

Forge Code God
  • Posts

    9273
  • Joined

  • Last visited

  • Days Won

    68

Everything posted by LexManos

  1. That error is literally impossible to get in 1.15, as that string does not exist in the installer 1.15 uses. So... 1) Why you lying? 2) Where did you get the installer from?
  2. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  3. This is a English only forum, and if you want tech support do it under the support forum not general.
  4. Tell your friends to use the vanilla launcher. That is the only support you'll get here. We do not condone entering credentials into 3rd party systems.
  5. Manually place the file there, if you can figure out what is preventing the download in your browser. The otehr thing I would try is make sure you either run the installer as admin, or fix whatever permissions are messed up in your minecraft directory that isn't allowing it to download the file.
  6. What language is your system set to?
  7. The forge version wouldn't change this, you just 'fixed' it by using a different Forge version which wasnt cached yet. So it rebuilt it with the correct java version.
  8. This thread is 8 god damn years old....and has absolutly nothing to do with your issue, AND you're using a unsupported version...
  9. Post your installer logs.
  10. 1.7 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  11. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  12. It's because you have JDK 9+ installed and set as your JAVA_HOME. But like I said you can work around it by using JDK 9+ in your dev env and just targeting source/target compatibility to 8 in your build script.
  13. Why?
  14. "Complicated tutorial" "To install my modpack, Run this jar, unzip this zip" Not complicated. The thing is, you don't need to know the main class, because there is SO MUCH MORE then just the main class that needs to be done. And the fact that you HAVE found the main class {Because it's literally labeled 'mainClass'} and disregarded it shows you have no idea what you're doing...
  15. You should use the vanilla launcher. It is NEVER a good idea to use a 3rd party launcher, giving your user account to 3rd parties is a bad idea. If your launcher does not support the vanilla format, then there isn't much we can do, use the vanilla launcher.
  16. Use an older Java version, or better yet, use a newer Forge version.
  17. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  18. The problem is that you setup your workspace with java 9. And there is a issue with the java compiler that produces incorrect method references when targeting j8 with j9. Just use j9 in your dev env, or clean your cache and rebuild with j8.
  19. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  20. Doesn't seem to be a Forge problem, more a interaction with your drivers and java. Worth cleaning up your installed Java versions, and video drivers.
  21. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  22. 1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  23. Naw, this would just cause a spam of useless reports from people who don't search before posting. We already get enough of that.
  24. Of coarse simple single use code is going to be faster then unrelated complex code. The kicker is the integration with Minecraft itself, and taking into account the things you so nonchalantly ignored, user configs dynamic textures, or any of the plethora of other things mods do that screw up the cache. Also, what parts of the texture stitching event actually takes time? What parts could be accelerated? The actual slot allocation shouldn't be that time consuming. But it'd be worth quantifying. So, as I said before, write something up and add benchmarks. And i'm talking real world implementations not unrelated theoretical code.
  25. Don't bump 3 year old threads. Also, you have the 'same' problem when there is no problem... so... Have fun!
×
×
  • Create New...

Important Information

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