Jump to content

DaemonUmbra

Members
  • Posts

    11222
  • Joined

  • Last visited

  • Days Won

    67

Everything posted by DaemonUmbra

  1. And your configs are exactly the same?
  2. User was banned for using a cracked launcher
  3. Does your client have the same mods and configs that the server has?
  4. Please read the logs section of my Signature and provide the appropriate log in the preferred manner.
  5. Remove the mod that was made for 1.7.10
  6. You have a 1.7.10 coremod when you're running 1.12.2
  7. You have a misbehaving coremod: Try removing these one by one, I would suggest starting with BetterFoliage.
  8. Please read the logs section of my signature and post the applicable log in the preferred manner.
  9. Can you please post your code as a GitHub repo so we don't have to ask for code file by file?
  10. So override shouldBurnInDay and you should be good, you shouldn't need to override onLivingUpdate unless you are doing other things. If you still have this issue it would be easier on us if you could post your code as a GitHub repo so we could poke around.
  11. Wait no I've lost myself, why are you overriding onLivingUpdate? I need to stop coming on the forums late at night...
  12. Do you know what this line does?
  13. Please post your code as a GitHub repo so we can take a look.
  14. You have a broken coremod, check for updates.
  15. Please don't necro old threads.
  16. Don't, this is one of the things Mojang explicitly wants you not to do.
  17. You should not rename it from what the Forge installer names it.
  18. What's the name of your vanilla jar?
  19. This usually means a corrupted (or missing) vanilla Jar, the vanilla server has log4j fat-jarred in.
  20. Any coremod that's doing things wrong could cause this. II would need your full log to determine anything further, check the Log section of my signature for more information on submitting the correct log.
  21. Where are you getting your mods?
×
×
  • Create New...

Important Information

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