FrostFyte Design Architecture

• FrostFyte is a platform fighter in which players are tasked with knocking opponents into the blast zone, using a variety of attacks to damage them and send them flying further.
• The game is a take on the traditional fighting game formula that incentivises a greater emphasis on movement and stage control.
• The game is built in GameMaker, using Platform Fighter Engine.

• FrostFyte features a large variety of assets, abilities, and requirements.
• As such, we’ll need an architecture that can support lots of data, in the form of sprites, scripts, and other assets.
• We’ll also need to have easy access to the relevant data at any given time.

Two options pique our interest with that goal in mind:

Blackboard: A system-active architecture in which computational processes are determined by data status.

Repository: A client-active architecture with in which computational processes are independent.

We’ve chosen a Repository Architecture, as an architecture accustomed to user input would be optimal for a fighting game, and the independence of computational process will be helpful for the constantly shifting game states at play.