The settings menu is structured similarly to Balatro’s. I added the option to change each player's name, and the name carries over in-game.

I created a game stats menu for players to view. The design is an original one I conceived.

There’s a reset button that allows the player to clear their stats. I wanted a dynamic way to show the stats resetting, so I decided on an animation that shakes the current stats off in a way.

One of the aspects I want to highlight here is the information button. In this iteration, I made it a button to click on. I carried over the concept to Auragami and refined it to be hoverable.

Another original design I conceived. Due to the time limit behind the project, not all of the rules save. However, Initial Cash and Pass GO Salary do save, and every rule can be changed.

From a scripting view, this was when I realized my scripting approach was too bloated, leading to further refinements with subsequent projects.

Along with all the menus I showcased, I wanted to embody Balatro’s excellent use of animation. Having each piece and player type animate when cycling adds livelyness to the UI interaction.

This practice permeates so much of the game.

Initially, I followed the layout of EA Monopoly’s UI, just with Balatro’s look and style. However, this did not satisfy me visually, so I closely looked at Balatro’s in-game UI as a start.

I realized each button is of a different size in-game. I took this direction and applied various sizes to the importance of each button. Rolling the dice is mandatory to move around the board, so I made that the largest button.

Different colors also help the buttons stand out more, so with various sizes and color differences, buttons are quickly identifiable.

The user experience is a pillar of an interface-centric experience such as this, so my top priority was to add small details that strengthen that experience.

Details such as the property being bought shrinking down, moving towards the property tab, and having the property card sway are true to the dynamic nature of Balatro’s UI.

Above the roll button are the dice. I placed them above the roll button for ease of use. I wanted players to keep track of them, so I restricted them to the space they occupy.

Information such as how many players are present and properties owned was important to showcase in a digestible way. Since the number of properties players buy or sell can change, I made it the largest info box to easily identify.

Originally, the background was going to be a static color. As development progressed, I was eager to showcase each player’s turn in an eye-catching, yet practical way. Instead of different pieces, I gave each player a distinct color to represent them. This color would manifest through several UI elements and the background.