Jump to content

LexManos

Forge Code God
  • Posts

    9279
  • Joined

  • Last visited

  • Days Won

    72

Everything posted by LexManos

  1. jar.manifestVersion is the version you found in the manifest. So if a mod specifies that as their version, then check the manifest.
  2. Version checking is also done off the main thread so it shouldn't effect startup times in any significant way.
  3. You can't change the vanilla loading screen with a resource pack {unless something has changed recently}, for the same reason that you can't change this one. They are done before mods are loaded.
  4. You don't. Its meant to keep with Mojang's branding colors. If you want a different color use the dark theme option in vanilla, it'll switch to black.
  5. The concept is a known exploit that has been around for several years. It is not something that is caused by anything in ours, or Minecraft's end. It is unfortunately a risk when using mods in Minecraft. They are arbitrary jars which can have any code in them. This is one of the reasons we push people to use the latest versions. This particular case was fixed in BdLib for 1.16+ and the author has no intention of back porting.
  6. Ya, but the debug log should still contain the loaded mods, the enhanced exception was added later I guess.
  7. You have the same mod installed more then once, no idea what one it is, we used to have them listed in the log, so try checking the debug log.
  8. Run the forge jar...
  9. coda.breezy.Breezy.resetWindDirection(Breezy.java:67) is casting the client world to the server world without properly checking, talk to the breezy mod author.
  10. Something blue_skies is doing is conflicting with other coremods you have installed, try removing it and/or optifine.
  11. there is literally no executable jar anymore. Java does not allow them to be used when using the module system. Use the run scripts, or copy the run scripts into the command line arguments of your server
  12. No, there is literally no executable jar anymore. Java does not allow them to be used when using the module system. Use the run scripts, or copy the run scripts into the command line arguments of your server
  13. Fixed in 47.1.34+ https://files.minecraftforge.net
  14. This is the Forge forums, not Fabric, you'll want to go to their forum/discord to get support with Fabric.
  15. Seems like an issue with fishofthieves, remove it
  16. There is no error in that log, what are you actually experencing?
  17. There is no jar anymore, and hasnt been for a couple years now. You need to use a server host that supports modern ways to launch the game.
  18. Post the logs that are in the same folder you ran the installer from. This is typically something on your computer blocking internet access
  19. That is not a problem, that is exactly what the installer is supposed to do. You have to use the run script to start the server now. There is no executable jar.
  20. It very much is included in the installer, so not sure what you're getting at. Make sure you are using the vanilla mojang's launcher. Also this isn't the same issue as the OP because OP hasn't posted his logs so we dont know what his issue actually is.
  21. When you start the server, in your bat file there is the word 'java' you need to replace that with the full path of the specific java version you want to use.
  22. This isn't a bad idea, we typically have these things go through the GitHub PR system. However couple questions. All spawners get is a tick method. Why not use our level tick event? The only information that spawners get is (this.spawnEnemies, this.spawnFriendlies), which are private fields, so we could add getters.
×
×
  • Create New...

Important Information

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