Character Creation
The player can assign a name to their character and select a class, which will impact the die used to roll for their stats. To simulate the rolling of a die, I used a coroutine to cycle between sprites. The delay between sprite changes increases as the animation progresses to show that the die roll is slowing down, before landing on the number rolled.
Fog of War
The game features a fog of war system which was implemented using shaders and masks. There are two cameras in place, one for saving the known fog and showing the known fog, and the other for showing the visible area which the player can see through. The camera handling the known fog was set to never clear its flag, resulting in the known fog areas. This was then applied to the render texture which is attached to the camera, resulting in saving the fog of war for that level. Then by swapping out this render texture, it was possible to have saved the fog of war for each of the levels. This way the player would have a new fog of war for new levels while maintaining their existing fog of war for when they eventually go back to previous levels. Furthermore, the game objects were hidden in the fog by setting their mask interaction to only be visible when inside the secondary mask (the visible area around the player).
When the player has an interaction range attached to its game object which when it collides with a game object on the “Interactable” sorting layer will make a button appear. Clicking this button will perform the game object’s interact action which is handled by having the game object's script extend an abstract class for interactables.
Inventory
There are two types of items present in the game. Equipable items and consumable items. Both use the same class as this made it easier to maintain the player’s inventory in one list using this method given the time constraint of the project. Scriptable objects are used to assign the generation properties for these items, with equitable items having a modifier applied based on how far down into the dungeon the player has gone. Resulting in the player getting better equipable item stats as they progress further into the dungeon.
Hovering over an item will present the player with a tooltip which outlines the details of that item. The tooltip is capable of ensuring it is on screen and will adjust itself should it need to. The player can drop or pick items from their inventory, monster drops and chests. Furthermore, they can equip and consume depending on the item type. The consumable items are stackable, with a system in place to check if the player already has that consumable item and continue the stack. When the player drops an item, in places it into a loot bag onto the floor, which the player can interact. This will store all the items the player has dropped in that spot. The loot bag window is designed to group items by pages. Therefore the player can access more items by clicking to the next page and be able to view the rest of the items. If the player’s inventory is full or their weight limit is exceeded then they will be unable to pick up more items.
Throughout the dungeon, the player may encounter shops. Here they will be able to purchase equipment and consumables using the gold they earned from killing monsters in the dungeon. The items in the shop are random, and in the case of the consumables, the amount of a consumable is also random with the price scaling depending on the size of the stack. The size of a level will influence the number of shops which can spawn on that level.
The boss of the dungeon is called Dorian and uses a class which extends from the other monster's class. Dorian can not be attacked and is consistently within range of the player throwing out telegraphs. These telegraphs will go off after a certain amount of turns damaging the player. Since Dorian is always near the player throwing out abilities, I chose to make it a UI element as this saved time by not needing to code this logic.
Clicking the ability will first show the ability’s range, then clicking on an enemy within range will perform the ability given that the player has sufficient fatigue. The player can cancel an ability by clicking on the ability again. Hovering over the ability icon will bring up a tooltip which will detail what that ability does, its cooldown and its fatigue cost.
The ability's range is being dynamically drawn at the start of the game. This makes it possible to change an ability's range without having to update any sprite visuals. By drawing the range once and not every time the player clicks an ability helps in reducing computing power.