plowmanplow

You should be changing your dropbox links in this manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove "?dl=0" or "?dl=1". Make sure you are incrementing the pack version number any time you change the pack data or metadata. Your modpack archive is in 7z (7-zip) format. All archive files intended for use in the platform must be in ZIP format only. Simply change the file extension to ".zip" is not sufficient. You must set your client to create a ZIP format archive. Your modpack.jar file is totally messed up. 1) It's in 7zip format instead of ZIP format. 2) The contents of the file are in a subfolder. 3) It's an ancient version of Forge. Simply download the latest Forge universal binary JAR file. Don't extract it, don't change it, don't re-compress it. Just download it and rename it to "modpack.jar". Your modpack contains no config files. While this isn't typically fatal in a 1.7.10 modpack, it is still ill advised. Forge for 1.7.10 does not use a /coremods/ folder in any way. All mods belong in or below the /mods/ folder. Your /Mods/ folder must be renamed to /mods/ (note the lower case 'm'). Some of your mods are fatally out of date or simply very old (AM2, CodeChickenCore, BuildCraft, ProjectRed just to start). Please address these issues and come back if you still have difficulties.

We cannot help you without: Relevant server logs Relevant client logs Hosting details (local or commercial host details) Server details (Forge/Thermos/KCauldron/etc.) DNS/hostname information (can be a PM if you do not wish to share this information publicly).

Please note that the "?dl=1" was one of three distinct things that needed to be changed in the URL. It's all or nothing. Basically, if you use a "www.dropbox.com/blah/blah?dl=1" link it will be redirected internally by dropbox when referenced to "dl.dropboxusercontent.com/blah/blah". It is advantageous for you to make that change yourself so that it doesn't require that redirection step. Glad the file reference solved your immediate problem.

If you are the creator of these packs please start a thread with relevant information (API URLs, pack links, explicit problem description, etc.). If they are not your packs please follow up with the pack author.

You should be changing your dropbox links in this manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove "?dl=0" or "?dl=1". There is a file with a non-standard-ascii name in /mods/millenaire/languages/zh_tw/ (starts with an 'S'). Remove that file.

You should probably be using Forge 1614 since that's what most devs are targeting (if they are current). You have both the legitimate and illegitimate "Camping Mod" JAR files in your /mods/ folders. Your Flan's mod is out of date and not compatible with your weapons pack versions. You have both the 1.8.9 and 1.7.10 versions of MapWriter in your /mods/ folder. You have the Player API Core install ZIP instead of the actual mod in your /mods/ folder. Your Player API Core mod is fatally out of date. You have the Smart Moving install ZIP instead of the actual mod in your /mods/ folder. You have both the legitimate and illegitimate NotEnoughItems mods in your /mods/ folder. Your ChickenBones mods (NotEnoughItems, CodeChickenCore, etc.) are fatally out of date. You should be using the latest versions. This should also sound familiar. The /cofh/ folder in your pack belongs in /config/. (Familiar?) All of these issues were identified and resolved using: 1) Simply looking at the list of mods in the /mods/ folder. 2) Examining the /logs/fml-client-latest.log file.

On a 32bit windows system (32bit hardware since if you have 32bit windows on 64bit hardware I would just recommend you update to 64bit windows) the OS will really only have access to a bit over 3G. The maximum heap that a JVM can acquire in that environment is typically around 1.4-1.6G, but that would be on a clean system with NOTHING else running. You likely aren't in that situation. Realistically, you simply can't allocate more than 1G of heap (-Xmx1024m) on a 32bit Windows system.

Please stop posting screenshots of your folder listings. Always provide a download URL for the pack data you wish to have analyzed.

@Modernization: As previously stated, you are not following instructions. Until you make the recommended changes already submitted we will be unable to assist you.

No. You would need to manually create a modpack combining (deduplicated/deconflicted) mods from both packs and re-publish that.

You may have better luck ditching GalaxySpace and using More Planets.

I will put my two cents in the hat along with AetherPirate's excellent work so far: Assemble your pack in a development environment: I would recommend my BareBonesPack using these instructions The linked post instructs the pack builder to add mods singly or in logical groups. Yes, this means that it will have to be launched MANY times as you build your pack and tweak the config files. There's a reason the BBP has 9K+ launches.

We're not making your pack for you. We will help you debug your pack provided you make the recommended changes and provide requested information.

You'll need to take that up with the mod author.

Always provide an API URL or a link to the Platform modpack page when requesting custom modpack assistance. Your pack contains many mods from illegitimate/sketchy sources. Any mod named in the format of "ModName-Mod-1.7.10.jar" is likely to be from a content stealing/scraping website. Always get your mods directly from the pack authors.

Your pack settings still indicate a version of 1.0. It is imperative that the pack version number be incremented any time the pack data or metadata is altered in any way. You should be using the most recent release of Tinkers' Construct available on CurseForge, not v1.8.8

Sad to say, but no one with the power to do anything about this seems to have the interest or the time to pursue a resolution. Sorry, dude.

Info about blocks and recipes while inventory is open: Not Enough Items (or Just Enough Items if using 1.8.x) Info about blocks you are looking at: Waila (What Am I Looking At) Yes you can use plugins, provided you use something like Thermos you can use Bukkit plugins with your server. I would recommend GriefPreventionPlus for managing grief I am not aware of any plugins which properly log anything but vanilla (no modded) items. Building your client Turning your client into a server You can add/remove mods after you initially start the server. However, you will need to deal with world generation (mods that add blocks to the generated world) No suggestions on hosting other than Apex which is recommended by the Technic group.

Other than the two corrupted ProjectRed files that forge log has no issues to speak of and gives no reason why the server would be bouncing. I suspect this is a McMyAdmin issue.

Both of the Flan's weapon packs you have included require the Simple Parts Pack.

Unable to read the jar file ProjectRedLighting-1.6.4-4.3.5.30.jar - ignoring java.util.zip.ZipException: zip file is empty Unable to read the jar file ProjectRedMechanical-BETA-1.6.4-4.3.5.30.jar - ignoring java.util.zip.ZipException: zip file is empty Those files are empty or corrupted. I'm assuming you reached the pastebin size limit. Please provide that file through a DropBox (or other file hosting service) link so I can see the full log.

You must use a pastebin service because attachments don't work.

Always provide the API URL or a link to your Platform pack page when requesting custom modpack assistance. When using dropbox, change: "www" to "dl", "dropbox" to "dropboxusercontent", and remove "?dl=0" or "?dl=1" Your /bin/modpack.jar is named "modpack.jar.jar". Google "windows explorer always show file extensions" to learn how to prevent this issue. Flan's weapon packs go in /Flan/ not /mods/Flan/ You should be using the Latest versions of ChickenBones' mods (CCC, NEI)

Notice : Minecraft server has stopped running. Warning : Server was not yet ready, automatically restarting (Attempt: 1 of 5) Notice : Server jar hash is f357560b-48c9-0e75-3cac-577022a094eb Notice : Starting Minecraft Server... This is your McMyAdmin log. We will need your fml-server-latest.log and your most recent crash-report (if there is one). These will be in the <server>/logs/ and <server>/crash-reports/ respectively.

Then no, you are not ready to start making a server. You will need to provide client crash reports in a pastebin in order to narrow down what's going on.