OrangeNote
commented
5 years ago The favorite page feature was originally planned in the early stage of development. Then I changed my mind and discarded the idea, because I thought that the app shouldn't actively interact with the game client without requiring user's action.
Nowadays it seems Riot allows that kind of automation, but still I have no plan to add new functionalities to RuneBook. Thanks for your suggestion though.
Blitz.gg app and OP.gg extension have an auto-import feature that automatically sends the most used runes per champion to the game, but RuneBook has a big potential other alternatives don't: local rune pages.
But wich rune page should Runebook send to the game if the user has many personalized local runes? That can be solved with a "favorite runes" feature: the user can mark just one page as its favorite (one favorite per champion), and RuneBook will send that page automatically to the game when the champion is locked. Then, if the user feels like using alternative runes for a match in particular, they can choose them manually from the app and overwrite the auto runes just for that game.
If the user doesn't have a favorite rune page for a champion, they have to select their runes manually from the app or... maybe the app could send the most used runes for that champ (from op.gg or maybe a secondary local datebase)? Of course that would require that the auto-import feature could be turned on and off.