Jump to content

plowmanplow

Discord Moderator
  • Posts

    4594
  • Joined

  • Last visited

  • Days Won

    74

Everything posted by plowmanplow

  1. OreSpawn is notorious for causing this kind of issue.
  2. As previously mentioned, the API URL is the URL you would paste into your Launcher to add the pack. Paste that link in here.
  3. All of these errors: java.net.UnknownHostException: session.minecraft.net and Disconnecting DeadlyOptics [/24.61.178.205:65140]: Failed to verify username! [internal error java.net.UnknownHostException: session.minecraft.net] Implies that your host is having trouble getting out to at least the MC session servers, and likely more than that. Investigate your network connection.
  4. Don't try to maintain multiple threads. Keep all the information here. Until you provide your modpack API URL we cannot continue.
  5. Look into Linux Screen or Tmux. Both will allow you to start the server in a virtual console which will permit you to detach and reattach later. Since your server is hanging/crashing, you should have a crash report, or at a minimum some information in the server log to help diagnose what is going on when it dies.
  6. Things to check: Is there some backup or other automated process running every 30 minutes which might be lagging the client/server communication enough to kick you all? Does the disconnect happen after 30 minutes online, or on specific 30 minute intervals? Is the server restarting when this happens, or is it just "pausing" due to lag/load? How much RAM are you allocating in the server startup script?
  7. This probably belongs in Platform Pagoda since you are now working on a custom modpack. Without a link to your crash report and most recent Forge Mod Loader log it will be difficult to provide assistance.
  8. Modpack assistance for packs maintained by the Technic group should be submitted through the tracker at the top of this page.
  9. What version/build of MCPC+ for 1.4.7 are you using? Not that one anecdotal reference means much, but I've been running TekkitLite on the latest (L67 & L70) for 18+ months and have never seen this.
  10. @Bradenhelmer: You might have better luck starting your own thread for this. That being said: java.lang.UnsupportedClassVersionError: codechicken/nei/asm/NEICorePlugin : Unsupported major.minor version 51.0 This implies that your ChickenBones' mods are mismatched. Make sure you are using the correct, matching versions for the version of Forge/MC you have selected.
  11. No worries, but you might want to read the sticky posts about proper use of the forums before continuing. That being said, the post cannot be simply moved. The procedure and process for posting in the respective trackers is different than a regular forum.
  12. Problems with modpacks maintained by the Technic group, or problems with the Launcher, should be directed to the Tracker links provided at the top of this page.
  13. The link you have provided is not a valid modpack link. It's not even a link to a ZIP file, but a JAR file. Additionally, you have been asked multiple times to provide the API URL so that we can properly work on your issue. This is the URL you would paste into the Launcher to add your custom modpack. The URL you provided is also linking to a file that is well over 400M in size. This is WAAAY to big for a modpack. If it's that large you have either: 1) Done something very wrong, or 2) Tried to include everything and the kitchen sink in your modpack. (1) we can help with. (2) ain't gonna fly. Again, please provide the API URL to your custom modpack. Edit: I went ahead and downloaded that huge file you posted. Here is some information: The modpack archive must be in ZIP format only, and have the extension of ".zip". The modpack archive should only contain the following folders: bin, config, Flan, mods The bin folder should only contain the file "modpack.jar" which is simply the correct version of the Forge universal binary JAR file renamed to be "modpack.jar". You should never include the modsVoxelMods folder in your modpack archive. The files there will overwrite each client's personal settings. You have multiple duplicate mods, often as both ZIP and JAR files. (i.e. DynamicLights) The Forge installer JAR does not belong in the modpack archive. You should not include any DEV or API (when the API files are intended for use only by developers). The modsdevelopment folder and its contents should be removed. You have mods for both 1.7.10 and 1.7.2. Make completely certain that the 1.7.2 mods are designed to work with both 1.7.2 and 1.7.10. If they do not explicitly state that they do, they probably don't. You have multiple "installers" for mods in your mods folder. The mods need to be installed by you and only included in your modpack archive after installation is complete. That being said, any mods you get as "installers" are HIGHLY suspect as the vast majority of mod devs provide their mods in ZIP or JAR format directly. You have multiple minimap mods in your archive. Choose one and remove the rest. It is highly recommended that you do not include Optifine in your modpack archive. Including it violates the author's restrictions and the mod has a long history of causing problems on some platforms. Have users who want it add it themselves. Good luck.
  14. Why do you have two threads running for the same issue? That is very confusing and impossible to support properly. Please pick one, post there, and stick with it.
  15. Also, always provide the link to your API URL when requesting help.
  16. Always post a link to your API URL when requesting help.
  17. Not really. The API URL is the URL you paste into your launcher to add the pack. The link you provided may suffice this time. As for the log file, we are talking about your most recent ForgeModLoader log file and/or a crash report, not the Technic Launcher log. Finally looked at the pack: Oh, my. Your Forge version in the modpack.jar file is for MC 1.5.2. This is probably not what you want. You have mods for Forge/MC ranging in version from 1.5.2 to 1.7.10 including every version in between. This will not work. You'll need to settle on a specific version and use mods designed for that version (highly recommend 1.7.10). You are missing most of your config files. All modpacks, regardless of version, should contain a full compliment of config files.
  18. Always make sure you alter your file explorer settings so that the file extensions are displayed. That will ensure that you don't have the extension duplicated. When I said post your startup script in a code tag it should have looked similar to this: @echo off java -Xmx2048m -Xms2048m -XX:PermSize=128m -XX:MaxPermSize=128m -jar cauldron-1.6.4-1.965.21.174-server.jar nogui Without seeing exactly what your script looks like, and precisely what the name of your jar file on the HD is, I can't really advise you. Did you use the installer for Cauldron, or do you just have the server JAR?
  19. To my knowledge, this was the last build of Cauldron for 1.6.4 before the DMCA debacle: cauldron-1.6.4-1.965.21.185-server.jar Please post the contents of your launcher script in a code tag and verify that the file/jar referenced by your command in the script is actually present. Keep in mind that you will need the libraries for that version of the Cauldron server since it does not automatically retrieve them. Cauldron 1.6.4 Libraries if you can't find the installer.
  20. Provide log output (in a spoiler tag or a pastebin). Provide the API URL for your custom modpack.
  21. Totally agree. Anything less than 1.7.10 is pretty much handicapping yourself at this point. Everything I listed (except for the stated exception) has a 1.7.10 version. As for Voltz, that is an entire modpack made and maintained by the Technic group. If you want a few specific mods from there, and they have 1.7.10 versions, then go add them in. If you want to do the whole thing as a 1.7.10 pack plus a ton of other stuff that may be a bit ambitious for your first time out the chute.
  22. That looks like it may be a client mod on the server, or a mod coded improperly which should be on the server but won't work there because it was poorly written. Try removing the Pokechest mod from the server.
  23. I recommend Liteloader + voxelMap for LiteLoader ( http://minecraft.curseforge.com/mc-mods/225179-voxelmap/files and http://www.liteloader.com/download ) Google (Requires bspkrsCore) Google http://ci.micdoodle8.com/job/Galacticraft-1.7/ (3 jars) http://forum.industrial-craft.net/ (may be down) Google Google (requires Mantle) http://ci.indiewikis.com:8080/job/Mekanism/ Google Google (requires a specific version of Buildcraft) Google (Calclavia mods) (Now part of ResonantInduction, Requires ResonantEngine) Google (iChun mods, requires iChunUtil) Google Google (ChickenBones mod, requires CodeChickenCore) What is a "vlotz"? Google (TeamCoFH mod, requires CoFHCore and ThermalFoundation) Google (TeamCoFH mod) May not be a 1.7.10 version. Kind of pointless anyway since you have a glut of weapons. Google Google Google http://build.technicpack.net/job/Inventory-Tweaks/ Google Not available yet. Kind of recommend against it anyway with this many mods adding armor, would trivialize much content. Google (Calclavia mod, required by ResonantInduction) You may want to add EnderIO to provide more power and item transport. It would be recommended to disable ore generation in other mods (when possible) and use ThermalFoundation to do all ore spawning. However, this makes things "less trivial". MFR has a block called a Unifier which can consolidate resources (ore, metals, etc.) of different types to one preferred type. Fairly easy to use. The items marked "Google" can be found following the guidelines in the previous post about "Getting Mods".
  24. Sure. Make a bulleted list of features you are looking for and I'll make suggestions for mods or sets of mods to provide the functionality.
×
×
  • Create New...