Failed to save runebook due to corrupted runebook. [CLIENT]

MajorDanger·4/29/2017, 11:36:24 PM·4 votes·653 views

EDIT: Thanks Riot Corndog! Fastest way to have this resolved is by submitting a support ticket. Make sure to not use special characters in your rune page titles in the future!

This error started happening after I used the new client to re-order my existing runepages.

Cannot modify any runepage. Attempt to modify a runepage and save it results in the error message "Failed to save runebook due to corrupted runebook."

Error is repeatable. In fact it is not possible to not get the error if attempt to save a runebook is made.

I purchased an additional runepage from the store to see if this would fix the error, but the new page is not visible. EDIT: Close and re-opened client, and the new purchased rulepage showed up. After attempting to save, it did not work, citing the same error. After trying to access the page again, it was renamed from "Rune Page 18" to "@@!PaG3!@@122670345".

Please advise.

4 Comments

weaktweek4/30/2017, 4:09:30 AM3 votes

I've had the same issue, and seen a few other posts like this one. Unfortunately there hasn't been any positive response or fix posted that i've seen.

Redesignated4/30/2017, 6:44:41 AM2 votes

The error has been present since at least 7.7. The only fix anybody was able to find was to use the legacy client, which is now disabled, and became disabled during the course of this bug where it was the only apparent workaround. Riot has not said anything about it despite a considerable number of people experiencing it.

I'm mad.