-
Posts
4594 -
Joined
-
Last visited
-
Days Won
74
Everything posted by plowmanplow
-
Dropbox public links should be altered in this fashion: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1" (including the question mark). The contents of your modpack are in a subfolder. The three required folders (/bin/, /config/, /mods/) must be at the top level of the folder structure inside the modpack archive. Your modpack contains too many files/folders. It should only contain the folders /bin/, /config/, /mods/. Additionally, the /bin/ folder should only contain the file "modpack.jar". You are using a very old version of Forge. You should be using #1614. You should not be including the root level file named "options.txt". This will overwrite all client settings every time the modpack is updated.
-
Always provide the API URL or a link to the pack's platform page when requesting custom modpack assistance. I would recommend building your pack in a test environment such as the BareBonesPack. This will let you debug your pack as well as fine tune the config files before building your modpack archive. Are you sure you do not want to include Not Enough Items? Working with the mod item and block recipes without some in-game GUI help can be quite frustrating.
-
I would typically recommend people use the latest released versions of mods. Some authors (like TeamCoFH) only release versions considered "release" (even though they sometimes called them beta). Some authors have release versions and dev versions and it's up to you to be familiar with their process to know which one to use. If the last release version was 10 months ago but the most recent dev version is a week old and has many known critical fixes in it then the dev version probably makes more sense. Also, sometimes you have a main mod like AE2 that has addons made by other authors, such as ExtraCells for AE2. You have to make sure you are using a version of ExtraCells for the AE2 version you have (i.e. the best compatible version).
-
Follow JaariAtmc's advice. Your /bin/modpack.jar is actually named "modpack.jar.jar". Google "windows explorer always show file extension" to learn how to prevent this. Your ChickenBones mods are fatally out of date. Current Forge for 1.7.10 does not require the legacyfixer JAR. It should be removed.
-
@JaariAtmc Feel free to jump into the more comprehensive analysis. It's not rocket science. @EricTheNerdr DropBox public links should be altered in this manner: Change "www" to "dl". Change "dropbox" to "dropboxusercontent". Remove any trailing "?dl=0" or "?dl=1" (including the question mark). Ensure that you are incrementing the pack version number any time you alter the pack data or metadata. Your FC Pack Flan's weapon pack is out of date. You have the FC Pack weapon pack but not the required dependency Simple Parts Pack. You should not be extracting the weapon packs downloaded for Flan's mod. Simply place the archive file in the /Flan/ folder. You should not include the options files in the root folder of your modpack archive. This will overwrite any client settings every time the pack is updated. Follow JaariAtmc's instructions above about the folders to include and their contents. You should probably be using Forge #1614 not #1448. Many of your mods are out of date, some fatally so. You should be using the most recent compatible versions. Some of your mods are not from legitimate sources: Farlanders,
-
Attack of the B-Team Server Problem
plowmanplow replied to LeonT01's question in Attack of the B-Team
Can you confirm that you are using the launch.bat batch file to launch the server and that you haven't made changes to the batch file? This really sounds like you aren't launching the correct process. -
Chocolate Quest has a beta update that seems to function. Structures seem to be generating (I've run across a few, with banners). Dim Doors has a more recent update as well. Rifts seem to be generating and are able to be activated by doors. Keep in mind that the default chance that a rift will spawn in a chunk is 1 in 5000, so VERY rare. You can increase that likelihood if you wish.
-
Ahh. You updated to the 1.8 version. You need the latest 1.7.10 version (4.2.2). On a relate note, Hats is the mod that depends on iChunUtil.
-
It's crashing because your AsieLib and Computronics are out of date and not compatible with other mods. Updates are availalble. Your iChunUtil is out of date.
-
When I launch, it's vanilla version.
plowmanplow replied to SeigneurGriffe's question in Technic Launcher
Questions for assistance on custom modpacks belongs in Platform Pagoda. Hopefully a mod can move this (or lock it). Always provide the API URL or a link to the platform pack page when requesting custom modpack assistance. -
Totally fair that you are still getting up to speed on legitimate sources for mods. It can take a bit to figure out the sketchy sites. Thankfully there are only a few places that host 99%+ of the mods: MineCraftForum, CurseForge, GitHub, Personal Website by the author. When it doubt just look here for your mod and follow its link: NotEnoughMods I'll do a full analysis of the pack after dinner (probably 30 minutes or so). Looks like we are getting quite close to a final pack here. Thanks for sticking with me
-
Attack of the B-Team Server Problem
plowmanplow replied to LeonT01's question in Attack of the B-Team
The BTeam pack is provided by the Technic group and has an official server download provided on the pack's platform page. You should be launching the batch file provided, not one of the JAR files in the top folder level of the server. If you are still having issues after ensuring you are lauching using the batch file then please do the following: Remove any of the .log files in the root folder of your server. Launch the server (using the batch file). Provide a Pastebin link for the contents of your ForgeModLoader-server-0.log file. -
This is why it is better to build and test your pack in an environment such as the one provided by the BareBonesPack. As you build the pack the configs get generated and the mods which get automatically downloaded (i.e. deploaded) into the /mods/1.7.10/ folder are available for you to include in your finished modpack archive.
-
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. Your Chickenbones Mods are fatally out of date. You should be using the "latest" versions for 1.7.10. Your Galacticraft version is very old. Some of your mods are not from legitimate sources: Damage Indicators, Dragon Mounts, Level Up*, Rei's Minimap, Tinkers' Mechworks. Back Tools The "Level Up" mod in the previous bullet point doesn't seem to have a legitimate version I can find for 1.7.10. The URL in the mcmod.info file inside the mod links to a thread that has been locked for almost three years. This is a shining example of why you should always get your mods directly from the locations provided by their authors. You should probably update Modular Powersuits (and any other of your many outdated mods). You have not included a version of Railcraft in your pack so I cannot diagnose any issues with that. This is the second time I've directed you to only get your mods directly from the locations provided by the mod authors. I do not make these recommendations lightly.
-
All mods go in or below the /mods/ folder. CodeChickenCore goes in /mods/. CodeChickenLib goes in /mods/1.7.10/ (in the same location it saved when it is automatically downloaded).
-
Attack of the B-Team Server Problem
plowmanplow replied to LeonT01's question in Attack of the B-Team
If it weren't for seeing that " [qCraft] Loading qCraft v1.1 " I would assume you were starting the minecraft_server JAR file instead of the Forge JAR. -
Your /Flan/ folder is actually named "flan" (note the lower case "f"). It must be "Flan". I believe the weapons packs you have included also require SimplePartsPack. So, you removed NEI instead of switching to the correct version. That is a solution, but not one I was expecting nor probably what you want. You addded Damage Indicators mod, but did not obtain it from a legitimate source. Why did you do this? You have changed your pack contents but not incremented the version number. If you do not increment the version number your pack WILL NOT WORK.
-
Your modpack contains too many files. The /bin/ folder should only contain the file "modpack.jar". Your modpack.jar is indeed the most recent version of Forge: #1614. Still missing your config files. I responded in your other post. Some of your mods are not from legitimate sources: BuildCraft (also missing BuildcraftCompatibility), Fast Leaf Decay, IC2, Rei's Minimap, WE-CUI. Other than that I was able to start your pack successfully. Make these changes, and the changes from the other thread and see where that gets you. Don't forget to increment the pack version number.
-
I would recommend building and testing your pack in a development environment like the BareBonesPack. The configs will get generated automatically and you can alter them as necessary before including them in your modpack archive.
- 1 reply
-
- help
- plowmanplox
-
(and 1 more)
Tagged with:
-
I was able to successfully launch your pack. Try removing it from your launcher and re-adding it. Make sure you are incrementing the pack version number any time you alter your pack data or metadata. You have Biome ID conflicts. Check your logs. Your pack is insanely huge and uses a tremendous amount of RAM to start a SSP world. I wasn't able to successfully enter the new world until I increased my Launcher RAM allocation to 5G. If your system has less than 10G of RAM it is going to struggle with this pack.
-
Not Enough Items is made by an author named ChickenBones. You should be downloading that mod and the required dependencies. CodeChickenLib will be automatically loaded in your test environment when you launch the pack and should be included in your modpack archive.I even provided a link directly to the mod author's website. Simply select the correct version of MC and download the "latest" versions. The pack version number is configured in your platform pack settings.
-
The /bin/ folder should contain one file: "modpack.jar". You should probably upgrade Forge (the modpack.jar file) to #1614. Your Still Hungry mod is not from a legitimate source. Always download your mods from the locations provided by the mod authors. Make sure you increment the pack version number any time you alter the pack data or metadata.
-
Please provide the API URL or a link to your pack's platform page.
-
I'm going to assume that this is your pack: http://technicpack.net/modpack/jholder-craft.835633 Make sure you are incrementing the pack version number any time you alter the pack data or metadata. Your /bin/modpack.jar file is actually named "modpack". It must be named "modpack.jar". Your Not Enough Items mod is not from a legitimate source. Always download your mods directly from the locations provided by their authors. You have Not Enough Items mod but not the required dependencies CodeChickenCore and /mods/1.7.10/CodeChickenLib.
-
You have a folder named "industriousadventures.jar" in the top level of the folder structure which contains the Forge universal binary JAR. The Forge JAR must be named "modpack.jar" and placed inside of a folder named "bin". You should probably update Forge to #1614. Your Chickenbones Mods are fatally out of date. Your Railcraft version is very, very old. Some of your mods, such as Hats and Parachute Mod, are not from legitimate sources. Always download your mods from the locations provided by their authors.