I still feel like the review intervals are out of whack. For example, if I get a character correct once then the next time it appears in my review is a few days later. If I get it right again it jumps to 3 or 4 months later. Is it possible to set smaller intervals? Does anyone else besides me think this is a little off?

Not sure if anyone is familiar with it, but I think the intervals for a flash card software called "Anki" are ideal. It's more like 3 days, a week, 3 weeks, then 6 weeks, etc. Basically the interval doubles each time an answer is correct. And of course an option to press an "easy" button or something for a character that one feels is already ingrained would be nice.

The only thing that I feel odd is that a word and it tones often gets revieved separately. with a couple of minutes in between. Then the second review gets a bit pointless. These should definitevly be grouped within a "big bag o' reviews"

not sure about the jkatz thing, maybe i'll look into my vocab to see if i have many with such a large interval.

I definitely CAN confirm what bodin says, happens to me with some regularity that a tone will be tested for a word, and then within a minute or two the characters will come up to test, which are obviously much easier having just seen them. The majority of the time I assume it knows to test both and seems to, but hopefully that algorithm will keep getting better! :)

The intervals for the stuff you get right the first time grow quickly because Skritter is guessing that you already knew that word/character from before. Did you? If you get it wrong once, they grow more slowly.

This next big Flash rewrite that I'm debugging now has 1-4 grading if you want to use it, which you'll be able to use for more accurate scheduling if you like.

I see the problem with the tone/writing being split even though both are about ready. If I'm correct, then this only happens when you're getting toward the end of a review queue (not when they're both much overdue), and the items are longer-term items (intervals over a couple days)?

Yes, your right. It happens when I'm getting toward the end of a review queue. But at that point in time it would be even more easy to group them, right?

It should have been working, yes. It's just a bug in the code that determines whether the other part is ready to be grouped in there. I think I've just fixed it, so let me know if you see this again.