Jump to content

Recommended Posts

Posted

So I set up a solder API finally, which was a project in itself. Ended up having problems with the SQL database on install, but I digress. I am working on building the repo, but I cant get any of the packs I built in the API to show up in the client. When I copy and paste the modpack address from the pack page on the main technic site, it tells me, "Invalid Solder link, contact the modpack author." I did not get any error messages when I added the API key or the solder address on the main technic site. On a related note... how long does it take to get info updated on your pack homepage? At first I only had 1 mod in the pack to test implementation, but I have since added more mods, and they are not showing up in the info page for the modpack. On a related related note... where do I find the UUID of the technic client so I can add that to the API. Thanks in advance.

Posted

Hate to bump again. I have been doing a lot of research where I can find it, including through the issues thread on TechnicSolders github page, but i am having little luck with this. Anyone have anything they want me to try?

  • Discord Moderator
Posted

The challenge with trying to provide support for problems involving Solder is that there are probably a dozen very different things that could be causing your issue. Maybe a couple different things working in conjunction which yield varying results based how how you alter other parts of the system. For very specific questions like "When I try to add a new version of a mod I am getting an MD5 sum mismatch when the client retrieves the file and here are the links to the file, API URL, webserver logs, etc." it is possible to track things down sometimes. For "my installation doesn't work and I have no logs for you, just anecdotal information" type requests there is little anyone can do to help you. It is assumed that one is already well versed in installing and maintaining the underlying structure (web server, SQL server, PHP applications, service level applications, etc.) before attempting to implement Solder for your packs. If I didn't already have strong suspicions about what is happening I would suggest trying to examine the web requests coming into Solder (server logs, pcap dumps, etc.).

 

  • All of your "mods" you have in your Solder setup are incorrectly packaged. The launcher simply extracts the solder-provided ZIP files into your modpack folder. None of your mods have the proper directory structure in them so you are getting mods in the root folder of your modpack instead of inside the mods folder.
  • You do not have Forge added as part of your modpack. You need to have a "mod" that is the Forge binary named modpack.jar which is in a folder named "bin".
  • You have no config files. Typically, with Solder packs, you will have the mods all packaged individually (or in sets like with Galacticraft) and have one zip file that contains all your config files. Look in one of Technic's packs (in the cache folder) for examples of how the accepted way to package configs.

Now, as to why you seem to be having troubles. I added your API URL to my launcher and it worked fine (aside from the fatal issues listed above). Where is the web server you use to host the Solder installation? Is it inside the same network as your client launcher? Are you exposing URLs to the outside world that are different inside your network? That is the most likely explanation for it working fine for me but not for you if your web server is sitting inside a NAT filtered network interface along with the client launcher.

Posted

Im not very surprised you had fatal errors as I havnt really looked into the pack in terms of the file structure and configs yet, I was just trying to get it to actually let me add the pack to my launcher and download what I had in there. The web server is one I am hosting myself, but the zip files are on dropbox. Now when you say they are structured wrong, I am guessing I misread the instructions for solder for the repo. If I understand you correctly, as I currently have it, for example, bigreactors_0.3.4a.zip currently only contains bigreactors.0.3.4a.jar. You are saying that jar needs to be in a folder called mods, very similar to the zip structure of the other modpacks? And while we are on that topic, do you recommend making a separate "mod" containing all the config files? Or should I include the configs in the individual mod zips?

 

Sorry for the confusion in the previous posts. I am glad that others were able to add the pack to the launcher, I continue to be stumped as to why I cannot add it. I will look more into that issue later on.

 

Thanks for your help.

  • Discord Moderator
Posted
  • Yes, you want to have a separate "mod" which contains all the config files. Do not include them with the individual mods.
  • Yes, the folder structure inside the Solder provided ZIP files for each mod needs to duplicate the folder structure for the modpack (i.e. mod files in mods, modpack.jar in bin, etc.).

As for your pack, if it works outside your network, but not inside your network you have some routing, DNS resolution, NAT, etc. issues of some sort going on.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...