William Koch wrote:This game I am creating needs to implement the strategy pattern, and it also needs to use the model view controller.
Why? "I need to hang this painting. I need to use glue". Even if glue will work, it seems ridiculous to limit yourself to a solution before you've even started exploring alternatives.
You can not know ahead of time everything that your program needs. Something always pops up during the design process. This is fine, it's how software is developed. Start with what (you think) you know for sure you'll need.
First of all, to me it seems pretty essential to keep track of each player's rolls. How about a ScoreCard class? A Yahtzee class can then keep track of ScoreCards and player turns. You also need a way to classify combinations: A Combination enum, that can calculate the score for a roll. Players also need to be able to choose how to reroll the dice, and select a category to put the points in. If you must, this is an opportunity to fit it the Strategy pattern.