Jump to content

plowmanplow

Discord Moderator
 View Profile  See their activity

  • Posts

    4594

  • Joined

  • Last visited

  • Days Won

    74

 Content Type 

Everything posted by plowmanplow

  1. plowmanplow
    This is an edge case which is likely not time/cost effective to implement. Just use one of the other publicly available hosting services (I like copy.com).
  2. plowmanplow
    That is likely caused by mismatched mods and APIs or an outdated mod and Forge combination. In any event you will need to post links to your Technic pack page, API URL and/or the download URL for more assistance.
  3. plowmanplow
    No. That tab is produced when the pack is linked to a Solder API installation. If you are not able to find/install this on your own then you can safely ignore it.
  4. plowmanplow
    If this is your modpack then post links to the client and server downloads. If it is someone else's pack then contact them for assistance.
  5. plowmanplow
    It means that you have not removed all of the client only mods from the mods folder.
  6. plowmanplow
    You have too much stuff in the bin folder. Remove everything but "modpack.jar". You have an outdated version of Forge for your modpack.jar. Get the latest build (965). The "config" folder in your modpack archive is named "conifg" (note the misspelling). You have some severely outdated versions of some mods (Backpacks, Biomes O' Plenty, etc.).
  7. plowmanplow
    Patience grasshopper. Nobody is getting paid here and I took a few vacation days over the USA holiday weekend. RivalRebels seems to be constantly overwriting its config file, a clear sign of a poorly coded mod. You will need to edit Mo' Creatures config in order to resolve this conflict. However, you have a bigger problem. You have a lot of mods which are adding entities and are running out of entity IDs/indices. You will need to figure out which one of your mods is incorrectly using too many ore remove entity adding mods until there are few enough to work together.
  8. plowmanplow
    All the required folders (bin, config, mods) in your modpack archive ZIP file are in a subfolder. The required folders must be at the top level of the directory structure in your archive. The bin folder should ONLY contain the file "modpack.jar". This file is simply the correct version of the Forge universal binary JAR file renamed to "modpack.jar". The config folder must contain all the config files from your working local modpack instance. Forge/MC 1.6.4 packs do not use a coremods folder. All mods belong in or below the mods folder. You have extracted all your mods to folders. Always follow the author's installation instructions but most mods just need to have the files distributed by the author dropped into the mods folder. Do not extract them unless specifically told to do so. You have an "installer" for Damage Indicators, IndustrialCraft, ThermalExpansion, maybe others. The author distributes these mods as a single file downloads. ONLY get your mods directly from the mod author's preferred distribution channels. To do otherwise invites virus and spyware infections. Fix all these problems and come back here if you are still having problems.
  9. plowmanplow
    The original error you posted often pops up when trying to use IDFix. IDFix is not meant to be used while the pack is running. Run the pack once to get the configs created and then disable/remove it. Try starting your pack again. You might get ID conflicts but you should be some more useful error messages. As previously stated, always provide a pack page, API URL, and/or download link for your pack when asking for assistance.
  10. plowmanplow
    Contact the maker of the modpack and/or the owner/operator of the server. We will not be able to provide much help for someone else's work.
  11. plowmanplow
    CodeChickenLib and ForgeMultipart belong in mods1.6.4 not the mods folder. Your version of Project Red has known problems. Update to the latest version. IDFix often just doesn't work as expected. In the case of your modpack it fails utterly. Run the pack once with IDFix in place and it will crash out. Disable IDFix and run again. The client will inform you that you have one block ID conflict which can easily be fixed. However, you'll have a large number of item ID conflicts which will need to be fixed. As for why the pack isn't downloading you have not provided enough information. Please provide a link to your Technic pack page or the API URL.
  12. plowmanplow
    For copy.com simply take any public share URL you create and add "?download=1" (without quotes) to make it a direct link which will work on the platform.
  13. plowmanplow
    That link does not work. As for the mods, if you are making a 1.6.4 pack then almost all mods are the same for SSP and SMP. There are some "client only" mods. Once we can see/download your pack it will be easier to know which ones are client only.
  14. plowmanplow
    Second vote for copy.com Any file you share will yield a public URL. Just add "?download=1" (without quotes) to make it a direct download.
  15. plowmanplow
    The first time the mods is loaded it will make its default config file.
  16. plowmanplow
    Your pack is not downloading correctly. A few possibilities: URL is not public, file is not shared as a URL. I've never seen anyone posting a pack link using Amazon's services so I don't have a lot of suggestions.
  17. plowmanplow
    The modpack archive currently tied to your pack has these problems: Still many, many ID conflicts. Player API Core is not installed properly (look inside the zip). Smart Moving is not installed properly (look inside the zip). You need to update to the latest CodeChickCore for 1.6.4 (0.9.0.9 as of this post). (fixes the crash)
  18. plowmanplow
    Modpack archives intended for use in the platform must be "direct" download links. If you paste your zip file link into the browser URL bar and it shows you a web page then it is NOT a direct download. Each public hosting provider has a different way of making the shared/public links direct. Google is your friend here.
  19. plowmanplow
    @Slayer19 If you aren't using Hamachi (and you really never should) you leave the IP settings in the server.properties file blank. You have to open a port through your firewall/router which is redirected to your local PC on the same port your MC server is running on (default/typical 25565). You can see your public IP and test the open port (when the server is active) here: canyouseeme.org
  20. plowmanplow
    If you have a modded client and can connect to a server one of two things is happening: The server has all the exact same mods, versions, and configs as your modded client. The server has the same vanilla version of Minecraft but is not running Forge. Your scenario sounds like #2.
  21. plowmanplow
    It seems like you might be starting vanilla minecraft instead of the Forge jar (BTeam.jar in this case).
  22. plowmanplow
    Nope, you can leave those at the default settings. And yeah, 1.25 up isn't amazing but it should be enough for a couple people. When the other person is trying to connect and is experiencing major lag what is the server TPS at?
  23. plowmanplow
    Hmm. Nearly singlehandedly supporting Platform Pagoda (with all respect to others who have helped) for the last few months at least implies that I might have an inkling of what I am talking about. Yes, you might be having few issues. I am just stating that the overwhelming body of evidence indicates that a pack of that size on a Windows machine with 4G of ram will often have some distinct challenges. I wasn't saying it wouldn't work.
  24. plowmanplow
    Wait, so you get no lag when connecting to the server running on the same local machine but a remote person does? Could be bandwidth issues. What is your upload/download speeds? speedtest.net
  25. plowmanplow
    @slayer19: How much memory does your PC have? How much are you allocating in the launcher?
×
×
  • Create New...