How to Make Easy behave exactly like Good via Custom Scheduling?

Anki Help
1

Hi, I want the Easy button to produce identical scheduling to Good (when FSRS is enabled).

Which of these (if either) is the correct way to do it via Custom Scheduling?

javascriptstates.easy = states.good;

Or maybe:

javascriptif (states.good.normal?.learning) {
states.easy.normal.learning = states.good.normal.learning;
}
if (states.good.normal?.review) {
states.easy.normal.review = states.good.normal.review;
}

Is one of these correct and complete, or is there a better approach?
Will it work too on Anki Mobile?

Thanks!

2

… why though?

I’m asking because it seems like a terrible idea. I’m wondering if we have an XY problem here, and if we knew what your actual goal/reasoning was, there might be a smarter way of getting there.

3

It may sound harsh, but the real reason is to prevent my son from cheating on his studies with Anki… :scream:

4

How about disabling the ‘easy’ button instead?
https://ankiweb.net/shared/info/1236436346

5

That doesn’t work on AnkiMobile. In fact, nothing will work since OP’s son can always press “Good” when they failed.

My recommendation is to regularly test them using a filtered deck and compare their answers with the stats of the filtered cards. Maybe the average retrievability can be used as a baseline for how well they should be able to answer.

6

Missed that part. But if the goal is to make something work on iphone, AnkiWeb is an option. There the buttons can be selectively hidden too. Moreover, for a typing card just a single Again/Good button can be left on the screen depending on the entered answer.

7

Thanks for the suggestions.

Yes, the reviews are always about Anki Mobile, which limits the options.

He has enough self-discipline not to tap “Good” when he doesn’t know the answer… but sometimes he does tap “Easy” when it’s actually not that easy.

Based on the responses, should I assume that my suggestions regarding “Custom Scheduling” are incorrect?

8

In that case, just let your son use gestures and to effectively disable the “Easy” button.

[I don’t know about custom scheduling.]

9

We’re all like that.
I don’t see anything we can do to prevent cheating.
We love to deceive ourselves: “Simply viewing creates a sense of familiarity: ‘I’ve seen this, so I know it.’ But when tested, the information is often not retrieved (recalled).”

Typing—that is, writing—is the best test, and that’s how we prepared for the exam, writing out each question in full.
But even then, the child will want to throw the card as far into the future as possible and press “Easy.” So, the best thing to do is to disable this button altogether, hide it.

Another indicator of knowledge is recall speed. If you recall something almost instantly, in no more than two seconds, then you know it. It’s difficult to do this with settings; perhaps the person got distracted and walked away. You have to judge for yourself, based on the speed of your response, whether you really know it that well. But I still wouldn’t press “Easy,” unless you have time before the exam. But when it’s 3-7 days, unfortunately, you have to select the ones you don’t know well, and you’ll have to sacrifice those easy steps, since it’s unlikely you’ll forget them.

To clarify the speed, I recently gave an example like this: Seas (6th Grade)

This was described in the add-on: https://ankiweb.net/shared/info/675107747

10

Thank you all for your suggestions.

After several tests, it seems that the following javascript code makes the “easy” button equivalent to the “good” button (even in Anki Mobile):

states.easy = states.good;

This should be pasted into Options > Advanced > Custom scheduling

This change applies globally to all decks. It is not possible to apply it individually.