plowmanplow

The required folders for a modpack are in a subfolder inside your modpack archive. The "bin" and "mods" folder are inside a subfolder called "Das Reich der Drachen". They should instead be at the top level of the archive's folder structure.

http://files.minecraftforge.net/

@RavioliMonster: yes.

Please provide a link to your Technic pack page and/or API URL.

Your pack settings on your page are set to MC 1.7.5. Change it to 1.6.4

Your modpack archive is not properly assembled or you are missing the "binmodpack.jar" which is the Forge universal binary jar file renamed to modpack.jar.

@AsunaYuki: You are missing the libraries for your server. Use the latest version of Cauldron (formerly known as MCPC+) and run the installer.

Are you certain that isn't being triggered by some action you are taking? Teleporting? Some other command?

@Bob MC bob: No, it probably doesn't. The Tracker is for Technic related issues. Cauldron is developed by a totally different group of folks. @trimardland: The latest versions of Cauldron no longer automatically retrieve their library files. There is an installer provided with each version of Cauldron which will do that for you.

Without more information I would guess that you are seeing unloaded chunks. Entities (of which animals are members of) will act "oddly" when they move into unloaded chunks. How to fix them? Bigger question. However, this sounds like a basic Tekkit issue which should be posted in the Tracker for Tekkit at the top of this page.

@RavioliMonster: you pack is so close to being done, let's just get that working: Your "binmodpack.jar" is messed up. The modpack.jar file is JUST the Forge universal binary jar file renamed to modpack.jar. Don't extract it, don't add anything, don't change anything. Just rename the Forge jar. Forge/MC 1.7.2 does not use a coremods folder in any way. Put all mod file into the mods folder. However, one of the files in your coremods folder is the Forge universal binary jar. Rename that to modpack.jar and put it in the bin folder. Move the other file over to the mods folder. Your mods folder is named "Mods" (notice the upper case "M"). Rename it to be "mods" (note the lower case "m"). That's it. Your pack will be DONE!

With no crash-reports, no FML client logs, no Technic pack page or API URL links it is basically impossible to provide any assistance that wouldn't be a complete guess.

Your modpack archive needs a folder named "bin" and inside that folder a single file named "modpack.jar". The modpack.jar file is simply the Forge universal binary jar file renamed to modpack.jar.

And, as always, any time you are asking for help related to a modpack provide links to the Technic pack page and/or API URL.

One of two possible problems: You have a client only mod in your server mods folder. One of the mods you have in your pack is using the Forge API improperly and not correctly proxying the client API calls in the server code.

My pleasure. Always good to see a successful conclusion.

It is surprisingly difficult (not really) to provide assistance for a crash when we cannot see the crash report or ForgeModLoader server log.

You are only allocating 1G to the Launcher. If you cannot increase the memory allocation beyond 1G you need to remove all versions of Java from your system and install the latest Java 7 64bit JRE for your OS.

The output of the 64bit Java looks like this: java version "1.7.0_60" Java(TM) SE Runtime Environment (build 1.7.0_60-b19) Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode) Note the last line is different. Uninstall all the Java entries from your Programs in Control Panel and re-install the latest Java 7 64bit JRE for Windows (download it if you don't have it already). Take special care to get the 64bit version.

How odd. Another person is having the exact same problem you mentioned in Post #12 in this thread: '?do=embed' frameborder='0' data-embedContent>> Open a command prompt and type "java -version". Paste the full output of that command here.

Google is your friend. Ask him how to "open command prompt in windows".

Your bin folder has extra unneeded/unwanted files. Remove everything but modpack.jar from the bin folder. Remove the hats folder. The mod will create that when it starts up for the first time. You have item ID conflicts between: Factorization & ProjectRed, Railcraft & Telepads Don't allocate 7G of memory to the client. 3G should be more than sufficient. The game will often run more poorly if you allocate too much RAM to Java. You really need to update your version of ProjectRed as it is quite old and has known crashing problems. Other than that I don't see anything glaringly problematic. If you make all these changes and the problem persists I would recommend taking the crash report to the forums for Mystcraft.

What is the full output of a "java -version" from the command line?

Re-added Arcane Scrolls and KingCore mods. Uploaded the version of Cauldron I referenced in my previous post to the /jar/ folder. Changed settings in Multicraft interface to reference the new cauldron jar as the server process. I was then able to start the server and connect with your unaltered client (in there now, actually).

Use a file hosting site, or pastebin.com if it will fit, to provide your full FML server log and crash-report