plowmanplow

You are most likely launching the "minecraft_server.1.7.10.jar" instead of the Tekkit JAR file.

I would recommend using an alternate server version such as Thermos.

Everyone needs a hobby. It only takes a small bit of time each day. This just happens to be one of the things I am fairly good at. I am glad you have been helped by my efforts. Now, on the excellent advice of the Ghostbusters crew: Yes.

When you provide the API URL or pack page link you no longer need to provide the download URL. We can get that from your pack metadata. You don't have to remove damage indicators, you just need to get it from the correct location. Your pack data has changed (modpack contents) but you have not incremented the pack version number. Any time you alter the pack data or metadata you must also increment the pack version number. Your /bin/modpack.jar file is actually named "modpack.jar.jar". Google "windows explorer always show file extensions" to learn how to prevent this issue. When you are building/testing the pack using the BareBonesPack there will be a /config/ folder created which contains all the config files for your mods. After you are done editing those to tweak things to your preferences (you have so few mods you might not need to edit anything), you should include the /config/ folder from %appdata%/.technic/modpacks/barebonespack/ in your own modpack archive.

This GitHub repository has plenty of information and examples: https://github.com/ChatFawkes/CoFH-OreGen-Pack Make sure you have CoFH configs set to override vanilla oregen.

You are using a current (although it should be updated to #1614) version of Forge with some mods that are very old. This will cause issues like the one you are experiencing. You probably will need to: 1) Update to Forge #1614. 2) Update all your mods to their current stable/latest versions (depending on the mod). Edit: When I posted this I did not realize we weren't in the Platform Pagoda forum. All custom modpack support requests belong in the Platform Pagoda forum.

Additionally, even with 64bit Java, never allocate more than 4G of RAM or half your physical RAM, whichever is smaller. Unless you are using a HD texture pack you should never need to allocate more than 3G of RAM. Allocating more than you need will cause as many problems as not allocating enough.

Try removing the "teams.dat" file from the world folder.

From my previous response: Always provide the API URL or a link to the platform pack page. Dropbox public URLs should be altered in the following manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1". Your modpack.jar is a ZIP format archive containing the file "modpack.jar". <insert Inception joke> The modpack.jar file should be the Forge universal binary JAR file renamed to "modpack.jar". Nothing more, nothing less. Your Damage Indicators mod is not from a legitimate source. Always obtain your mods directly from the mod authors' preferred locations. Your collection of config files is incomplete. If you are using the BareBonesPack (BBP) to build and test your modpack you should be including the /config/ folder with all of its contents. Once you have the pack working fine through the BBP, simply copy the complete config folder from there to your staging area for your own pack.

To elaborate in a (nearly) necrotic thread: Windows 7 was licensed for the product purchased (or shipped in the case of OEM). What that means is that a product key for 32bit Windows 7 will work just fine for the same Windows version (home, pro, etc.) but for 64bit. Your friend could re-install Windows using his product key and the 64bit install DVD. He could also accept the Windows 10 upgrade, then reinstall with the Windows 10 64bit media.

Requests for assistance regarding custom modpacks belong in Platform Pagoda. If you stand on one foot and pray to the forum gods, maybe a moderator will move this thread. Always provide the API URL or a link to the platform pack page. Dropbox public URLs should be altered in the following manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1". Your modpack.jar is a ZIP format archive containing the file "modpack.jar". <insert Inception joke> The modpack.jar file should be the Forge universal binary JAR file renamed to "modpack.jar". Nothing more, nothing less. Your Damage Indicators mod is not from a legitimate source. Always obtain your mods directly from the mod authors' preferred locations. Your collection of config files is incomplete. If you are using the BareBonesPack to build and test your modpack you should be including the /config/ folder with all of its contents.

You can use BareBonesPack to build and test your client modpack. Creating a server from a working client modpack. You can use Thermos or KCauldron in place of Forge.

Always use a Pastebin Service for log/crash data. Don't paste it into your posts. Please refer to my edited post above.

Always use a Pastebin Service instead of attaching files or pasting their contents into your post. Attachments do not work here.

Please provide the client crash report from this event. Dropbox direct URLs should be altered in this manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1". What server process are you using? (KCauldron, Thermos, Forge, etc.) Your client pack needs to be complete/fixed before attempting to use it on a server: All deploaded resources (files typically loaded automatically into /mods/1.7.10/) must be included in the modpack archive. The pack must contain a full compliment of config files which are synchronized with what is on the server. Your Biomes O' Plenty mod is fatally out of date. You should probably be using Forge 1614.

@JaariAtmc feel free to use my platform API URL tester here: http://www.circlecraft.info/platform/ @luckylittleshark Dropbox direct links should be altered in this fashion: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove the trailing "?dl=0" or "?dl=1". Make sure you are incrementing the pack version number any time you alter the pack data or metadata. Since the pack starts fine for myself and JaariAtmc I suspect you have not done this. Increment the pack version, make sure you restart your Launcher, update the pack, and see if it works for you. Your modpack contains no config files. All modpacks should include a full compliment of config files. You should be creating your pack in a development environment. I provide a quite functional pack development environment with my BareBonesPack. Using this you can build and test your pack locally before pushing a new version up to the platform. Your TConstruct mod is out of date. I would like to congratulate you on getting all your mods from legitimate sources. This is uncommon with first time pack builders.

"Top Level" means the root folder of the ZIP archive. Yes, you should remove the /cofh/ folder and all of its contents.

Always provide the API URL or a link to your pack platform page when requesting custom modpack assistance. Dropbox URLs should be altered in this fashion: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove the trailing "?dl=0" or "?dl=1". Do not use some third party site just to "transform" a link. Always ensure you increment the pack version number any time you alter the pack data or metadata. Your modpack archive is in RAR format. All archive files intended for use in the platform must be in ZIP format only. Your /bin/modpack.jar file is named "modpack.jar.jar". Google "windows explorer always show file extensions" to learn how to avoid this issue. You should upgrade your Forge version to 1614. Your modpack archive has no config files in the /config/ folder. All modpacks should include a full compliment of config files. Some of your mods (Ancient Warfare, Damage Indicators, Iron Chests) are not from legitimate sources. Always download your mods from the locations specified/preferred by their authors. Your ChickenBones mods are out of date (CodeChickenCore, NEI). You should remove the " (1)" from the witchery file name.

<shakes magic 8-ball> ... because racecar On a more serious note, always provide the API URL or a link to the pack's platform page when requesting custom modpack assistance.

Is the mod that is failing to add significantly larger than your previous mods? What details can you provide about the mod? Can you provide the direct URL to the mod file in question?

I get the same HTTP/1.1 302 then 302, then 404 responses to that URL. It also takes me to a login screen when I paste it in a browser.

That link doesn't work because you have to log in to gain access. Here's the CURL output (the same method the platform uses to validate URLs). HTTP/1.1 302 Found Cache-Control: no-cache, no-store Pragma: no-cache Content-Length: 0 Content-Type: text/html; charset=utf-8 Expires: -1 Location: /pagenotfounderror Server: Microsoft-IIS/8.5 Set-Cookie: E=P:TGGnZ/pa04g=:66BGu7NUkOnaDPoOOSwNKGd2jBrDUalQBSaz6P05rrs=:F; domain=.live.com; path=/ Set-Cookie: xid=efded440-0308-43b6-a713-096a18f85835&&BY3302xxPFE008&130; domain=.live.com; path=/ Set-Cookie: xidseq=1; domain=.live.com; path=/ Set-Cookie: LD=; domain=.live.com; expires=Sat, 02-Apr-2016 11:46:31 GMT; path=/ X-MSNServer: BY3302xxPFE008 X-Content-Type-Options: nosniff Strict-Transport-Security: max-age=31536000 X-MSEdge-Ref: Ref A: E0BF888932F84A9DADC7D7A117A5A514 Ref B: 135948621AA218B5CF38112208D434A6 Ref C: Sat Apr 02 06:26:31 2016 PST Date: Sat, 02 Apr 2016 13:26:31 GMT HTTP/1.1 302 Found Cache-Control: no-cache, no-store Pragma: no-cache Content-Length: 0 Content-Type: text/html; charset=utf-8 Expires: -1 Location: /pagenotfounderror Server: Microsoft-IIS/8.5 Set-Cookie: E=P:kmTHZ/pa04g=:Pl1vqtDOcTQW3dVmeb8l93T9xDaE+VIizAK+QY0k8v8=:F; domain=.live.com; path=/ Set-Cookie: xid=ef6d0863-5757-43ae-8eaf-8039deb049a1&&BY3301xxPFE016&130; domain=.live.com; path=/ Set-Cookie: xidseq=1; domain=.live.com; path=/ Set-Cookie: LD=; domain=.live.com; expires=Sat, 02-Apr-2016 11:46:31 GMT; path=/ X-MSNServer: BY3301xxPFE016 X-Content-Type-Options: nosniff Strict-Transport-Security: max-age=31536000 X-MSEdge-Ref: Ref A: 7A5AFAE084344A98843B883368896DA4 Ref B: 3F076A39A6593090A642FA1C72E1B5E2 Ref C: Sat Apr 02 06:26:31 2016 PST Date: Sat, 02 Apr 2016 13:26:30 GMT HTTP/1.1 404 Not Found Cache-Control: no-cache, no-store Pragma: no-cache Content-Length: 0 Expires: -1 Server: Microsoft-IIS/8.5 Set-Cookie: E=P:t+HYZ/pa04g=:KCFElxHqlHVeYBsUUw1SgWk5RVtzMvy2n+UlADXaPLg=:F; domain=.live.com; path=/ X-MSNServer: DM2302xxPFE029 X-Content-Type-Options: nosniff Strict-Transport-Security: max-age=31536000 X-MSEdge-Ref: Ref A: 424AA5587A964B0A86E36295543D7074 Ref B: 6FF8B05D4C81F22CDAEB63D49B82647F Ref C: Sat Apr 02 06:26:31 2016 PST Date: Sat, 02 Apr 2016 13:26:31 GMT Unless the URL returns a "HTTP/1.1 202" the platform will not accept it. I have bee able to successfully use the host Weebly.com with a free account to host packs. (as a test only)

Yes. As soon as the date isn't April 1 the effects will go away automatically.

Dropbox links for a modpack download should be altered in this manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove the trailing "?dl=0" or "?dl=1". Your client pack has no config files. This is always ill advised and often causes significant to fatal issues when the pack is used to connect to a server. One of your mods has a (very lame) April Fools feature. The artifacts you are seeing are because it's currently April 1.

Your pack still has that top level /cofh/ folder. This is not needed and should be removed (as previously stated). There is an odd error showing up in the fml-client-latest.log. Something in "cpw.mods.fml.client.SplashProgress:start". Doesn't seem fatal so I wouldn't lose too much sleep over it. Your mod configurations have multiple duplicate types of ores (copper, silver, etc.). Not fatal, but not ideal. Other than that you can probably start making a server at this point.