Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shortcut automatically changes to "regular" shortcut #2

Closed
Zero8000 opened this issue Oct 18, 2023 · 2 comments
Closed

Shortcut automatically changes to "regular" shortcut #2

Zero8000 opened this issue Oct 18, 2023 · 2 comments
Labels
Bug Something isn't working Can't Fix This can't be fixed on our side Riot's Design Choice This relates to the way Riot Designed things to work.

Comments

@Zero8000
Copy link

Zero8000 commented Oct 18, 2023

Version

2.0.1

Describe your issue.

Generally speaking the shortcut creation goes fine, but after opening it the first time the shortcut automatically changes to the one used automatically by Riot's client, with the launch-product line to open League from the Riot launcher. I have to re-run the script after deleting the first shortcut. Even still, whenever I open, I often have to attempt to open the game three times or so before it finally opens as the Riot launcher comes up, then it shows me League in the launcher, and then the game opens in my desired language.

Have you modified the script?

Yes.

User Modifications

Shortcut location changed from the original to where I have the game installed (E: drive.)

Discord Username

Zero8000 (zero8000)

@KuryKat KuryKat added the Bug Something isn't working label Oct 18, 2023
@KuryKat
Copy link
Owner

KuryKat commented Oct 18, 2023

Thank you for your issue report! I will look into it to see if it can fixed on our side.

However I should inform you, the LeagueClient shortcut gets automatically updated to the RiotClient location once you execute it, that is Riot's intended design. Sadly there is not much I can do to mitigate that effect. The only thing you can really do is run the script again every time you need to change the language again.

About the second issue: have you tried making sure that you closed the Riot Launcher in the system tray to assure that the game is fully closed before trying to run the script again?

From my experience I noticed that the Riot Launcher will always try to ensure your specific Region's Language, probably an intended design, so the way I found to mitigate this is to completely close the Launcher before opening the game again with a new Language.

To achieve this you first have to open your Riot Client, then click on the "User"

image

Then click on Settings

image

In there make sure you don't have the Riot Client to run on startup, and also set the Close Window behavior to Exit the Application.

image

After that, close the Riot Client, make sure to close it in the system tray as well if is still there:

image

Then trying running the Script and executing the new LeagueClient shortcut, you can delete the created shortcut after you open it, as it will get updated to the new location anyways 😅😅

image

image

Then whenever you need to change the language again you just need to run the script again, ensure your game is fully closed, and run the new shortcut!

Hope this helps! Thank you for your time and your report!

@KuryKat KuryKat added Can't Fix This can't be fixed on our side Riot's Design Choice This relates to the way Riot Designed things to work. labels Oct 18, 2023
@KuryKat
Copy link
Owner

KuryKat commented Oct 18, 2023

Let me know if you have any other concerns or comments, I will close this issue for now as it isn't something I can actively mitigate, if you have any more information that can be useful for us to know how to change this behavior, let us know!

@KuryKat KuryKat closed this as completed Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Can't Fix This can't be fixed on our side Riot's Design Choice This relates to the way Riot Designed things to work.
Projects
None yet
Development

No branches or pull requests

2 participants