Kalbintion

I misunderstood what your setup was then, but yes, either way should work just fine.

When you got the server files, you shouldve been downloading a zip (or archive) file. Unzip it, then run the launch.bat (or launch.sh on mac, *nix) and the server should be up and running. To connect to it yourself on the same computer, use ip 127.0.0.1 or localhost (Both mean the same thing) and you can connect to it. If you want others, then you need to do port forwarding and the like, or use a program like hamachi.

Go to the .technic folder, Go into the assets folder Delete "avatars" and "skins" folder presented there. Let me know if this resolves the issue.

Go to the .technic folder, Go into the assets folder Delete "avatars" and "skins" folder presented there. Let me know if this resolves the issue.

Pretty much - it was a wait for it solution at that time, new information has been presented to me. So, Go to the .technic folder, Go into the assets folder Delete "avatars" and "skins" folder presented there. Let me know if this resolves the issue.

Blacklisting on the chest shouldnt be necessary if the trash disposal system is closer to the input than the chest is. With the pipe to the chest marked for dense it should check everything else first before going there anyway.

Need to know a bit more on what you're stuck at.

If you don't have the plugin then there's nothing to disable. I'm still a bit confused on what entirely you're attempting to do. Use inventory tweaks in what way?

Last i knew you need to use the necronomicon (sp?) on the altar in order to summon the minion.

Who is he? What instructions are you attempting to follow and for what mod?

It crashed then when you made that other world, post the crash log for it.

Are you still experiencing an issue with it?

Alright, got some good news and some bad news. Good news is I found out why it isn't opening. Bad news is, I found out why it isn't opening. The level.dat is filled up with no information at all, nothing what-so-ever. No level seed, no player information, nothing. It may as well be non-existent, because thats what information it has. The only way to resolve this is to re-create the world with the exact same generator settings (world seed included) and replace the worlds level.dat with the new one. The other option is doing something similar, but with any settings and expect the world to have chunk edges. Edit: For the more technically inclined, the level.dat file contained 38.7kB of NULLs (u0000, ASCII 00)

Upload the worlds level.dat to a file host, i'll dl it and see what i see.

Anything else with that message? And you directly told NBTExplorer to open the level.dat and not the folder?

com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was STRING at line 1 column 1 ... at net.minecraft.server.management.PlayerProfileCache.func_152657_b(SourceFile:156) at net.minecraft.server.management.PlayerProfileCache.<init>(SourceFile:42) to me it indicates a corruption of the player info in the level.dat file. Removing the player tag from the level.dat using an nbt editor like NBTExplorer should fix it, but maybe not long-term. There isn't anything i see in the crash log that indicates what mod exactly that it was trying to get info for but rather was just an issue overall with the information.

I do suggest updating the 1.7.2 mods to 1.7.10 if this is meant to be a 1.7.10 pack, not all of the mods that work for 1.7.2 will work for 1.7.10 due to changes the games gone through and subsequently FML/Cauldron. The issue in the log itself though is in relation to snooper settings not being found then the following line is an error about a file not being found,. [14:14:31 WARN]: Can't read server snooper settings, won't send any data java.io.FileNotFoundException: server.properties (The system cannot find the file specified) It doesn't mention what the file name is at all, but it does say it saved a full crash log to C:UsersOwnerDesktopMinecraftServer.crash-reportscrash-2014-08-31_14.14.31-server.txt Which would be helpful in seeing the full stack trace and other info.

You only need the universal version. You will only download that jar then rename the file to modpack.jar - then you put it into the bin folder. That is all that needs to be done for that.

The -Xmx512m flag is actually the workaround provided by some sites about the JVM failing to create, only instead of setting it via the command line an app at a time, itd be the default value set to the _JAVA_OPTIONS environment variable (which is the same thing responsible for overwriting flags set by a batch file, etc in some cases) so yeah, im not 100% sure why this fails to create for some people. My only suggestion is reinstalling Java may fix that particular issue (uninstall all versions, reboot, reinstall in admin mode if possible) for a longer term than being forced in the 512M argument "trick"

And this version containing the issue for the modpack is live? I am noticing the id issues in the log. plow beat me to replying noticed those issues myself in the log.

To verify - this modpack is actually meant for 1.7.10? And you do not have any issues with running the cauldron.jar file by itself without via a batch (.bat) file? It's possible your download of the jar file got corrupted somehow. Also, fyi, -Xmx512m is a bit small for a server, maybe not for vanilla, but usually is for a server, but this isnt the issue atm.

This simply means you need to start over on the modpack jar file. Go to the FML site and download the FML Edit: universal version necessary for the modpack, and rename the jar file downloaded to modpack.jar and put it into the bin folder. Ensure you do not add anything to this jar file.

Oh you added mods? Wasn't aware. That'd make it a custom modpack issue then and the issue would belong in the Platform Pagoda section instead. If you feel its due to a mod added, my suggestion for quick testing if thats the case is to remove it and see if the issue persists, if it doesnt - theres the problem, and if it does - then theres something else going.

I did attempt to help, _Clannad. And even had help (question rather for assisting) associated in that post of mine that is now gone.

Java not being recognized is often due to the PATH variable not being set properly. As for the JVM issue - theres a minor fix but it can be a hassle itself that overwrites RAM set by the launcher. For the last issue, it doesnt seem to be finding the jar properly. Ensure the name is correct (itd be easier to name it modpack.jar or something shorter without the numbers hyphens and periods)