[Userscript] Reorder Omega

Previously there were three Back To Back modes

  • Repeat Until Correct: This already works
  • True Back To Back: I believe this should be possible, and I plan on bringing it back shortly Nevermind. It’s the same as Shuffle Incorrect
  • Shuffle Incorrect: This is technically possible for the moment, but would rely on WK not undoing certain temporary changes, so I have no plans on supporting it for now
1 Like

After double checking the streak counter does work correctly. The percentage is native to WK and Omega doesn’t touch it at all, so you’ll want to bring this up with @rfindley in the Double-Check thread.

1 Like

Thanks for checking!

I gave this script a try for the first time today and it works wonders for sure. Thank you @kumirei for making this great script! <3<3<3

7281bcb37e23bdc0d2e436488dfa9d18

1 Like

Yeah, I absolutely cannot imagine doing reviews without the reorder settings that work for me.

In my case its back-to-back reading-first. I really recommend trying that out, because I find it makes the brain “think in japanese” or another way to say it, brain “reads” the kanji with its reading and then makes the connection to meaning based on context, which feels very natural (if you were to read aloud a japanese sentence, youd also want to “read the reading”.
You do lose the “double appearance” of an item in reviews if its back-to-back (regardless of whether meaning or reading first), but I found that to actually be a hindrance and not an asset - it makes the “reading experience” very artificial and keeps reading and meaning separate in memory for longer, making you rely on mnemonics longer (I like to be able to do away with mnemonics after apprentice, which works better with back-to-back reading-first).

2 Likes

An idea about how to support true back to back without relying on WK not undoing temporary changes:
Let’s assume the user selects reading → meaning for this example.
Create a dictionary like the following:
key: [string] review item (maybe subject ID?)
value: [array of answer_check] answer_checks
If they answer the reading incorrectly, store the answer_check in the array and shuffle the item back into the review queue without answering it.
If they answer the reading correctly, store the answer_check in the array and ask for the meaning.
If the user answers the meaning correctly as well, submit all answer_checks stored in the dictionary and then the current one.
If they answer the meaning incorrectly, store the answer_check in the array and shuffle the item back into the review queue without answering it.
Now everytime a new item gets loaded, check if it already has a passed answer_check stored in the array. If yes, show the meaning instead of the reading. Then proceed as per the other cases.

Just an idea, but maybe it helps.

1 Like

Thanks, but I don’t want to get into the business of manually submitting reviews. Although I wouldn’t mind if you wanted to create a stand-alone script which does this

1 Like

Understandable. I might just sit down and do this, doesn’t seem to be too much of a challenge, although I can’t say for sure when I’ll find the time to actually sit down and do it. But once I do, I’ll let you know so you can implement it into Reorder Omega.

1 Like

It’s possible this preset has already been discussed, but there’s a lot of replies here so I’m just going to ask: I’m looking to make a preset that sorts by “most recently reviewed.” Would that be the same as sorting by overdue in ascending order?

1 Like

No. In an ascending “overdue” sort, an Enlightened item that was last reviewed 4 months and 1 day ago is only 1 day overdue, and an Apprentice1 item that was last reviewed 3 days ago is 2 days overdue.

1 Like

I think the closest option I have is the “recently failed” filters added by this script. If you need a filter that includes passed items as well I don’t mind adding that

Hmm, well I think this is still basically what I want in the end. It’s not that I’d be using this preset to avoid high-SRS stage items so much as that I want to make sure that things I’ve passed/failed come up as soon as they’re due rather than get buried (and forgotten) behind a bunch of other older backlog stuff.

Thanks for the clarification! I’m never certain which is ascending and which is descending either haha.

1 Like

Can this user script put all the readings first, then all the meanings? I put on “Sort by Type,” but it’s still going back and forth between readings and meanings, and since the color is the same, it always takes me a couple seconds to process which one I’m supposed to type.

1 Like

You can set it to show meaning and readings back to back, with reading always coming first. You cannot set it to show all readings and then all meanings. This is a limitation in how Wanikani works rather than the script

2 Likes

Ok, that should work fine once I get used to it. I want to ask how to do that, but I’m sure it’s already explained somewhere. Sorry I can’t figure it out so far haha.

1 Like

In the settings under General you’ll want to set the Back To Back setting to anything other than disabled (although at the moment only Repeat Until Correct is available), and Prioritize to Reading

2 Likes

Thank you!

This may be a dumb question, but what does speed demon do exactly?

1 Like

If you look in the settings you can see exactly which actions it contains

As you see it:

  1. Filters out non-critical items (items not needed for you to level up)
  2. Puts radicals first in the queue (because they need to be guru’ed first)
  3. Puts the non-critical items back in to the queue (but after the critical items)
2 Likes

Oh, I’m sorry! Thank you :blush:!

1 Like