Jump to content

plowmanplow

Discord Moderator
  • Posts

    4594
  • Joined

  • Last visited

  • Days Won

    74

Everything posted by plowmanplow

  1. You have the correct version of Forge as your modpack.jar.
  2. Mods that are still outdated (if I didn't miss any): (with current version in parens) bspkrscore (5.2) DamageIndicators (2.9.2.3) Applied Energistics (rv14-final3) Biomes-O'-Plenty (1.2.1.434) BuildCraft (1.6.4-4.2.2) Additional Buildcraft Objects (1.6.4-4.2.2-1.0.7.561) ComputerCraft (1.58 or 1.63) ExtraBiomesXL (3.15.7) ExtraCells (1.6.8f) ExtraUtils (1.0.3c) Factorization (0.8.34) ... Need I continue? I only got to the first "F" and there are already 11 major mods that are out of date. There are many, many more which need updated as well.
  3. Correct, 1.6.4 Forge/MC does not use a coremods folder.
  4. Your current pack download URL which points at a file called "retry11.zip" has almost none of the problems fixed. Yes, you did delete MDK, but the rest are still exactly the same: OpenMods: You have "OpenPeripheral-0.2.1-preview8.jar" which is both old and requires OpenModsLib. So much has changed since this version that this now consists of two mods OpenPeripheralCore and OpenPeripheralAddons. Old Versions: Just for example, you have versions of Galacticraft, Mekanism and IC2 that are so old they will be practically unplayable if they will even start at all. Configs: Your pack has 19 files in the config folder. My initial attempts to start the pack yielded 137 files in the config folder and that is without the pack even starting properly. This number may climb after it starts up all the way.
  5. While I agree that updating to Java 7 will be better in the long run, his problems are not related to that. I previously listed five bullet points which needed to be addressed before this pack has any chance of starting or working properly. Until that happens there is no point in continuing the back and forth. As for the configs, once the pack starts correctly it will have a full collection of config files in the config folder. The entire tree of files starting at "config" need to be included in the pack.
  6. You zip archive contains __MACOSX folders and .DS_Store files. These should probably be removed as they are unneeded.
  7. Kr0nZ: I do have a number of those options (and more) on my command line. I'll compare while refreshing my memory as to the functionality of each. Thanks!
  8. Start with this pack (make sure to check pack settings and choose Forge/MC version): http://www.technicpack.net/modpack/details/barebonespack.271497 Add mods one at a time or in logical groups. Get these mods from the author's preferred distribution channels (99%+ are from minecraftforum.com, curse.com or their own website), not from random sites around the internet or other packs. When everything is where you want it simply copy out to a new folder the config and mods folders, any extra folders you require such as Chocolate or Flan, and binmodpack.jar (just this file, not the rest of the bin folder contents). Zip up the contents of this new folder and you have yourself a modpack.
  9. You should really remove all the MacOS specific files and folders from your pack. You have the MekanismDevelopmentKit (MDK). Remove this. You have OpenBlocks installed incorrectly. All of the OpenMods mods require OpenModsLib. You have extremely old versions of many mods with know bugs/instabilities/crashes. You have not included a full set of config files with your pack. This is always "bad" and quite often fatal to the proper operation of a pack. You have some incompatibility between mods that is preventing OpenBlocks from properly initializing. Update all your mods and return here if you continue to have problems. I would normally list specific mods which are outdated but there are so many that it is better to just go through the whole list and get the latest compatible versions from the author's preferred distribution channels.
  10. Your modpack.jar file was fine, you just have to remove all the other stuff in the bin folder.
  11. There are a lot of variables in this scenario. Trying to resolve them without much more information would be challenging. How much RAM does your PC have? How much RAM are you allocating in the launcher? If the ram allocation in the launcher is more than your system RAM - 2G and you are running Windows you will likely have a bad time.
  12. Heh, I'll see what I can do. The crash that results from this generates 20-30 megabytes of log traffic in the server.log when it happens as it crashes to the command prompt.
  13. You are including the entire bin folder with contents. That folder should only contain "modpack.jar". It is a violation of Mojang's terms of service to redistribute minecraft.jar. There is no need to include the "hats" folder. It will get created when started the first time and needlessly bloats the pack. You have old version of many mods with known bugs/instabilities/crashes. Galacticraft, IC2, Backpacks, etc. You have MoCreatures installed but do not have the required dependency mod CustomMobSpawner-3.0.0. You have the MCPC+ binary in the mods folder. This needs to be removed. You have NEIAddons for Forge/MC 1.6.2. Get the 1.6.4 version. IDFixMinus is intended to be used to "fix" the configs then removed from the mods folder. It should not be distributed with the pack. This is, quite possibly, the primary reason for your client-server sync problems. You need to pre-download ForgeMultipart and put it in mods1.6.4. The one your included mods are downloading by default is very old. You should not be including "CodeChickenLib-universal-1.6.4-1.0.0.45.jar". It doesn't go in "mods" and you should just let CodeChickenCore retrieve that file on its own. You have mismatched mods for Galacticraft. GC and GCPlanets are b908 and MicdoodleCore is b1010. This is "bad". The version of Optifine you are including is not compatible with current versions of Galacticraft (at a minimum) and possibly other mods in your pack. Update to the most recent version. After you get the pack working correctly with updated mods, remove the client only mods (making note of my previous comment) for the server and copy over the configs from your working client (assuming you have removed IDFixMinus). Come back here if you are still having troubles.
  14. No need to remove Waila (might want it) on the server. Why would you remove Hats mod from the server? Players will only see random hats on people if you do that. Without a link to your pack(s) we will be unable to offer more assistance other than to say that 512M of ram is WAAAY too low for the list of mods you have.
  15. Millenaire has "problems" with filenames somewhere in it's path structure. Unzipping the file with WinZip or 7zip works fine, but whatever zip library is being used inside the platform doesn't like one of the files in there. I recommend re-downloading the files from the author's site and seeing if that gets you anywhere. I have gotten it to work for other folks with this problem by doing that.
  16. You are missing the required libraries. You can get them here: https://copy.com/qLsTvZfUUkkb
  17. The server has no need for binmodpack.jar. This can be safely removed. You have item ID conflicts between your mods. Check your FML log for the word "CONFLICT". There are conflicts between at least half a dozen mods. If you are including IC2 you likely want the recipe fixer since a number of the NEI recipes are messed up: As for your lag, your startup script needs adjusted. Currently it is this: java -server -Xms1G -Xmx7G -XX:MaxPermSize=6G -cp "forge.jar" -jar forge.jar Since you are obviously running Windows you cannot allocate more than 6.5G (and preferrably 6G) to the Forge/MC server without causing your system to start using swap space. This is "bad". Also, your MaxPermSize is just way too big. You probably want something more like this: java -server -Xms4G -Xmx4G -XX:MaxPermSize=256m -jar forge.jar nogui If you plan on having a couple dozen people online at once you can bump the 4G up to 6G. Otherwise, allocating more memory to the server process than it actually needs will negatively effect performance.
  18. So, a couple times now I've started getting crashes on my BTeam server with an error that looks similar-ish to this: java.lang.NoClassDefFoundError: net/minecraft/entity/CallableEntityTracker After some debugging I ended up increasing the permgen allocation on the server from 128m to 256m. After a number of weeks (don't remember exact time) I started getting this again. Bumping the permgen from 256m to 384m made the problem go away again. Any ideas what is going on here? I don't really care that it needs to be higher (I have plenty of RAM) but just want to make sure something isn't going off the rails or getting ready to melt down.
  19. When I click that link I get an HTML-404 error (page not found).
  20. If you provide no FML or crash logs, no modpack download URL and no Technic pack page how are we supposed to provide any assistance?
  21. The link you have provided is not a direct download and cannot be used in your pack settings as the download URL.
  22. 16.04 17:48:26 [Server] INFO We appear to be missing one or more essential library files. You are missing required libraries. These might help: https://copy.com/qLsTvZfUUkkb
  23. Calclavia does not always ensure that all of his mods work together when using the latest builds of each. Your best bet is to hit his IRC channel and ask which ones work together. You can also do some trial and error debugging to figure it out on your own.
  24. I don't mean to sound harsh, but no one is going to make this for you even though you have asked numerous times in numerous places. The pack you are asking for is HUGE and would take a skilled pack maker many, many hours to create, get all the immediate bugs out, integrate the mods which require it, balance things and then play test it to make sure everything is working as expected/desired. A pack this expansive is a labor of love and requires a serious commitment.
×
×
  • Create New...