I haven't completely given up, I am concentrating on something else. Unfortunately, most Google results take me to resources for more established Linux distros, like Ubuntu. I use Arch, which builds everything from the ground up; booting into an Arch USB drops you to a simple CLI. You have to turn on services and begin to download packages to build a GUI and window manager. This means you have great control over exactly what is installed, but has the con of not using the same software repositories that more user friendly distros use. No dulaboot to Windows as well; forces me to learn and use Linux proper. Doing rather well. ;)
I'll keep a look out and post my results in case another user might have the same issue but never followed thru.
So.... Looks like I will be running the Windows version through WINE. I can only imagine what kind of memory errors I will get from a game like this...
I have been working with someone on the Arch forums to see if there is a package or something I need to install, libcurl-nss-so.4 is the only thing missing. So far, nothing has worked and 5 hours of Google-ing hasn't revealed helpful results. Maybe for Ubuntu users, but Arch is a different beast altogether.
If you are allowed or able, what libraries were used to build Crescent Loom against? Either that or if I had the source I could find why it is calling libcurl-nss-so and redirect to another library that is actually used on Arch systems.
The game was built in Cerberus X, which automatically transpiles to various things, so I don't usually directly touch the libraries it uses to talk to the OS.... however, CSX is open source so we can just search it; this looks like it might be promising? I just searched Crescent Loom's repo to confirm that I don't mention libcurl anywhere else. I am using that httprequest.cxs file to talk to the creature server, so that might be a good list to pursue.
Sorry you've had to spend so long googling this! >_< I appreciate you posting the problems/potential solutions here. I'm also happy to keep assisting to the best of my ability, I'd love to see the game work on more versions of linux.
https://bbs.archlinux.org/viewtopic.php?pid=2081108#p2081108
So, it involved building a package from scratch with some patches and i voila !
Crescent Loom now runs. I think, and I could be wrong, I am still waiting on emails and discussion, there is a push to get rid of Network Security Services (NSS) in favor of what is happening with OpenSSL??? or fold the functions into curl at a base level??? I am not clear on it with just a cursory glance at an article and the fix is for something quite niche for Linux users. The only reason why there is a large number of answers that worked for Ubuntu and other users is Ubuntu being more popular of a distrobution, but also fosters a "complete user friendly" system, while Arch caters to people that are trying to be like Windows power users and more. libcurl-nss.so would be included in some of the curl packages available to them as a "just throw the kitchen sink in" to ensure compatibility, not security.
Oh fantastic! I'm very glad to hear that. I'm having trouble following the discussion — is there an obvious way you see that I could re-build the game so it doesn't rely on that depreciated curl option? e.g. recompile a version of Cerberus X with different dependencies or while in an Arch environment?
I would say firstly; I am not a developer. My experience is also not in using ready-made engines; I made a Zelda clone a loooong time ago and made the tile-ing engine for it myself in BASIC. If I could give some advice; I would look at why libcurl-nss was being called and find a more recent/supported alternative to those calls. The developer of the engine would know way more and might be interested in the archlinux thread and use that to tweak their engine and release a new version.
It would require looking at the code before it gets compiled to binary. This of course, is up to you and how much further you want to go. Linux is already a 'niche' platform and Arch users are even smaller group still. It isn't known for being the most user friendly.
Maybe include info in the readme on how to resolve this issue IF that user has the same problem. Overwhelming majority of Linux users actually read those readme files.