Someone should pay WaniKani to have an indefinite vacation and stop breaking shit. I don’t see improvements anyway, they just broke my learning streak by completely overhauling mnemonics halfway through (so that just confused my brain completely with the ones I already knew) and now all the time scripts falling victim to the tech entropy. Just chill, don’t touch it, let us learn… Jesus Christ…
5 Likes
Wow, my review page became monochrome.
RIP.
Because of a few users, they broke compatibility for many more users…
4 Likes
Got an error. Any ideas on how to fix it?
TypeError: Cannot read properties of undefined (reading ‘0’)
at Number.eval (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=f5733fc8-69a0-4a50-83d8-1871f63eeade:257:60)
at Function.each (https://assets.wanikani.com/assets/v03/review/application-fcfa8e614d53542baf1fc02697e12216e8167a19fc88d79ecb4e0f70a3671bc9.js:14:17232)
at Object.apply (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=f5733fc8-69a0-4a50-83d8-1871f63eeade:251:23)
at Object.create (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=f5733fc8-69a0-4a50-83d8-1871f63eeade:280:30)
at Object.init (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=f5733fc8-69a0-4a50-83d8-1871f63eeade:241:26)
at eval (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=f5733fc8-69a0-4a50-83d8-1871f63eeade:743:15)
Logs:
WKU Init()
2 Likes
Turn on script compatibility mode in the Wanikani settings. I’m not maintaining this script anymore as-is. It’s not actually my script, so I’m not keen on keeping it alive anymore in the face of significant changes. I may write my own version later in December… something that I feel comfortable supporting. But I can’t make promises until I know what my schedule is going to look like. Since I completed WK years ago, I just do scripting now for fun when I have time.
13 Likes
Thank you. It does work with Script Compatibility mode turned on… for now…
No man, they added BIG improvements like 2 new kanji and like 30 new vocab words. That’s worth breaking stuff and causing issues for lots of people, right?
2 Likes
I had the same issue. Turned on Script Compatibility mode as suggested and it worked. Thanks!
Stopped working for me even with compatibility mode turned on. I just keep getting the same five reviews over and over. Pity.
EDIT: actually it was another script, WaniKani Speed, causing the issue.
Zannen, got the monochrome bug, narrowed it down to this script, then with compatibility on it doesn’t monochrome but also doesn’t seem to work right. I guess I’ll learn to enjoy hard mode
edit: multiple reloads/browser reset fixed it. Yokatta
I might see if I can get around to making my version of reorder as well
1 Like
I’m currently trying to make one too. The major problem right now seems to be updating the elements in the activeQueue during review sessions, since manually overwriting the entire list seems to cause some issues with WK’s mechanism for downloading the full objects for the subject ids when an item is moved from the full queue to the activeQueue. You can manually download items from /reviews/items to update the activeQueue, but just overwriting that queue doesn’t seem to update the internal cache of downloaded items, which can lead to the cache slowly filling up and items no longer being loaded in there by WK itself for subsequent reviews in the session. It’s making it a bit harder to get reordering reviews to work correctly. So either I use a hack to get to the cache and update it myself (which will probably break the moment a new update gets rolled out), or I just reimplement the entire review downloading process in the script (which will probably be very inefficient as a result). I’m not too sure what to do there yet.
Reordering lessons is still the same as ever though, as the queues there still download everything ahead of time, which simplifies reordering a lot. Reordering reviews is still a work in progress. 
1 Like
The script told me to post this error here:
apply/<@moz-extension://b31ab166-cdc4-44d6-a3ee-935d24f7790a/userscripts/Wanikani%20Reorder%20Ultimate%202.user.js?id=161eb448-5778-4f61-a069-075f1e45e5eb:257:29
each@https://assets.wanikani.com/assets/v03/review/application-fcfa8e614d53542baf1fc02697e12216e8167a19fc88d79ecb4e0f70a3671bc9.js:14:17232
apply@moz-extension://b31ab166-cdc4-44d6-a3ee-935d24f7790a/userscripts/Wanikani%20Reorder%20Ultimate%202.user.js?id=161eb448-5778-4f61-a069-075f1e45e5eb:251:23
create@moz-extension://b31ab166-cdc4-44d6-a3ee-935d24f7790a/userscripts/Wanikani%20Reorder%20Ultimate%202.user.js?id=161eb448-5778-4f61-a069-075f1e45e5eb:280:30
init@moz-extension://b31ab166-cdc4-44d6-a3ee-935d24f7790a/userscripts/Wanikani%20Reorder%20Ultimate%202.user.js?id=161eb448-5778-4f61-a069-075f1e45e5eb:241:26
@moz-extension://b31ab166-cdc4-44d6-a3ee-935d24f7790a/userscripts/Wanikani%20Reorder%20Ultimate%202.user.js?id=161eb448-5778-4f61-a069-075f1e45e5eb:743:15
I got this error message.
TypeError: Cannot read properties of undefined (reading ‘0’)
at Number.eval (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=6fa56644-3c40-40d9-bb2b-89a5f21a9d5d:257:60)
at Function.each (https://assets.wanikani.com/assets/v03/review/application-fcfa8e614d53542baf1fc02697e12216e8167a19fc88d79ecb4e0f70a3671bc9.js:14:17232)
at Object.apply (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=6fa56644-3c40-40d9-bb2b-89a5f21a9d5d:251:23)
at Object.create (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=6fa56644-3c40-40d9-bb2b-89a5f21a9d5d:280:30)
at Object.init (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=6fa56644-3c40-40d9-bb2b-89a5f21a9d5d:241:26)
at eval (chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/userscript.html?name=Wanikani%2520Reorder%2520Ultimate%25202.user.js&id=6fa56644-3c40-40d9-bb2b-89a5f21a9d5d:743:15)
Logs:
WKU Init()
1 Like
You’ll need to enable script compatibility mode for it to continue working (WaniKani > Settings > App > Compatibility Mode).
The WK team recently made a breaking change to the API, and this particular script will probably never be updated to work outside of compatibility mode, although a few people are working on making new scripts to cover the same functionality.
2 Likes
User: I would like more functionality
WK: Use scripts
User: sigh okay
WK: I just broke all your scripts lol, get rekt
7 Likes
I know a few people have made this remark over the past few days, but I think this is exactly why they introduced script compatibility mode before making any changes. The changes themselves, while they do not have any direct visual results, do seem to improve things on the backend. The major change is a revision to the review queue which reduces the memory and upfront network overhead of reviews significantly. This would essentially allow them to add more data to reviews (e.g. adding more information and categories to items), without having to worry about reviews crashing for anyone due to their device or network not being able to keep up. So even though it’s slightly annoying to have to redo a script, I do feel that the new way of handling items is better than the old way.
But since they know a lot of people use scripts and the changes could break things, they introduced script compatibility mode before doing so. I honestly think they did the best they could. They updated their own code allowing them to do more in the future, while adding the option for users relying on scripts to still use the old model. From a design standpoint, I think their decision actually makes a lot of sense.
5 Likes
I have activated script compatibility mode, but it seems 1x1 mode is still broken. Is there any way i can fix that myself? maybe an alternative script? this confused the shit out of me this morning 
Yes, also broken for me. Please get it fixed, I love the script.
EDIT - script compatibility mode fixed it. Thank you for the suggestions!
Even in compatibility mode the script seems broken, at least for doing lessons. Reviews still seem to work, but in lessons mode I get correct answers marked as incorrect. Something wrong with the questions queue?
I could be wrong, but I’m not sure this has worked for lessons in a long time. Either way, I am no longer supporting this script as-is. I may write my own version sometime later this month if other scripters don’t beat me to it. The changes to WK are too significant to continue making minor tweaks to this version.
4 Likes