First Post-Launch Update
It’s been one week since the release of Risk & Riches. Thank you to everyone who has purchased the game and supported Growlery Games!
Most of the feedback has been positive, but a major bug was discovered (situational, but it causes a crash), and there were a couple of design elements that I wanted to improve. So here’s the first post-launch update to Risk & Riches.
Changes
Made it so the mouse line that follows the cursor after a card is selected in an Encounter first appears red and then switches to yellow when the card is playable (over a relevant character or the play area). This will hopefully improve the indication that cards that are self-targeting or target all can be dropped on the play area without needing to be dragged all the way to the player character or enemy, depending on the type of card. Single target offensive cards do need to be dropped on the target.
Changed the material setting on the character highlights (the four triangles that frame a character when hovered over) so that they are not impacted by other shaders and increased their opacity to appear brighter. This was also part of trying to make it clearer when and which characters were targetable by cards that can be dropped on the play area.
Added a floor count icon to the top bar in the UI when in the mine that shows which floor you are on out of the 4 floors.
Added a highlight that appears as either yellow or red when you drag a card over the Pocket Card area/box to provide further feedback about whether you have enough energy to pocket a card.
Bug Fixes
Corrected a check in the building menu to use the updated building costs when in New Game+ so that the purchase button is disabled if the player doesn’t have enough gold (it wouldn’t allow purchase, but the button wasn’t visibly disabled).
Added a safeguard to prevent a crash if the player attempted to draw cards when both the draw pile and the discard pile were empty (possible with Gambler).
Additionally, some new sprites were added to the project in preparation for a future content update, but the associated content has not yet been implemented.
Again, thank you for your support!
