Jump to content

sphereii

Members
  • Posts

    3,079
  • Joined

  • Last visited

  • Days Won

    23

Everything posted by sphereii

  1. In order to download the older versions, you would have to use the Download From Steam option. This will sync up the older alphas.
  2. Can you try Ravenhearst 7 Days Horde Edition? When you install the game for it, check the mark that says "Check here to download from mirror" and see if that lets you play that mod. It'll download from GitLab instead of Github, which is another hosting site.
  3. Each UI needs to know a fair amount about the base mod; Simple UI would have to be ported to work with WotW. I'd ask in the Simple UI thread to see if it's possible.
  4. This is a weird one. You are getting errors like it's still the SSL connection. Do you have any anti-virus or firewalls, other than default windows? maybe it's interfering and rejecting the change? - - - Updated - - - Is there a mod that currently has the 120 slot backpack?
  5. Never be shy reaching out for help. It's never a bother. It looks like the copy of the game failed, even before applying the mod. Are you running and anti virus programs?
  6. I looked at the history of the repos, and see where the files were. I am not sure what caused the issue with the bad one copying over. For replacement files like compo pack, I usually recommend creating a top level folder with the file in, and I can modify the configuration to either use the default or compo pack.
  7. The index out of error occurred by a trader bug it seems. Likely an NPC or something got too close to a trader, and it crashed the mod. While the launcher is showing an error downloading, it's actually throwing an error on the RSS feed, but not the mod download itself. - - - Updated - - - One users reported they installed 4.6.2, and it didn't seem to work for them. Once they installed 4.6.1, it started working. I'm not sure why that is, since the mod launcher doesn't really use anything special about those different versions. If you can confirm that 4.6.1 is installed, re-send your log files please, and I'l be happy to look.
  8. Glad it worked for you! The love of Windows 7 is still strong; and the distrust of 8/10 even stronger, it seems. Fun Facts! Windows 7 was released in 2009, with 8 appearing in 2012 and 10 in 2015. Mainstream support ended on January 13, 2015. Extended support ends on January 14, 2020. Installing Service Pack 1 is required for users to receive updates and support after April 9, 2013.
  9. There's a few things you can do. By design, it wants to over-write and keep everything up to date, because running an out of date mod is potentially against what the modder wants. However, for people who love tweaking, it's a bit of a challenge. Here's a few things you can do, and you may choose what works best for you. [ Simple and Easy ] 1) Make your changes under TempMods. Then, uncheck the Refresh Mods automatically, and play as normal. 2) Make your changes as you normally would, and run the 7daystodie.exe manually, skipping the Mod Launcher completely. [ Advanced ] 3) Make your changes in the files, then host the files somewhere, and create a My mod to download the full mod, then download your changes.
  10. Did the .NET auto-install? Here's the link for a manual install: https://www.microsoft.com/en-ca/download/details.aspx?id=49981
  11. Welcome back Sorry you are running into the error. Have you rebooted since you applied the EasyFix? I usually avoid rebooting when I'm told to, but in this case it's necessary. The EasyFix updates a few registry values to enable the TLS.
  12. Done, kind sir! I pushed the release a few hours ago, and things seem to be going well for the affected users.
  13. Attention Windows 7 Users! Due to GitHub changing from SSL to TLS, the Mod Launcher had to update in order to authenticate to download! This is available in the new Mod Launcher verison 1.0.4.8 and Higher. However, for Windows 7, TLS support is *not* enabled by default. Microsoft has an easy to use program to enable it: 1) Download their tool: https://download.microsoft.com/download/0/6/5/0658B1A7-6D2E-474F-BC2C-D69E5B9E9A68/MicrosoftEasyFix51044.msi 2) Run the Tool and apply the EasyFix 3) Reboot your computer ( Do not skip this step, otherwise it won't work) This is a one-time program to run, and only if you are running Windows 7. All current versions of Windows are compatible with TLS by default (8, 10). If you still get a message about Required .NET Framework upgrade, and it does not install it automatically, download it here: https://www.microsoft.com/en-ca/download/details.aspx?id=49981 I thank you all for your patience over the last 24 hours that this change was pushed out, and please let me know if any mods still does not work for you.
  14. What version of Windows are you running?
  15. Oh it's definitely not something you are doing GitHub dropped SSL support yesterday, which was kind of old protocol anyway, and just allow TLS1.2 now. Unfortunately, the different versions of .NET and windows has wonky support for that protocol. I'm playing around with some releases today to try to fix it, but it seems if you have the latest version of the .NET 4 installed, it'll work better. The Mod Launcher should auto-update to this in 1.0.4.7 or higher.
  16. Did you connect to a Valmod server with War of the Walkers mod installed locally?
  17. The Mod Launcher allows you to easily install and play multiple mods with little fuss. It's never been a gate-keeper; A requirement for being in the mod launcher is that it's still available for manual installs should someone wish to do so. The Mod Launcher has over 80,000 users now, so there's a few people who have faith in it The reason it broke yesterday was due to a change in GitHub. I've pushed a fix to hopefully fix it.
  18. I got back home this morning and been looking at it. I think it might be just adding a dependency on the newer .NET framework, which will be auto-installed in a few minutes, once I push this minor update. Let me know if it fixes the problem for you, as I have been unable to reliably reproduce it.
  19. Sorry you are still having trouble. Next time you get that error, would you mind posting a few logs for me to look at? With the mod selected, click on the View menu, then Log Files. Select the 7d2dlauncher.txt and click on Upload Log file. Give me the link to that pastebin.com link. In the same screen, you'll see the output_log.txt. You can upload that log file as well, and we'll see if we can get you sorted
  20. Sorry for the trouble. I need to push out a patch soon. GitHub made changes today.
  21. Working for some but not for others. They dropped support for a SSL method that the launcher defaulted too.
  22. Sorry for the trouble. GitHub made a change to my and the mod launcher needs an update for it. Hopefully I can push the update soon
  23. Yes, that seems exactly it. I'll work on a patch for the mod launcher.
  24. I did some tests, and looks like something changed with github and the direct download. HaidrGna pushed out a change to his config to help. Can you restart the Mod Launcher, and try again?
  25. Strange. I'll be home soon and will be able to test. It does look like something may have changed with github, if the other mods are starting to fail.
×
×
  • Create New...