Posted July 23, 2023 by Acehomie
#JLPT #Japanese #kana #仮名 #漢字 #kanji #learning #日本語
Today's devlog sees a lot of back end changes to implement what I'm calling the Bucket System. This is based off the Leitner system for efficient flashcard studying. The idea is to put every word in a Bucket ranked from 1 to 5. Anytime a player guesses a correct answer, meaning they get all the Kana correct on a question it will move up one bucket. Fail to answer a question correctly and go down one bucket. Now these buckets each have a percentage starting at 50 for 1 and going down to 5% for 5 which represent how often a user will be shown a word. The long and short is that initially this means players will be re-enforcing words they know while still showing them unfamiliar words until users have pool of known words which then they will start to see those words less. The idea being more efficient learning :)!
One of the next major features is the addition of the Review Page. After a user has played through a few matches they will have racked up a certain number of familiarity points. Players can keep track of these points and see words with both their Kanji and Kana reading to review any words they are unsure of. There is definitely a few things I'd love to add here like a search features or different types of sorting, but let me know what you think!
You can navigate to this page by clicking the "Review" button from either the title screen or the JLPT Select Scene.
There were quite a few QOL improvements particularly to the backend for handling the Word data sets which I think will lend nicely to implementing new word sets. However one of the last I'd like to call out is the addition of the skip button. In the last iteration if you were answering a question and didn't recognize any of the answer words you were forced to guess and hope you got a Kana you needed. Now for any question if you get a set of words that you're unsure on you can skip and get a new set of words. Currently this is for no penalty to either score or Word familiarity, but I'm thinking in the future of deducting a bit so this method doesn't become meta. Let me know what you think, should this be penalized?
That's it for this devlog, thanks for reading/playing :)
Bug/QOL improvements: