[Dev] What Should We Show First? (Prototype)
Aug 21, 2026
This prototype build is not simply meant to confirm that the systems work.
We plan to start reaching out to external investors with this build, so within a short play session, we need to show what kind of game BARIEL is and what makes it fun.
The problem is that there is a lot we want — and need — to show.
At the core of BARIEL is the interaction between action combat, traps, defense, and building.
That means the prototype also needs to introduce those elements as early as possible.
And that is where the questions started.
How Much Do We Need to Explain?
Normally, players learn a game naturally through tutorials and quests.
But at this stage, building a proper tutorial and quest system would require a significant amount of development time.
The bigger issue is that most of what we build for a tutorial now would likely need to be rebuilt by the time the game reaches full release.
So for the prototype, we are trying to avoid creating dedicated tutorial and quest systems as much as possible.
That immediately creates another problem.
How do we explain the game to the player?
We want to keep explicit explanations to a minimum, but the player still needs to understand what they are supposed to do.
At some point, it started to feel like preventing a first-time player from getting lost might be harder than building the prototype itself.
How Much Should We Show?
How many monster types do we need?
How large should the first wave be?
How much of the repeating wave structure should we show?
After experiencing defense at the territory, how far should the player be able to venture out into the world?
How difficult should the opening be?
Would deliberately allowing the player to fail once help them understand the game, or would it simply create a bad first impression?
Every decision immediately led to another question.
Since we cannot show everything in a prototype, the more important question became what we should show, and what we should deliberately leave out.
Should the Player Start by Building?
Building was another major point of discussion.
If the player starts in an empty space and builds everything themselves, they can naturally experience BARIEL's building system from the beginning.
But if a first-time player has to understand the building system before they can reach the action and trap-defense gameplay, it may take too long to get to the part we most want to show.
For this prototype, the first thing we want players to experience is not a building menu.
It is fighting directly while making use of traps.
So for now, we have decided to begin the game in a space where some of the building and trap placement has already been intentionally set up.
Instead of entering a completely empty area, the player starts inside a prepared defensive space.
Without having to explain everything directly, we want the environment itself to communicate ideas like:
"I can place traps here."
"Enemies are going to come from this direction."
"This is a game where traps and direct character action work together."
At least up to the point of starting and playing through this initial setup, the direction is now decided.
What happens after that is still being discussed.
Should the player begin building for themselves after the first defense?
Should they head out into the world?
Should we introduce new traps?
Should they immediately experience another wave?
We are still working through those questions.
Not Building a Game Only for the Prototype
There is one more point that has been especially important throughout these discussions.
We want to minimize development work that exists only for the prototype.
For a small team like ours, spending several weeks on a feature that is used only in the prototype and then discarded represents a significant cost.
Of course, some prototype-specific work is unavoidable.
But whenever possible, we want the systems and assets we create now to carry naturally into full production.
That is also one of the reasons we are not investing heavily in a polished tutorial system at this stage.
Rather than building separate systems that will only be used now, we decided to focus on building the game's actual core systems first, and then think about how best to present them.
At the same time, an investor or a first-time player still needs to understand within a short session that they can:
fight directly, use traps, defend against waves, and build.
The challenge is finding the right balance between development cost and first impressions.
We Still Don't Have All the Answers
Because it is called a prototype, it can be easy to think that all we need to build is a smaller version containing the game's core features.
In practice, we found the opposite to be true.
Because the play session is short, the fun needs to appear faster.
Because there are fewer systems, we need to be more deliberate about which ones remain.
And ideally, the things we build in this process should continue into later development.
At the moment, one thing has been decided:
the game will begin in a space where the initial structures and traps have already been deliberately arranged.
The number of monster types, wave structure, scope of world exploration, difficulty, whether the player should experience failure, and what happens afterward are all still being discussed.
As usual, we will probably find the answers by building it, playing it, and adjusting from there.
We are working on a prototype,
but perhaps the question we are thinking about most right now is not what to build, but what to show first.