-
Notifications
You must be signed in to change notification settings - Fork 14
doesnt work with league of legends #3
Comments
I don't play LoL myself but I'll try and test this out after the weekend. |
after searching around for a while i learnt that league also uses another address for updates
after adding this to the config files it starts working for a while then gives errors all similar in type: on the host pc the client starts updating normally and it pulls data from the cache but sometimes it decides to give an error . Patching failed and we're not sure why. Please restart the client to try patching again. (Error code 004.) its just annoying and it starts the update back from 0% reading the cache data again. server side log example (every other error is similar):
maybe its a slicing module problem but im out of ideas. |
Can you try putting this into the league nginx conf file? After |
that did cause the error to go away but now it doesn't always serve data from the cache even after fully caching it; goes to 12% from the cache then starts sending GET requests again. changes i made to fix some stuff:
to the league_dnsmasq.config and league_nginx.config uninstalled:
because it was blocking tcp port 53 and not letting dnsmasq run as intended. edit: the league cache folder is only 6.9gb of the 18 gb download size. |
Do you have any follow up on this @RyanEwen ? |
I'm sorry I haven't gotten around to working on this particular game. The readme has a quick-start but for more detailed setup check the Wiki: |
the steamcache generic setting works for everything including league. |
Next time I work on this project I will try to find the differences between steamcache generic and this, and close that gap. I don't get to work on this very often, though. Hopefully someone else might find the time sooner than I. |
the problem persists, some suggestion. |
the cache works for blizzard and steam but league of legends crashes during update.
The text was updated successfully, but these errors were encountered: