plowmanplow

The latest 1.7.10 version of WarpBook mod is 2.0.37. You have the 1.8.9 version 2.0.43. You should downgrade. I replaced your Waila mod with the one from CurseForge and it worked perfectly.

Also: Always use a pastebin service for log/crash data. Do not paste it into the forum here, just provide a link to the pastebin. You should be using the most recent Java 8 64x. It is more helpful to post the most recent Forge logs, not the Launcher logs. Forge logs are located in the modpack folder under the /logs/ folder.

When looking for files on Curse/CurseForge it is vital that you pay close attention to the Forge/MC version the mod is made for. The files listing clearly indicates the MC version. The 6th file from the top in CurseForge's files listing for Waila is the most recent for 1.7.10.

What part of Millenaire isn't working? I see the creative tab for the mod and am able to spawn in items and blocks. If you log into the server I set up there are number of Millenaire mod blocks right by spawn. The starting kit (on the server) gives new players tools from the Millenaire mod.

This is the correct place to get Waila: http://minecraft.curseforge.com/projects/waila The site "http://mod-minecraft.net/waila-mod/" is a content stealing site. You have the LiteLoader "installer", not the actual mod JAR file in your /mods/1.7.10/ folder. You have the 1.8.9 version of JourneyMap. You need to replace that with the 1.7.10 version. Do you really want two minimaps? (JourneyMap and VoxelMap) Client Only Mods: JourneyMap LiteLoader VoxelMap NEI Addons WailaHarvestability WailaPlugins

Pack seems to start fine for me with the current mods (including Waila).

All of the Waila mods go in the /mods/ folder. One of the plugins requires a dependency mod (not sure which plugin requires this, but the curseforge page clearly states the requirement).

Are you executing the startserver.bat or the minecraft_server.1.7.10.jar? You should be starting the former. I started a server using only the download you provided (no changes). You can use the client to connect to this server to ensure your client is functional: vanilla.wegoboom.biz:25570

Always use a pastebin service when posting log or crash data. As for your pack, I'm not sure what to tell you. I added your pack to my launcher and started it up. I then ran the startserver.bat file from your server download and was able to connect using your client. No errors or problems.

You don't do anything with the minecraft_server.1.7.10.jar file, nor do you reference it in any way. Forge simply requires it to be in that folder with the correct name. Your "minecraft_server.1.7.10.jar" file is actually named "minecraft_server.1.7.10.jar.jar". Google "windows explorer always show file extensions" to learn you to prevent this issue.

Simply adding "?dl=1" to the end of the URL makes it eventually be a direct link. However, if you look at the server responses that results in a HTTP 302 (redirect) message which takes you to the dl.dropboxusercontent link which is the actual direct URL. This cuts down an the requests and makes it more streamlined (and thus less error-prone). Also, the actual direct link returns the correct file size to the CURL request (the method the Platform uses to query URLs). It's just the "right" way to do it.

You'll want the latest alpha from curseforge for TCon. Many fixes in there and quite stable. Chickenbones Mods: Make sure you select 1.7.10 at the top and get the "Latest" versions. Not 100% sure about Waila with Thaumic NEI. No issue having both.

Mekanism has three parts: Core Mekanism mod: Provdes most of the processing machines, cables, etc. Mekanism Generators: Provides power generation, including Fusion power! Mekanism Tools: Provides various tools to enhance play. Not strictly needed, but some handy stuff in there.

(Again) Dropbox direct links should be altered in this fashion: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1" . You aren't properly incrementing your pack version number. I recently downloaded your pack when it was verison 1.1 and the file size was 41,923,023. It is still version 1.1 but the file size is now 41,960,293. Increment your pack version number, restart your launcher and update the pack. If it still doesn't work, come back here.

Please don't put the "?" at the end of the dropbox URLs. It breaks the direct link. You have changed the name of the "minecraft_server.1.7.10.jar" to "server.jar". This breaks the library inclusions. Don't forget to edit the eula.txt file to set "eula=true".

Your Dropbox link is broken. Dropbox direct links should be altered in this fashion: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1". Make sure you are incrementing the pack version number any time you alter the pack data or metadata. You are including too many files in your modpack archive. The pack should only contain the folders: /bin/, /config/, /mods/. The /bin/ folder should only contain the file "modpack.jar". Forge Multipart belongs in /mods/1.7.10/ not /mods/. You should be include the contents of the /mods/1.7.10/ folder from your BBP test environment in your modpack archive. Did you intentionally exclude the two other Mekanism mods? You have the VoxelMap Litemod, but not the required parent mod LiteLoader (LiteLoader-1.7.10-04.jar belongs in /mods/1.7.10/). Your NEI mod is out of date. TConstruct is out of date. Most people like to have Waila (and possibly WailaPlugins with WailaHarvestability) as a client helper mod. PowerCrystalsCore does not belong in a 1.7.10 modpack.

When you don't get your mods from legitimate sources a myriad of "bad things" happen. 1) You typically have little idea which version you are actually getting. 2) You aren't supporting the authors. 3) You are supporting shady SOBs that steal other people's content for their own profit. 4) The mod may be compromised in some fashion (i.e "installers"). 5) It's just the wrong thing to do. It does seem that Metaworlds is not compatible with the latest Forge for 1.6.4 versions. Quite lame, but it is what it is. You will need to include the LegacyFixer JAR file in order to maintain compatibility with Java 8. MetaWorlds is the only mod in your pack not compatible with the latest Forge. You still need config files. No need to continue the PMs. Simply follow the points from the two posts above and you should be fine.

This post should help you get back on track. Feel free to come back here if you are still having troubles.

The original paste didn't work correctly. Try this one. You will be using the Forge installer JAR for the server.

I would recommend going through this post: Setting Up A Server You are missing the minecraft server JAR, all the libraries, and the rest of the support files that go with the server. You also have no batch/script file to launch the server. You should not be just launching one of the JAR files to start the server.

You will need to log in once with a valid account while connected to the internet in order to cache your credentials. Been that way for quite some time.

Do include config files for all packs in all situations and circumstances. Please do not spread misinformation regarding this requirement.

For the love of all that's holy, ALWAYS INCLUDE CONFIG FILES. Most of them get automatically generated but all of them will be defaults with no modifications to ensure compatibility. I'm putting this here so that if anyone sees your previous post that they don't get the idea that omitting config files is acceptable.

Yes, I assumed as much. I can think of no reason to implement such a feature that would not violate the Mojang TOS. Failsauce.

Dropbox direct links should be altered in this manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1". Make sure you are incrementing your pack version number any time you alter your pack data or metadata. You should probably update to Forge #1614. Your pack contains no config files. This is always bad and sometimes fatal. The pack should contain a full compliment of config files for all mods. I was able to add your pack and launch a SSP world. Try incrementing your pack version number and accept the update after restarting your launcher. Note: This "Real Trains Mod" seems sketchy as all hell. Why would you need an auth code? Seems like a clear violation of Mojang's TOS. I'm out from here on.