COLLECT ARROWS, DEFEND THE CASTLE!

Carry arrow bundles into danger, return before the orcs break through, and turn your visible arrow tail into the fortress’s arrow storm.

Comment 2

Inspiration

I wanted to make a defense game where the player feels directly responsible for keeping the fortress alive.

In many defense games, the player places weapons and watches the battle happen from a distance. For this project, I wanted the player to feel closer to the defense moment. Instead of only commanding the fortress, the player becomes the supply line that keeps the fortress fighting.

One thing I thought about a lot was how quickly a player could understand what to do when the game starts. I did not want the player to feel lost in a wide open space or depend on a long tutorial. That is why the game uses a clear forward-and-return structure: the fortress is behind the player, the rewards are in front, and the decision is always easy to read — collect more, or return safely.

Because the core system may feel unfamiliar at first, I used a classic hero-versus-orcs fantasy theme. The familiar setting helps players quickly understand the threat, the role of the fortress, and why their supply runs matter.

What it does

COLLECT ARROWS, DEFEND THE CASTLE! is a defense game built around risky supply runs.

The player leaves the Fortress Safe Zone, enters the battlefield, and collects arrow bundles and visible Gold. Each arrow bundle connects behind the character as a visible tail. The tail shows the value of the current run at a glance: the longer it becomes, the bigger the payoff — and the more the player has to lose.

Basic Orcs advance toward the fortress. They do not directly chase the player, but they create pressure by moving toward the defense line. If the player touches an orc, they lose part of the carried arrow tail and collected Gold, but they are not instantly removed from the game.

When the player returns safely, the arrow tail is absorbed into the Central Supply Depot and converted into ammunition. Then the five Arrow Launchers near the fortress entrance fire automatically, turning the player’s risky supply run into a visible arrow storm.

Defeated orcs drop Gold directly onto the battlefield. This makes the field tempting even after a successful defense. The player sees Gold outside the Safe Zone and wants to run out again, collect it, upgrade the Arrow Launchers, and push farther on the next run.

How we built it

We built the project around one clear player loop:

collect arrows, build a visible tail, return safely, power the fortress, collect Gold, upgrade, and push farther.

The first design priority was readability. The map is structured like a risk-reward corridor instead of a wide open space. Nearby areas are safer and easier to recover from, while deeper areas offer better rewards and higher risk. This makes the player’s choice simple to understand but still meaningful.

We also kept the defense system focused. Instead of using many different weapon types, the fortress uses one clear weapon family: Arrow Launchers. As the player upgrades them, the launchers become stronger, fire more arrows, cover more space, and create a bigger payoff without becoming visually confusing.

The UI and progression were designed to stay close to the action. The player sees the carried arrows as a tail, sees Gold on the field, and uses upgrade buttons near the fortress. This keeps the rhythm fast and avoids forcing players into deep menus between runs.

Challenges we ran into

The biggest design challenge was making a fresh system feel easy to understand.

The arrow-tail supply system is not a standard tower defense mechanic, so we focused on making every important idea visible. The player can see the Safe Zone, the battlefield, the arrow tail, the Gold, the orcs, and the Arrow Launchers without needing a long explanation.

Another challenge was balancing tension and comfort. I wanted the player to feel risk when carrying a long tail, but I did not want one mistake to end the experience. That is why orc contact causes partial loss instead of instant death. The player loses enough to feel the danger, but can recover quickly and keep playing.

We also had to make the failure state feel fair. A fortress breach does not erase all progress. Long-term upgrades remain, so failure becomes a reason to reinforce the fortress and try again.

Accomplishments that we're proud of

I am proud that the main hook is easy to explain in one sentence:

the arrows behind the player become the arrow storm in front of the fortress.

The visible arrow tail makes the player’s inventory feel physical. Gold on the battlefield creates a natural “one more run” feeling. The five Arrow Launchers create a clear payoff when the player returns safely.

I am also proud that the game combines a familiar fantasy theme with a new supply-run structure. The orcs, hero, fortress, and arrows are easy to understand, while the way the player powers the defense feels different from a traditional tower defense game.

What we learned

We learned that simple readability can make a game feel stronger.

A new mechanic does not always need a complex explanation. If the player can see what they are carrying, where danger is coming from, where safety is, and what happens when they return, the game becomes easier to understand.

We also learned that failure can support retention if it feels fair. Partial loss, knockback, recovery, and checkpoint-based fortress fallback create tension without making the player want to quit.

Most importantly, we learned that a small change in player role can change the entire feeling of a defense game. The player is not just placing defenses. They are the reason the fortress can fight back.

What's next for COLLECT ARROWS, DEFEND THE CASTLE!

Next, we would expand the same core loop without changing the game’s identity.

We would add deeper battlefield choices, more valuable Gold recovery moments, stronger Arrow Launcher upgrade stages, clearer fortress breach feedback, and lightweight social goals such as highest wave, longest arrow tail, most Gold recovered, and strongest fortress.

The main rule for future expansion is simple: every new feature should make the supply-run, fortress defense, Gold recovery, and upgrade loop stronger.

Every risky supply run should make the fortress stronger.

Built With

  • and
  • designed-for-meta-horizon-worlds-as-a-concept-submission.-built-with-game-design-documentation
  • low-poly-3d-fantasy-art-direction
  • mobile-first-ui-planning
  • pdf-based
  • production
  • visual-mockups
Share this project:

Updates

Submission history