BUSHIDOCODE Let’s talk

Game development & prototypes

Find the fun.
Then build on it.

A game idea becomes easier to evaluate when you can play it. I help turn a concept into a focused prototype or interactive experience that gives you something concrete to test.

Talk through your idea

The right starting point

Start with what the player actually does.

Before a long feature list, define the central action and why someone would want to repeat it. A prototype can explore that core loop with a small amount of content. The goal is to learn which parts feel good, which need work, and whether the direction is worth expanding.

Playable prototypes

Test a mechanic, interaction, or core loop in a small build. Decide what the prototype needs to demonstrate, then keep secondary systems out of the way until the main idea has been explored.

Game systems and interactions

Scope the behavior behind the experience: how a player interacts, what changes in response, and how progress is communicated. The platform and existing project determine the technical approach.

Creator tools

Tools are part of game development too. My own project, Stasis Engine, is a drag-and-drop game creator currently in development. It reflects my interest in making the process of building games more approachable.

Scope & fit

Give the prototype a specific question to answer.

The scope changes significantly depending on whether you need to test movement, a puzzle, a combat interaction, or a larger experience. We’ll identify the target platform, the essential mechanic, the assets available, and what a playtest should tell us. Multiplayer, custom art, audio, and publishing requirements need their own explicit scope.

A prototype is useful when there is still something important to learn about the idea. It is different from a finished release, and it should be evaluated on that basis. After playtesting, we can decide what to refine, what to remove, and what a further phase would involve.

Working with Bushido Code

Direct collaboration.
Focused iterations.

You work directly with Matt, the developer behind Bushido Code. We’ll discuss the problem, agree on the first useful outcome, and review the work as it takes shape.

I use AI to accelerate exploration and implementation. Architecture, code review, and testing remain hands-on responsibilities. The scope and complexity of the project determine the timeline.

More about my approach

Before we build

Questions worth asking.

Do I need a complete game design document?

No. A description of the central mechanic, the intended player experience, and a few references can start the conversation. We can use those to define the question a first playable build should answer.

Which engines and platforms can you work with?

The right fit depends on your project and its requirements. Include your existing engine, target devices, and any code or assets already available so we can assess compatibility before committing to the work.

Is Stasis Engine available to use?

Stasis Engine is currently in development. It is a drag-and-drop game creator, and there is no public release page yet. You can email me if you want to discuss it.

Start a conversation

Tell me about
the work.

Share the central idea, intended player, target platform, and what an initial prototype should prove.

Prefer email? You can still contact me directly.