Original systems-driven game / In active development
Evil Alchemist
A dark alchemical roguelite with turn-based combat. Its clean .NET 8 domain stays independent from Godot while mechanics and balance live in a versioned, validated data model.
Design, architecture and implementation
What this demonstrates
The project shows C# beyond conventional web work: complex rule modelling, game state, auditing tools and sustained work on a large system.
Evil Alchemist: C# beyond the usual web
Evil Alchemist is an original turn-based roguelite where most of the work lives in rules, data and tools. It shows how I use .NET to build a domain independent from the game engine.
FIELD NOTE
DOMAIN
Mechanics do not depend on a scene
A clean .NET 8 domain stays separate from Godot. Combat, status, reaction and progression rules can be tested and evolved without mixing logic with presentation.
DATA
Balance lives in a versioned model
Ingredients, recipes and encounter configuration live in JSON. Experimenting with 162 alchemy combinations does not require rewriting scenes or control code.
TOOLING
Validation before runtime
GameContentValidator and a dedicated audit check recipe completeness and cross-catalog references. Separate knowledge profiles, checkpoints and three save slots are designed into the system.
NEXT ITERATION
Need a system with similar capabilities?
Tell me what you are trying to improve and we can map the next practical step.