Rose v1.5.5
Highlights
- Custom mods are now checked and repaired when you add them. Rose has LTK Manager check each mod with the same rules it applies in game. What can be repaired is repaired right away (old audio banks, data a patch changed, textures), so old custom skins that crashed the game or lost their sounds can work again. A mod LTK Manager would turn off in game, such as a skinhack (a base skin that uses another skin's model), isn't added, and Rose tells you why. You no longer find out in a game that a custom skin doesn't work.
- No more black loading screen lasting minutes. LTK Manager checked the skin you picked again before every game; on a hard drive that took 4 to 6 minutes while the game was loading, so the loading screen stayed black or stuck at 2%. Rose now turns that automatic check off: mods you add are checked once, when you add them. (#481)
Fixes
- If LTK Manager's library held damaged mods, every skin failed with an "expected value" error. Rose now turns those mods off. (#479)
- Troubleshooting explains more LTK Manager problems instead of a generic error: its patcher never getting into the game (#475), LTK Manager or its patcher set to run as administrator, Windows error 740 (#468, #456), and LTK's service refusing to send LTK Manager its patcher, "rate limited" (#482).
- When LTK Manager refuses an official skin or chroma package, Troubleshooting points you to LeagueSkins instead of telling you to use the official skin. (#454)
- Skin downloads work behind a SOCKS proxy. (#454)
- Pengu Loader activation errors are readable on a Chinese Windows, and in other languages. (#449)
Under the hood
- The LTK logs (ltk_api.log, ltk_launcher.log) now go to the ltk folder of Rose's logs: right-click the tray icon > Open Logs folder. The always-empty ltk_bridge.log is gone. (#480 by @itsdaymi)
- Rose's log records which LTK Manager version it uses and how it was started, so reports can be diagnosed without asking for more files. (#478, #479)
- No more error spam in Rose's log on a Turkish Windows. (#478)
Thanks to @itsdaymi for the pull request, and to everyone who reported issues with logs.