Soulslike games communicate entirely through gameplay. The first enemy in a soulslike teaches the player how parrying works by killing them. The second teaches them that enemies behind corners exist. Designers write the lesson plan in encounter placement, not in tutorial text boxes. Every death is feedback.

Build the soulslike you want by describing your world architecture, your combat feel, and your boss encounters. Summer Engine helps you create the stamina system, the estus-equivalent, and the enemy aggression model. You design the geography that punishes rushing, the shortcuts that reward exploration, and the bosses that define your game.

The rewards in a soulslike are not just items. They are understanding. A player who survives the game does so because they learned every system, every enemy, and every secret it had to offer. Designing a soulslike means designing an education in your game world. That starts with deciding what you want to teach first.

• Solo devs who want to build a challenging action RPG without recreating the entire Souls combat engine from scratch.
• Designers with a specific world and lore vision who want the soulslike format as a vehicle for exploration and atmosphere.
• Anyone inspired by Dark Souls, Elden Ring, or Hollow Knight who wants to create their own take on the genre.
• Teams building a game where difficulty and atmosphere work together to create a specific emotional experience.

• World Zone Vertical Slice

  Build one interconnected zone with a bonfire, 10-15 enemies, and a boss. Show the world architecture, the combat system, and the shortcut design that defines the genre.

• Boss Showcase Demo

  Build 3 handcrafted boss encounters that demonstrate your game direction. The boss is the marketing. The rest of the game supports it.

• Metroidvania-Adjacent Soulslike

  Build a 2D soulslike with metroidvania-style ability gating. Players unlock movement abilities that open new routes back through areas they could not reach before.