Following on from the removal of our legacy lessons from the code base this week, I will continue retiring
Script Compatibility Mode from WaniKani by removing the legacy review code next Monday (28 November 2022).
If you want to check in advance whether this change affects any scripts you’re using, please turn off
Script Compatibility Mode in the app settings if you have previously enabled it. If it is already turned off, then you should not notice any change when the code is released.
Once the legacy reviews removal has been released I will complete the retirement of
Script Compatibility Mode behind the scenes. This will include removing it from the app settings shown above. I won’t write a separate update for this as I don’t expect these changes to impact anyone.
Thanks again for your continued support.
This will break REORDER ULTIMATE 2. You may want to consider switching to Reorder Omega. I know change is frustrating, and that Omega can be confusing, but if you have any questions (about Omega) I am happy to help.
Does an Omega-6 egg cost twice as much as an Omega-3 egg?
No, it’s 3 times more because 6 is 3 more than 3
If userscripts are being removed, is it possible for wanikani to natively support on’youmi in katakana and kun’youmi in hiragana? It makes learning for me a lot easier and opens the door for using my phone to learn kanji. Thanks.
Userscripts aren’t being removed (WK can’t remove them since they run from a browser extension), they’re just removing the script compatibility mode which… does… something…
… I don’t really know what it does to be honest…
so in a nutshell, most scripts are more or less closely tied to the WK webpage (no surprise) and its underlying structure (this is the important bit). Some time ago the WK team started to change this underlying structure quite a lot without the normal user being able to notice, but it made a huge difference to many scripts, and so many of them broke more or less. At that point the WK team introduced “compatibility mode” which basically was the old website before those changes. So the users would still be able to run their old scripts. The idea probably was to buy some time for the script devs so that they could adapt their scripts to the new webpage. But many of the script devs are no longer around, and so this didn’t work out exactly as planned, I guess. Now it’s a huge PITA for the WK developers to have two versions of basically the same thing around, and so compatibility mode is being removed right now, i.e. everybody is forced to use the new webpage, and the scripts don’t work any more. That’s all.
Thank you @NicoleRauch, your assessment is correct.
Further to this, if anyone is curious, there is some documentation in the knowledge base about
script compatibility mode. This will be updated / removed in the coming weeks once the transition is complete.