ADD a "LOCK" feature to Rune Pages: In-select changes or 3rd Party Apps should NOT overwrite Locked

Sandomar·2/6/2020, 8:49:39 PM·1 votes·662 views

​THIS SHOULD BE A FEATURE

  1. Create a custom Rune page, Save it, Name it.
  2. IF you wish for this Rune page to be RETAINED on the server, regardless of changes you make during Champ Select for a particular match-up, or use of a 3rd party Runes assist that "pushes" rune settings for you: THEN have a radio-button/check-box for LOCK this Rune page.

EFFECT 3. If your champ gets banned, stolen, or you decide to make some edits to a selected Rune page; OR you make a complete change to the one you've saved for any reason, e.g. using a 3rd party app like Overwolf/Facecheck, then... 4. Edit/Push the desired Rune page into client and... 5. Later, in next match, instead of finding out that all of your custom saved Rune pages were overwritten, and finding that multiple uses of some 3rd party app has continually overwritten EVERY page, rather than just repeating saves to ONE/Same rune page...you'll find all your original, Saved, and LOCKED Rune pages intact.

  1. No longer must you Wonder: WHY is there no "LOCK THIS RUNE PAGE" option?

POSSIBLY: Just allow only "temporary" champ-select changes to any or all Rune pages, ever.

Changes DURING CHAMP SELECT could, by default, ONLY apply to the game you are entering. Upon NEXT game, in champ select, all saved Rune pages could be 'copied from' your SAVED or LOCKED library.

SAVED PAGES WOULD STILL BE THERE > so that changes you make DURING champ select are intentionally gone, since they are only ever intended as "This-Game-Specific for this champ and matchup." All your Saved, or possibly if RIOT adds it, only your "Locked" rune pages, should be STILL THERE being drawn from the server, INTACT and READY for the next match.

1 Comments

OwO Furry UwU 2/6/2020, 9:23:17 PM1 votes

Or you could just not use third party apps?