Jump to content

DaemonUmbra

Members
  • Posts

    11222
  • Joined

  • Last visited

  • Days Won

    67

Everything posted by DaemonUmbra

  1. You can identify an MCreator mod by unzipping it (a .jar is essentially a .zip with some extra specifics) if you see a folder called "mod" with a folder called "mcreator" inside it then either it's an MCreator mod or someone's being a doof.
  2. Click the 3 lines in the top right of the launcher Go to launch options Click the switch to enable advanced settings (switch should turn green) Click on the profile you're using Click the switch next to JVM Arguments to enable the text box Then scroll to the end of the text box and put in -Dfml.debugAccessTransformer=true (I have recently learned that some JVM args that I thought were good to go anywhere turned out position sensitive, so if this should go somewhere other than the end please correct me, Lex)
  3. Another improperly coded mod, with the same issue on a different class... client-only stuff doesn't exist on the server but a mod is trying to access client-only stuff when it's on the server. Sadly I can't tell you which because it's happening before the mod has even finished being constructed, meaning the dev likely has no concept of sides.
  4. Remove Arcane Lamps, the dev needs to learn how to mod properly.
  5. I have no idea what to tell you, to my knowledge what the log is reporting is impossible unless you are using a mod that is not registering itself with forge.
  6. @Noppes may want to weigh in but to me it looks like you may need to choose between Smart Moving and More Player Models.
  7. By in the system tray I mean there should be an Avast Icon, by right clicking on it there should be an option to temporarily "disable all shields".
  8. Even if Avast isn't showing an alert I would recommend disabling it for maybe 10 minutes from the system tray and retrying the installation.
  9. If it's neither of those things please post the installer log, the name for which will be <name of the installer>.log
  10. Check that your internet connection is good and make sure you're not running an overzealous antivirus program.
  11. No... I mean the .jar version of the installer.
  12. Try following these instructions:
  13. The location of debug.log is your .mincraft\logs folder, as long as you are using the default launcher from Mojang the .minecraft in my signature links to the Minecraft Wiki page which tells you where to find it depending on your operating system.
  14. Do you know any other programming languages?
  15. I don't know if there is an official Forge stance on this but I would recommend Sponge over Spiggot. Also note that if you use 1.7.10 you will NOT receive any support on these forums, 1.7.10 is an ancient version.
  16. Please double check all your mods and make sure they match the client you're running version-wise.
  17. Could you post your fml-client-latest.log please?
  18. Can I get a new log then?
  19. You are trying to use a 1.11.2 coremod (Quark) with a 1.12 client.
  20. Thread moved to Modder Support
  21. Why are you giving an argument to getRegistryName() ?
  22. If this is the same issue you had before please stop making new threads. You still have yet to post your debug.log You do not need to copy/paste from my Signature, it is a list of instructions not a template. What launcher are you using?
  23. Please post your mod as a GitHub Repo, making sure the git root is next to your build.gradle and the .gitignore provided by Forge's MDK.
  24. Saw this issue in another thread, rename the CCL config to something else so CCL generates a new one, then use the new one as a template to check for issues. I believe the formatting gaffe is that dump_asm and textify, which are boolean (true/false, yes/no) values should have B: in front of them, like B:"message_player_on_catch"=false does
×
×
  • Create New...

Important Information

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