Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

cpw

Administrators
  • Posts

    193
  • Joined

  • Last visited

Everything posted by cpw

  1. Stop posting. Its being worked on. Just getting the problem to occur is fucking hard work. Your provider could fix it in a heartbeat by just installing some java fonts but whatever. So stfu and gtfo. It'll be fixed soon..
  2. Your trying to run 1.2.5 forge in a 1.3.1 bukkit server? DA fuk? Gtfo.
  3. You can't have installed forge correctly. Copy the entire content of the forge universal to the mine craft server jar. DO NOT DELETE METAINF.. make sure the directories are correctly copied over...
  4. Log, or console info, or it didn't happen..
  5. It is. Example mod that is not. Also make sure the latest forge is incompatible..
  6. Your mcmod.info file in not correct. Likely you have an empty section in it somewhere..
  7. Register your entity using registermodentity after your register global entity... FML always spawns mobs it knows about out of band...
  8. No that should be sufficient.make sure your running a recent forge..
  9. Update forge yes. That's forge 200- the first of about 40 subsequent releases.. update!!!
  10. Still not helpful. Optifine has input smoothing- is it possible that's the problem. Anyway you're the only person reporting input lag will forge. Also you do give the world some time to load? Finally, how much vanilla 1.3 have you played with NO mods? Its quite different from 1.2 single player...
  11. Update forge... that can never be the only error with recent forge builds...
  12. Don't put all your mods in the top panel of magic launcher. Just put forge, maybe mystcraft and maybe opt I fine in the top panel. Everything else should go down in the bottom panel: aka the mods directory. Ignore "no mod found" noise- that's magic launcher it doesn't know how to read new forge/FML universal mods...
  13. Fine. But magic launcher spews noise. Ignore it. Also don't put modloader and forge in the Same setup. That is guaranteed to fail.
  14. 1. Start from a clean jar. NO modloader. 2. Get newest forge. Not an ancient version.
  15. @mod.instance did receive an update. Unfortunately. If its a multi mod package it might fail where previously it worked. Send the mod author this way if he doesn't understand the change...
  16. Was a forgemodloader-client-0.log file generated? If not, you didn't install forge correctly..
  17. Try the latest forge. I had a small headless deep...
×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.