Using information from The Movie Database API, create a collaborative game where trivia about a movie (movie name, performers, genre, year produced, etc) is provided as a hint, and the user must guess the correct answer based on a list of possible answers. The user has ‘X’ seconds to answer. Click an answer to confirm your guess. If your guess is correct, then you will be rewarded with a link to play the movie trailer. Additional correct guesses will display a badge with the number of correct guesses. An incorrect guess will clear the badge and reset the game. The game can be played with one or more players at a time in person or using a screen share service like Zoom.
Originally the purpose of this ticket was to fetch the genres of all movies from the API and create a feature where the user could pick a genre and during the gameplay the questions would correlate to whatever genre the user picked, but after completing the ticket we realized there was going to be a lot more complexity than expected so we decided to prune the feature as a whole. With that being said, while creating the ticket we modified the fetch to be able to dynamically change the amount of pages the fetch was pulling from the API which is the main reason we are still pushing this ticket up to develop.
Approach
The approach we had in completing this ticket was to find a genre endpoint and succesfully fetch from that endpoint to filter the questions based on what the genre the user wanted to pick.
Learning
While working on this ticket we learned that there is too much complexity within the scope of this feature to fully implement within our game. We were able to complete the ticket but there would have to be many more feature tickets to make the game as functional as we would want it. So to wrap things up the only thing being pushed up form our branch will be a modified fetch we originally had which is more dynamic in terms of how many movies will be fetched form the API
Changes
Purpose
Originally the purpose of this ticket was to fetch the genres of all movies from the API and create a feature where the user could pick a genre and during the gameplay the questions would correlate to whatever genre the user picked, but after completing the ticket we realized there was going to be a lot more complexity than expected so we decided to prune the feature as a whole. With that being said, while creating the ticket we modified the fetch to be able to dynamically change the amount of pages the fetch was pulling from the API which is the main reason we are still pushing this ticket up to develop.
Approach
The approach we had in completing this ticket was to find a genre endpoint and succesfully fetch from that endpoint to filter the questions based on what the genre the user wanted to pick.
Learning
While working on this ticket we learned that there is too much complexity within the scope of this feature to fully implement within our game. We were able to complete the ticket but there would have to be many more feature tickets to make the game as functional as we would want it. So to wrap things up the only thing being pushed up form our branch will be a modified fetch we originally had which is more dynamic in terms of how many movies will be fetched form the API
Closes #24