Eriast Derby

Every attribute and statistic like health and armour class can be modified through various game mechanics (skills, status effects, equipment etc.). The modifiers are aggregated in StatCalculator while keeping note of their source for logging and UI tooltips.

A unified way of handling all kinds of common actions that happen in a D&D setting such as dealing damage, applying buffs, draining resources, etc. This allows code reuse across multiple sources of such actions like player skills or environmental effects (e.g., from event cards). This system allows for fully modular and composable skills and events that can be created and configured in the editor.

System for evaluating and executing skills and abilities. This can include attacks, buffs, debuffs or any combination composed of effects. Also includes the logic of skill checks, saving throws and attack rolls, with more possibilities in the future.

Each effect in a skill can specify targeting rules. Those include the source, a target entity, the enemy vehicle as a whole, multiple targets, and more. This allows for configuration of complex skills like "damage the enemy while also applying a status effect to self."

Used for handling buffs, debuffs, damage over time and other behaviours common in games of this genre. Fully composable and modular using the effect system. Implemented as a Flyweight pattern with a template and runtime instances.

Vehicles are composed of modular components, each with their own stats, health and functionality. This allows for creating any sort of vehicle for different playstyles and tradeoffs by choosing the components to include. Gives interesting tactical depth for the players while also giving an identity to the NPC vehicles. Also allows for progression as the players find or create better and more powerful components in the parallel D&D campaign.

The vehicles are meant to support any sort of crew configuration, be it a 5 player team with their own specialisations, or a single driver controlling everything. As such, the seat system was developed to control how many characters a vehicle can support and which components they operate. It also controls which character will be responsible for which skill check and saving throw via a dedicated routing class.

A state machine that controls the flow of the game and progression of the race on a turn-by-turn basis. Determines which vehicle goes next, when event cards are drawn, when status effects tick, and so on.

The idea behind the race track is to make each stage distinct with its own imagery and tactical considerations. Mapping each stage on a typical D&D gridmap would not only be too time consuming, but it was also not very fun during early playtesting. On the flipside, having simple, uniform and abstract stages felt like it stripped away their identity. Therefore a middle ground was devised to include multiple lanes in each stage, with flavour and tactical implications. Vehicles can move between lanes to attain different benefits and drawbacks, while also triggering different checks, saves and events.

The lane system offers ample opportunity for future expansions, like blocking lanes, more complex AoE targeting rules, combat considerations like flanking, conditional hazards, and much more.

A complement to the stage and lane system aimed at enforcing stage identity even more, as well as adding an element of unpredictability. Event cards can happen at any point during the stage and can be They can also include narrative flavour and player choices while providing bonuses, penalties, or environmental changes. Vaguely similar to events in strategy games like Europa Universalis or Crusader Kings.

A complex logging system that allows for meticulous recording of everything that happens within a race, from attacks, damage, skill checks, to lane changes, event card triggers, and much more. Meant to be the ultimate monitoring tool for the DM to keep track of what's going on, while also offering excellent debugging capabilities during development. Also includes a full breakdown of all calculations with modifiers and their sources.

In the future, this system could be used to generate a summary of the race and its key moments.

A rudimentary UI in Unity used for debugging and display purposes. Offers all the required information to understand the state of the game such as the state of every vehicle and its components, their positions in the stage and lanes, or a log of all the actions that happened.

Automated test covering most core mechanics as well as several more complex integration tests. While most testing happens in the Unity editor, the automated tests provide an indication if any of the core mechanics might have been broken by a change. The core architecture was designed with testability in mind, so writing automated tests is straightforward and doesn't require any special setup or workarounds.