Designing a platformer where you don’t control jumping

#gamedev #indie #gamedesign #2d

We recently released a 2D precision platformer on Android, built around a simple question:

What happens if the player doesn't control jumping?

In most platformers, jumping is the core mechanic. It’s reactive and immediate. You press a button, and you jump.

In Crom's Escape, the character jumps automatically.

The player controls only movement, timing, and positioning.

Why remove jump control?

The idea was to shift the challenge away from reaction toward consistency.

Instead of asking:
"Did you press jump at the right moment?"

the game asks:
"Are you in the right position at the right time?"

Removing manual jumping changes how levels are built:

Levels are designed with very low tolerance for error, and failure usually happens quickly.

This is intentional.

Fast retries are part of the core loop.

Early versions felt confusing rather than difficult.

Players tried to jump instinctively.

So the design had to clearly communicate:
"Jumping is not under your control."

The final result is a precision platformer that feels unusual at first but becomes predictable over time.

It’s not designed to be accessible or relaxing — it’s built around repetition and mastery.

We’d be curious how you approach gameplay constraints like this.