Jump to content

MDW01

Members
  • Posts

    441
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by MDW01

  1. So I'm assuming the missing world appear when you run the game in vanilla.

    • Could you try to open a save file in vanilla that was created with forge mods that you don't mind possibly losing (or just make a test one in forge) and tell me what happens? I just want to rule out the possibility of the saves actually being corrupt.
    • Are the regular files in the saves folder or are they empty?
    • Also, do you have any mods that are modifying the main screen, terrain generation, coremods installed that may cause issues?
  2. Sorry that this is happening I don't think that the couldn't get hash for the issue would cause this but I could be wrong. I think it is more likely a permissions issue.

    Could you post some more details:

    • Could you post a log where you actually enter the game and load up a world?
    • Could you check the permissions on your Minecraft folder?
    • Does this also happen in vanilla Minecraft?
    • When you say the saves are deleted could you check when you create a world if they appear in your saves folder and when if at all they disappear from the saves folder?
  3. One of my favorite and most complicated blocks the SkyBlock is throwing bytecode errors and nobody likes bytecode errors, which is why forge tells you to contact the mod authors first when core mods are present. You could try removing open mods but it looks like the actual reason for the crash probably is the LoadingPlugin (Quark-r1.4-122.jar)

  4. Yea this can be a bit tricky. Personally, the way I would do it is by adding that repository to yours using a git submodule. This shouldn't be an issue since they have an MIT license just make sure to give them credit. It will then get compiled directly into your code. It is pretty easy to keep the library up to date using git modules and they make it even easier to change the library if you need to.

  5. Your newly packaged library is not backward binary compatible the with the old version. For this reason, some of the library clients that are not recompiled may throw the exception. Pretty much you have made some incompatible binary changes to the library without recompiling the client code. This can mean making changes such as changing non-static non-private fields/methods to be static or vice versa.

    • Like 1
×
×
  • Create New...

Important Information

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