Skip to content

I know league is a big game...

Crowfeather··4 votes·952 views

... but I'm reasonably sure it's not 30,000 individual files big.

Yesterday when 5.3 came out, my patcher scanned over 26,000 files in part 2 before it started actually updating the game. I was able to play matches and use League normally.

Today, when I got home, I booted it up to discover it at "33% Calculating Differences" once more.

Over 4 hours later, the file count reads 31,300 and increasing as I type.

This is an incredibly frustrating bug that makes me dread updates, because they usually mean my league will update for several hours and I'll be able to play little to none that day.

Could we get some clarity on why the patcher acts like it does, at the least? I'm not asking for a full fix (although that would be nice), because I understand it would be a lot of work and may even be being worked on right now, but I feel like if I knew the reason my league patcher's file count was higher than the total individual files on my Windows account , I would be more understanding of it.

3 Comments

ValyrianBlade1 votes

I strongly agree. Whoever is managing league's files needs to get fired.

There is a file archives folder. It has over 15000 files in it, and weighs in over 2GB.

Interestingly enough, deleting this folder will get you past the 33% stuck problem consistently and reasonably quickly. You'll just have to redownload the full 2-3GB folder, which takes quite some time.

Whoever is managing this needs to learn something - you NEVER archive everything. There should not be any reason to have more than 4 time stamps archived: most recent release, most recent stable environment, start of season environment, start of game environment.

Anything else is unnecessary, and unless the folder is poorly named, having 15000+ files here is "termination-of-employment-worthy".

Also, to patch by " calculating differences" is completely stupid. A much easier and faster way to accomplish the same feat:

  1. Include a "last downloaded update file"
  2. In the file timestamp the download
  3. Check the time stamp of the league folder versus the time stamp in the file
  4. A. If consistent, apply all updates between last downloaded patch and current patch
  5. B. If inconsistent, request the player to reinstall league.

I feel like 4B is the only reason we need calculating differences. They're afraid players will delete their files and thus can't just update by applying all updates since the last one. If you're messing around in your league files without knowing what you're doing, I'm fine with you needing to sit through an extra long download each patch until you learn not to so the rest of us can have smooth patches.

As of right now I'm appalled at the state of the patcher. I downloaded 5.3 2 days ago and it took almost 4 hours because it crashed at 99% and then got stuck at 33%. Then this morning it has another update and gets stuck at 33% again. I've only done a bot game each day since 5.3 because I've had no time due to the patches taking all of the time I had allocated to play.

Crowfeather1 votes

I wasn't aware of the archive folder; that does seem incredibly stupid. I wonder if there's a reason for it or if it's just vestigial. Either way, I might have to redownload it, but I'd rather try to just let it run its course this time, due to the fact that my internet is god awful. If it goes too long I might do it anyway though, it's close to hitting 40,000 now. Thanks for the advice.

And yeah, I think it's set up to scan the ENTIRETY of the league folder every time anything client-side is released. If so, the re-updates after new patches are probably bug fixes that they don't tell anyone about. Only speculation, though.

And no, I'm not messing with my league files lol, this has just been happening to me for a long time and today it was worse than ever.

ValyrianBlade1 votes

Yea, I don't think hardly anyone messes with the files. I was just saying that I think the only reason they do this calculating differences step that scans thousands of files must be because they literally check every file and thus they're not just looking at the files they're expecting to change; they're looking at all files in case the player intentionally/inadvertently changed something.

More from [ARCHIVED] Miscellaneous

More by Crowfeather